Deis 0.2.0 - DigitalOcean Support & Installation Docs
The Deis project is psyched to announce our v0.2.0 release. We've added support for DigitalOcean Cloud, improved our Installation docs, updated Chef, and fixed many issues found by the Deis community.
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.
- DigitalOcean Cloud provider support
- New Installation docs for EC2, Rackspace, and DigitalOcean
- Updated controller web UI
Under the Hood
- Chef updated to v.11.6.2
- Updated some Ruby and Chef libraries
- Updated EC2 AMIs for faster provisioning
- Fixed socket.hostname issue that prevented controller restart
deis opentext output
git push deis masterbug with PHP buildpack
deis logssometimes returning 404s
- Fixed issues with
deis createand explicit --id flag
We want to thank the following Deis community members for creating GitHub issues, providing support to others, and working on various Deis branches:
- @bacongobbler - DigitalOcean has arrived, and it's thanks to his hard work. Try it out! And Matt's continued help on IRC and GitHub is invaluable.
- @enyachoke - Vagrant support request and feedback.
- @tombh - Vagrant support--with
deis nodes:scale--seemed nearly impossible, but Tom found a way. This will land in master soon and enable testing and development on Deis without any cloud provider charges.
- @scottstamp - Bug finding, bug fixing!
- @jeff-french - Testing and feature requests.
- @zodman, @mkuklis, @BrianHicks,@ianthedeveloper, @wiemann, @arkan, @luislavena, @cpursley, @nikolay, @Qard, @wingrunr21, @kylefinley, @phildini, @Imdsm - DigitalOcean testing and feedback.
- Vagrant provider. Allowing Deis to run on a completely local "cloud" will enable developers to test and improve Deis without incurring any provider charges. This works in a "static" node formation currently, but @tombh has a complete Vagrant provider implementation branch that is currently in testing.
- Team Support / Sharing. The mechanisms for sharing Formations and Apps are already implemented in a branch; we need to write more tests, implement some access control endpoints and make some changes to the gitosis data bag.
- Improved Documentation There are a few items that require better documentation including how to setup a static formation on bare metal. We also need to provide a Tutorial that walks through advanced usage of the CLI, including how to create custom layers.
Enhanced Docker Integration
Deis currently uses Docker as a LXC wrapper for running Heroku Buildpack slugs that are bind-mounted into Buildstep images. As soon as the Docker Private Registry code stabilizes, we will be adding a new
git push build process that creates and distributes images via
Dockerfile and a private registry hosted on the controller.
General Security Improvements
Both the controller and formation proxies 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. If you find any other security holes, please open a GitHub issue and tag it "Security".
We do not currently monitor nodes or container health -- though we have infrastructure in place to do it.
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.
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.