github.com/fanux/shipyard@v0.0.0-20161009071005-6515ce223235/roadmap.md (about)

     1  # Roadmap
     2  
     3  ## Shipyard 3.0
     4  This is the next major version of Shipyard.  There is quite a bit planned and
     5  some of the features may get bumped to next incremental versions.
     6  
     7  ### Docker Swarm Integration
     8  When we started v2, libswarm was still very early.  We knew that we wanted to
     9  have cluster capability without hitting each individual Docker API.  Now that
    10  Swarm is here (and is awesome btw) we want to replace the existing backend
    11  with Swarm.  With that will come improved scheduling, full support of Docker
    12  features (i.e. `docker run --rm` etc) and less maintenance enabling us to focus
    13  on Shipyard itself.
    14  
    15  ### Docker Registry
    16  There has been lots of interest in managing a private Docker Registry.  Shipyard v3 will contain registry management including managing and deploying from repositories.
    17  
    18  ### Interlock
    19  This will bring the "composable" management to Shipyard.  Interlock has a plugin system that allows the selection of plugins including application routing and load balancing to stats and more.  These can be enabled / disabled at user discretion.
    20  
    21  ### Docker Machine Integration
    22  This would enable provisioning of Docker Engines in all providers supported by Machine.  These nodes could then be used to create or scale a Swarm cluster.
    23  
    24  ### Docker Compose Integration
    25  There has been a long standing request for 
    26  [Docker Compose](https://github.com/docker/fig) (Fig) integration 
    27  (https://github.com/shipyard/shipyard/issues/172 & 
    28  https://github.com/shipyard/shipyard/issues/270).
    29  We want enable deploying containers from Docker Compose configuration definitions.