Deis 0.3.1 - Fixes and Docs
The Deis project is happy to announce our v0.3.1 release. Usage of Deis has begun to take off, and the user community has been extremely helpful in finding issues and suggesting improvements. This is a maintenance release that implements and fixes nearly everything reported so far. Please keep the feedback coming!
What is Deis?
Deis is a Django/Celery API server, Python CLI and set of Chef cookbooks that combine to provide a Heroku-inspired application platform for public and private clouds. Your PaaS. Your Rules.
- Added navigation between documentation versions, e.g.:
- Added permalinks to documentation headers
Under the Hood
- Updated to Django 1.6.1
- Added several tests to the "make test" API suite
- Added unit tests for web/templatetags
- Updated boto, Sphinx, celery, django-restframework
- Fixed env vars being sometimes unavailable in
- Return error detail in some
knife bootstraperror cases
- Hid web signup form; use
deis registerfrom CLI
deis keys:add ~/.ssh/mykey.pubargument handling
- Fixed client setup.py to install tested versions of support packages
- Fixed node deletion on DigitalOcean when provision script errors
- Fixed DigitalOcean provisioning script for Mac OS X
- Fixed EC2 security group deletion to be more robust
We want to thank the following Deis community members for creating GitHub issues, providing support to others, and working on various Deis branches:
- @tombh - DigitalOcean provision script fixes, Vagrant node destruction fix, proposed test improvements and slugbuilder hook relocation.
- @bacongobbler - Permalinks request, service discovery spec, stellar support on IRC and GitHub as always.
- @lvnilesh - Testing, many bug reports.
- @ksikka - Testing and bug reports.
- @dscanlonpa - Bug reports and testing.
- @alanjds - Bug reports with a side of testing.
- @mrkaspa - Doc bug report for stale install URL.
- @guestisp - Doc bug report for bare metal installation.
- @bengrunfeld - Env vars availability bug report, many months of testing and help!
Containerization of Deis Components. Converting all the Deis components to Docker images is well underway in the containerize branch. This will result in a more modular system that's easier to deploy and manage.
Release Rollback and Auditing We need to provide developers the ability to rollback to a previous release. While we have the infrastructure in place to do this, we don't yet tag releases with meaningful log events that describe what was changed.
deis runThough we provide the ability to run admin commands inside containers, we don't currently support interactive shells into containers. We will soon.
Enhanced Docker Integration
Deis currently uses Docker as a LXC wrapper for running Heroku Buildpack slugs that are bind-mounted into containers. We will sonn add a new
git push build process that creates and distributes images via
Dockerfile and a private Docker registry. Follow progress on this GitHub issue.
We need to make it as easy for ops folks to publish a set of reusable backing services (databases, queues, storage, etc) and allow developers to attach those services to applications. This will be done in a loosely coupled way, following Twelve Factor best practices. You can review the specification and follow progress on this GitHub issue.
General Security Improvements
The controllers require SSL configuration. Right now controller sessions are just HTTP with cookies and passwords sent in the clear! We've also glossed over some pretty important security features in an effort to get Deis into developers hands. For example, we need to implement iptables host-level firewalls, improve security group default rules, use Chef recipes to harden systems, etc.
How can you help?
- Star our GitHub repository
- Help spread the word about @opendeis on Twitter
- Explore contributing to the Deis project by joining the #deis channel on Freenode
You can learn about other ways to get involved on our website.