* Removing the hard dependency on Chef
* Integrating with an enterprise-grade scheduler (possibly Mesos)
If you have any questions, I'm happy to field them here.
Thanks guys for a great product, for being patient with us :) and for your help improving the Docker community!
Look out for more pull requests to the registry! :)
Though, I kinda wonder. When scaling web instances, does it provision a new machine per instance?
Also, how do I do something like create backing services?
We host application instances in Docker containers, so each instance is essentially a container on a VM. We have a very basic scheduler implementation (read: round-robin) that deploys the containers evenly across nodes under the Runtime Layer. As gabrtv mentions in another comment, we are looking to replace this scheduler with something more sophisticated like Apache Mesos.
As for creating backing services, we are looking to implement a service registry where it would communicate with third-party services much like how Heroku Addons work. For the moment, most users set an environment variable for their application as per the docs: http://docs.deis.io/en/latest/developer/manage-application/#...