-
Notifications
You must be signed in to change notification settings - Fork 1.1k
0.3.0 Milestone Project Page
- 05/26/2015 - Code Freeze
- 06/18/2015 - Release
####Multi-tenancy Regarding Swarm Multi-tenancy, we are working on shared states between multiple "soon-to-be-master" and master election.
- P1 Leader election [#598] (https://github.com/docker/swarm/issues/598)
- P1 Node removal #197
The builtin scheduler allows you to manage container on approximately hundreds of machines within a cluster. In the future, we want to allow third party tools to be plugged into Docker Swarm to allow management of much bigger clusters.
The work has started on defining the "cluster" interface in #393 The first integration will be Mesos but other tools will arrive after, like kubernetes.
- P1 Mesos Integration #214
####Scheduler Swarm comes with a builtin scheduler. It currently provides basic functionalities, such as scheduling containers based on constraints or affinity (co-scheduling of containers), persistent storage and multiple scheduling strategies like binpack or spread.
We plan to add more features to the builtin scheduler such as rebalancing (in case of host failure) and global scheduling (schedule containers on every node)
- P1 Swarm ID (depends on
labels
) #600
- P2 Rebalancing (depends on
Virtual Container ID
) #599 - P3 Global scheduling (depends on
Virtual Container ID
) #600
####Networking Scheduling and container placing is only part of the problem. In order for Swarm to be a good solution for distributed environments, we need to support multi-host networking.
- P1 Minimal integration of Swarm with Docker Networking.
####API Matching Swarm currently supports around 85% of the Docker API as you can see here
Our goal is to support 100% of Docker 1.6 API, so all the Docker CLI commands would work against Swarm
- P1 Bring Swarm API on par with Docker API as much as possible [#602] (https://github.com/docker/swarm/issues/602)
- P1 Use labels instead of env variable for constraints and affinity [#288] (https://github.com/docker/swarm/issues/288)
- P3 Display labels in
docker ps
docker/#12931
####Hosted Node Discovery Service
Right now, the tokens created via swarm create
aren't linked to any user/hub account. It should so we could at least, list the tokens you own in the hub interface.
- P1 Update the server side part to accept username / password and store them. #438
- P1 Update the client side part to send the username / password. #438
- P2 TTL handling in Discovery #611
(13 Apr 2015 - 24 Apr 2015)
Goal: Focus on the P1 items in each area.
- API
- Add support for
build
,load
andrename
- Migrate to labels
- Labels support in affinities #667
- Extensibility
- Experimental support of Mesos (work in progress).
- Multi-tenancy
- Started implementation of distributed storage through libkv (consul and etcd supported)
- Scheduler
- Initial implementation of rebalancing (naive).
- Quality
- Refactoring and cleanup of the API and CLI
- Make codebase pass golint
- Improve test coverage
- Add stress tests
- Covered most of the API by integration tests
(27 Apr 2015 - 08 May 2015)
- Goal: Focus on the P1 items in each area.
- API
- [VV/AL] Support registry authentication #684
- [VV] Support for
docker save
#739 - [AL] Support for
ps --filter
- Migrate to labels
- [VV] Use labels instead of environment variables to store state #673
- Extensibility
- [VV] Continue Mesos experimental integration
- Multi-tenancy
- [AB] Add support for Zookeeper in libkv
- [AB] Integrate libkv into Swarm and use it as its discovery backend
- [AL] Add support for Swarm IDs
- Discovery Service
- [VV] Authentication server side
- [VV] TTL server side
- Quality
- [AL] Automated integration tests
- [AL] Integration tests against Docker master
- [AL] Regression tests (manual)
(11 May 2015 - 22 May 2015)
- Goal: Finalize the features for the release
- Multi Tenancy
- Leader Election
- [AL] Algorithm
- [AL] API integration
- [AB] etcd
- [AB] zk
- [AL] consul
- Core
- Node removal
- [AB] Store TTL
- [VV] Token TTL
- [AL] Engine removal from Cluster
- [AL] Engine shutdown
- Discovery Service
- [AL/VV] Revisite token on-boarding process
- Extensibility
- [VV] Revisit per-cluster flags
- Reliability
- [AL] Make discovery fault-tolerant
(26 May 2015 - 5 Jun 2015)
- Goal: Finalize the release
Address all 0.3.0 P1 issues
- API
- [AL/VV] Support authenticated
docker run
- Mesos
- [VV] Test mesos in jenkins #894
- Discovery Service
- [VV] Authentication client side #695
(8 Jun 2015 - 19 Jun 2015)
- Release on 6/18/15
- 0.4.0 Planning
We use GitHub milestones to track issues and PRs for each release. You can see a list of milestones and related issues here: https://github.com/docker/swarm/milestones. Depending on urgency, importance, or demand for a feature/issue fix, we might move issues and PRs between milestones.