Skip to content
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.

1.0.0 Milestone Project Page

Jump to bottom
Victor Vieux edited this page Mar 30, 2015 · 14 revisions

Schedule

Date Item
05/12/2015 - draft Code Freeze; first Release Candidate
06/02/2015 - draft Release

Tracking

Release Goals

####Leader Election (Distributed State) Regarding Swarm Multi-tenancy, we are working on shared states between multiple "soon-to-be-master" and master election.

  • Shared state between multiple "nodes"
  • Node removal

Mesos Integration

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.

  • Mesos Integration POC

####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)

  • Virtual Container ID (depends on labels)
  • Rebalancing (depends on Virtual Container ID)
  • Global scheduling (depends on Virtual Container ID)

####API Matching Swarm currently supports around 85% of the Docker API as you can see here

Our goal is to support 100% of the API, so all the Docker CLI commands would work against Swarm

  • Bring Swarm API on par with Docker API as much as possible
  • Use labels instead of env variable for constraints and affinity
  • Open a few PRs on docker/docker to display labels in docker ps and docker images

####Hoster 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.

  • Update the server side part to accept username / password and store them.
  • Update the client side part to send the username / password.

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.

Resources

Clone this wiki locally