1. docker
  2. Commit 2ea29ce0ef5bd507497fe65d2507bc6ff52fd9fb
Browse code

hack/ROADMAP.md: a high-level roadmap. Make a pull request to suggest changes

Solomon Hykes authored on 2013/06/06 00:26:26
Showing 1 changed files
hack/ROADMAP.md
History View file @ 2ea29ce
1 1 
new file mode 100644
... ... 
@@ -0,0 +1,88 @@
0 
+# Docker: what's next?
1 
+
2 
+This document is a high-level overview of where we want to take Docker next.
3 
+It is a curated selection of planned improvements which are either important, difficult, or both.
4 
+
5 
+For a more complete view of planned and requested improvements, see [the Github issues](https://github.com/dotcloud/docker/issues).
6 
+
7 
+Tu suggest changes to the roadmap, including additions, please write the change as if it were already in effect, and make a pull request.
8 
+
9 
+Broader kernel support
10 
+----------------------
11 
+
12 
+Our goal is to make Docker run everywhere, but currently Docker requires [Linux version 3.8 or higher with lxc and aufs support](http://docs.docker.io/en/latest/installation/kernel.html). If you're deploying new machines for the purpose of running Docker, this is a fairly easy requirement to meet.
13 
+However, if you're adding Docker to an existing deployment, you may not have the flexibility to update and patch the kernel.
14 
+
15 
+Expanding Docker's kernel support is a priority. This includes running on older kernel versions,
16 
+but also on kernels with no AUFS support, or with incomplete lxc capabilities.
17 
+
18 
+
19 
+Cross-architecture support
20 
+--------------------------
21 
+
22 
+Our goal is to make Docker run everywhere. However currently Docker only runs on x86_64 systems.
23 
+We plan on expanding architecture support, so that Docker containers can be created and used on more architectures.
24 
+
25 
+
26 
+Even more integrations
27 
+----------------------
28 
+
29 
+We want Docker to be the secret ingredient that makes your existing tools more awesome.
30 
+Thanks to this philosophy, Docker has already been integrated with
31 
+[Puppet](http://forge.puppetlabs.com/garethr/docker),  [Chef](http://www.opscode.com/chef),
32 
+[Openstack Nova](https://github.com/dotcloud/openstack-docker), [Jenkins](https://github.com/georgebashi/jenkins-docker-plugin),
33 
+[DotCloud sandbox](http://github.com/dotcloud/sandbox), [Pallet](https://github.com/pallet/pallet-docker),
34 
+[Strider CI](http://blog.frozenridge.co/next-generation-continuous-integration-deployment-with-dotclouds-docker-and-strider/)
35 
+and even [Heroku buildpacks](https://github.com/progrium/buildstep).
36 
+
37 
+Expect Docker to integrate with even more of your favorite tools going forward, including:
38 
+
39 
+* Alternative storage backends such as ZFS, LVM or [BTRFS](github.com/dotcloud/docker/issues/443)
40 
+* Alternative containerization backends such as [OpenVZ](http://openvz.org), Solaris Zones, BSD Jails and even plain Chroot.
41 
+* Process managers like [Supervisord](http://supervisord.org/), [Runit](http://smarden.org/runit/), [Gaffer](https://gaffer.readthedocs.org/en/latest/#gaffer) and [Systemd](http://www.freedesktop.org/wiki/Software/systemd/)
42 
+* Build and integration tools like Make, Maven, Scons, Jenkins, Buildbot and Cruise Control.
43 
+* Configuration management tools like [Puppet](http://puppetlabs.com), [Chef](http://www.opscode.com/chef/) and [Salt](http://saltstack.org)
44 
+* Personal development environments like [Vagrant](http://vagrantup.com), [Boxen](http://boxen.github.com/), [Koding](http://koding.com) and [Cloud9](http://c9.io).
45 
+* Orchestration tools like [Zookeeper](http://zookeeper.apache.org/), [Mesos](http://incubator.apache.org/mesos/) and [Galaxy](https://github.com/ning/galaxy)
46 
+* Infrastructure deployment tools like [Openstack](http://openstack.org), [Apache Cloudstack](http://apache.cloudstack.org), [Ganeti](https://code.google.com/p/ganeti/)
47 
+
48 
+
49 
+Plugin API
50 
+----------
51 
+
52 
+We want Docker to run everywhere, and to integrate with every devops tool.
53 
+Those are ambitious goals, and the only way to reach them is with the Docker community.
54 
+For the community to participate fully, we need an API which allows Docker to be deeply and easily customized.
55 
+
56 
+We are working on a plugin API which will make Docker very, very customization-friendly.
57 
+We believe it will facilitate the integrations listed above - and many more we didn't even think about.
58 
+
59 
+Let us know if you want to start playing with the API before it's generally available.
60 
+
61 
+
62 
+Externally mounted volumes
63 
+--------------------------
64 
+
65 
+In 0.3 we [introduced data volumes](https://github.com/dotcloud/docker/wiki/Docker-0.3.0-release-note%2C-May-6-2013#data-volumes),
66 
+a great mechanism for manipulating persistent data such as database files, log files, etc.
67 
+
68 
+Data volumes can be shared between containers, a powerful capability [which allows many advanced use cases](http://docs.docker.io/en/latest/examples/couchdb_data_volumes.html). In the future it will also be possible to share volumes between a container and the underlying host. This will make certain scenarios much easier, such as using a high-performance storage backend for your production database,
69 
+making live development changes available to a container, etc.
70 
+
71 
+
72 
+Better documentation
73 
+--------------------
74 
+
75 
+We believe that great documentation is worth 10 features. We are often told that "Docker's documentation is great for a 2-month old project".
76 
+Our goal is to make it great, period.
77 
+
78 
+If you have feedback on how to improve our documentation, please get in touch by replying to this email,
79 
+or by [filing an issue](https://github.com/dotcloud/docker/issues). We always appreciate it!
80 
+
81 
+
82 
+Production-ready
83 
+----------------
84 
+
85 
+Docker is still alpha software, and not suited for production.
86 
+We are working hard to get there, and we are confident that it will be possible within a few months.
87 
+