Deis 0.4.0 - Rollback and Auditing

15 Jan 2014

The Deis project is glad to announce our v0.4.0 release. This version adds better logging, more detailed release summaries, and the ability to roll back to a previous release.

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

New Features

  • deis logs now includes app lifecycle events
  • deis rollback creates a new release from a previous build and config
  • deis releases summarizes what changed in each release and when
  • Rackspace provider uses new, fast "performance" flavors
  • Added "customizing buildpacks" to FAQ

Under the Hood

  • Updated to Docker 0.7.5
  • Added a "Push" domain object en route to decoupling SSH/Git from controller
  • Updated boto, paramiko, psycopg2, and requests Python libs
  • Moved slugbuilder hook to deis repo from deis-cookbook

Bug Fixes

  • Fixed deis config always returning latest, not necessarily current
  • Fixed deis releases:info v1 ignoring optional version argument
  • Added "prepare new image" instruction and other improvements to Rackspace docs
  • Improvements to contrib/vagrant/
  • Return better error message in client on ConnectionError

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:

  • @stackedsax - Rackspace doc and code improvements, lots of great feedback
  • @joelvh - Fixed a typo
  • @ksikka - Testing, several GitHub issues, tons of great feedback
  • @tombh - Moved slugbuilder hook, CLI connection err message fix, vagrant doc improvements, much more help and support...and the amazing
  • @bacongobbler - Alpha of service discovery for Deis, major user support on IRC and GitHub

What's Next?

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

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


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.

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

Posted in Deis v1 PaaS

triangle square circle

Did you enjoy this post?