Deis 0.2.1 - Full Vagrant Support, More Bug Fixes

26 Nov 2013

The Deis project is pleased to announce our v0.2.1 release. We've improved support for local testing with Vagrant, added "bare metal" documentation, 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.

0.2.1 Summary

New Features

  • Full Vagrant provider support (0.2.0 supported a limited configuration)
  • New Installation docs for "bare metal" nodes

Under the Hood

  • Updated EC2 AMIs and Vagrant .box for faster provisioning
  • Simplified credentials discovery code
  • Updated to latest progrium/buildstep with Ruby and PHP fixes
  • Better isolation in client/tests test suite

Bug Fixes

  • Increased nginx server_names_hash_bucket_size to fix multiple app hosting
  • Raise exception when not authorized to delete Chef node/client
  • Ignore Chef 404s when destroying a node
  • Fixed user entry being orphaned in deis-users Chef data bag
  • Fixed old documentation being orphaned at rtfd.org
  • Improved deis run before git push error message
  • Fixed example-go app 502: Bad Gateway error
  • Improved prompt after deis nodes:scale dev runtime=0

Community Shout-Outs

We want to thank the following Deis community members for creating GitHub issues, providing support to others, and working on various Deis branches:

  • @tombh - Tom took the training wheels off our Vagrant provider support and turned it into the preferred way to test and develop Deis. This has literally saved us money--thanks Tom! And he has many more great ideas up his sleeve...
  • @nightshade427 - Fixed virtualenv python invocation in buildstep-hook and some promising chat about Linode support.
  • @jfairbairn, @ianthedeveloper - Vagrant.box download error catch and testing.
  • @alexandrz - DigitalOcean testing
  • @malandrew - Found registration error when missing URL schema, requested alternate AWS_* var support
  • @bacongobbler - Improved DigitalOcean error messages, helped with commentary on many issues, tons of IRC and GitHub support as always. Thanks Matt!

What's Next?

  1. 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.
  2. Docker 0.7.0 Integration. The new Docker fixes several issues and removes a dependency on AUFS that may allow Deis to run on more flavors of Linux.
  3. 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.

Future

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".

Health Checks

We do not currently monitor nodes or container health -- though we have infrastructure in place to do it.

Service Registry

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.

Posted in Deis v1 PaaS

triangle square circle

Did you enjoy this post?