Deis 0.4.1 - Docker 0.7.6 and Fixes

4 Feb 2014

The Deis project is happy to announce our v0.4.1 release. This version updates Docker to v0.7.6 and fixes several issues.

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.4.1 Summary

Under the Hood

  • Updated to Docker 0.7.6
  • Updated knife-digital_ocean to 0.4.0
  • Updated celery, requests, and Sphinx python libraries

Bug Fixes

  • Fixed deis nodes:scale orphaning nodes on DigitalOcean
  • Fixed consistency in arg parsing for deis config:list and containers:list
  • Added "by path" option to interactive deis keys:add
  • Fixed handling of "--app" parameter in deis scale
  • Allow Deis to run from Vagrant dir with spaces in the path
  • Remove old chef keys on Deis base images
  • Install inotify-tools to Deis base images
  • Skip docker steps if it's already installed

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:

  • @niccolox - 12-factor persistence and Xen/OpenShift discussions
  • @nathansamson - several bug fixes and CLI improvements, lots of great feedback, custom domains PR
  • @shredder12 - Clarifications to Chef admins documentation
  • @thpham - proposal for DigitalOcean provisioning
  • @paulczar - Chef cleanup and fixes
  • @jfw - Significant typo fix in docs
  • @ksikka - Major bug hunting, tons of IRC help
  • @danscan - Bug finding
  • @tombh Bug fixes, pull requests, Deis services work, lots of IRC & GitHub support
  • @bacongobbler - Bug finding, Deis services design & implentation, IRC & GitHub support

What's Next?

  1. Containerization of Deis Components. Converting all the Deis components to Docker images is done and being tested in the containerize branch. This will result in a more modular system that's easier to deploy and manage.

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

  3. Interactive deis run Though we provide the ability to run admin commands inside containers, we don't currently support interactive shells into containers. We will soon.


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. You can review the initial implementation 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.

Posted in Deis v1 PaaS

triangle square circle

Did you enjoy this post?