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

0.3.0 Milestone Project Page

Andrea Luzzardi edited this page Apr 22, 2015 · 51 revisions

Schedule


  • 05/26/2015 - Code Freeze
  • 06/16/2015 - Release

0.3.0 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.

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.

  • P2 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 Virtual Container 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.

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

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

Sprint Goals


Sprint 14

(13 Apr 2015 - 24 Apr 2015)

  • Focus on the P1 items in each area.

Tracking