-
Notifications
You must be signed in to change notification settings - Fork 1.1k
0.4.0 Milestone Project Page
- 07/21/2015 - Code Freeze
- 08/04/2015 - Release
We plan to focus this release on quality
- P1 Fix fragile sub-components (issues reported after 0.3.0 release)
- P1 Parallel scheduling
- P1 Improve tests for the Mesos cluster driver
- P1 Add tests for leader election
We are going to improve the ops experience for Swarm.
- P2 Minimal front-end
- P3 Display labels in
docker psdocker/#12931
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 Integration of Swarm with Docker Networking.
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)
- P2 Rebalancing (depends on
Virtual Container ID) #599 - P2 Global scheduling (depends on
Virtual Container ID) #600
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 TTL handling in Discovery #611
- P3 Update the server side part to accept username / password and store them. #438
- P3 Update the client side part to send the username / password. #438
(29 Jun 2015 - 10 Jul 2015)
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.