[ https://issues.apache.org/jira/browse/JCLOUDS-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Dancy closed JCLOUDS-782. ------------------------------------- Resolution: Fixed Assignee: Christopher Dancy Code was previously removed from jclouds-labs per my request as the project was dying down and being replaced by docker swarm (lead maintainer works for docker and the swarm project). > Add Shipyard provider > --------------------- > > Key: JCLOUDS-782 > URL: https://issues.apache.org/jira/browse/JCLOUDS-782 > Project: jclouds > Issue Type: New Feature > Components: jclouds-labs > Affects Versions: 2.0.0 > Environment: docker 1.3 > Shipyard 2.0.4 > Reporter: Christopher Dancy > Assignee: Christopher Dancy > Priority: Minor > Labels: Shipyard > > Add a provider for Shipyard to jclouds: > http://shipyard-project.com/ > Shipyard is a cloud for docker managment. It allows one to connect multiple > engines (docker daemons) to a single point. It has a UI, REST API, and > command line interface for interacting with nodes/containers. > The idea is to leverage what's already been done with jclouds (particularly > jclouds-docker) to implement the ComputeService. By doing so we will have a > common interface, via jclouds, with which to interact with Shipyard. > I'll take on the initial coding of this provider to get things up and going > (though anyone that wants to help is more than welcome). > Thoughts/opinions/ideas? -- This message was sent by Atlassian JIRA (v6.3.15#6346)