New things we’re working on… and how you can get involved

Docker London

- I used to run a company called Orchard in London building stuff around Docker- We were acquired by Docker this summer to establish the London office- We’re working on orchestration features on the Docker open source project, as well as some cool new things…- I don’t want to pitch but… Like Go? Want to work on an open source project? Well…

Open Design

- We’re experimenting with a new process for working on Docker- Open source companies are in this odd situation where our customers can influence the product directly by working on it- At the moment lots of development work is done behind closed doors or in places that are open but poorly organised like IRC channels- We want to make the design process open and easy to participate as possible- Separate out Docker, Inc and the open source project

- 50/50 split of PRs, but Docker, Inc is more likely to be merged- Docker, Inc happens to hire a lot of the contributors, but they will contribute to the open source project like any other company or individual- Open governance board- Specifically: Proposals process

- Rough, just making semi-official what was already happening- Whole load of issues we have to work through - openness, fairness, scope, etc- Some of the things we’re using this with…

Clusteringhttps://github.com/docker/docker/pull/8859

- Currently, Docker works really well on a single machine- API for single machine- Links, volumes on a single machine

- We want Docker to work out of the box on multiple machines- Will work a bit like starting a Docker daemon, but you connect it up to another Docker daemon- Docker remote API becomes the API for controlling your data centre- Implementation has not been decided upon yet

- We want something that works out of the box, but we also want to make it work with other clustering systems like Kubernetes, Mesos, etc- Probably some kind of plugin system, shipping with a simple bundled plugin

Grouping and Compositiona.k.a. “docker up”

https://github.com/docker/docker/issues/8637

- At Orchard, we made a tool called Fig for running development environments locally- This is the good bits of Fig worked into Docker- Another multiple things problem!- Docker’s UI works really well when you have a single container- Though >1, you have to fiddle with with command line opts, naming things, linking things… you’ll probably write a bash script- You should be able to define a file that says how multiple containers connect together then run them all with one command- Like Fig it just uses the Docker remote API, so it’ll be compatible with clustering

- it’ll Just Work across multiple machines

Host Managementhttps://github.com/docker/docker/issues/8681

- boot2docker is two things:- a hypervisor for running Docker containers- a command line tool for provisioning a boot2docker machine on Virtualbox so you can use Docker on OS X a way of running a Docker host on OS X

- We want to build the command line tool straight into Docker so you don’t have to think about a separate thing and mess around with environment variables to configure Docker

- Best way to explain it is with a demo…

Demo!

Get involvedFeedback, test builds, contribute code:

Clustering: http://git.io/r3tZnwComposition: http://git.io/N6tLrg

Host management: http://git.io/IlD7Qg

- This is not done yet! We don’t know whether it’s right and we want you to tell us what’s wrong and why it wouldn’t work for you.- Ways to get involved:

- Give feedback on the proposals and pull requests above- Test builds of the features- Write code! Open pull requests against feature branches.

Questions?@bfirsh

bfirsh@docker.com#docker-dev on Freenode