I've reached out to the docker team, spoken to the GM of cloud for Amazon and passed on the feedback (as well as asking a bunch of questions on the API). I'm also talking to the head of product for Joyent tonight and get some feedback on the Triton API.
as well as posting on the docker reddit channel (+upvote please) https://www.reddit.com/r/docker Ant On Tue, Jan 5, 2016 at 7:28 PM, Sebastien Goasguen <run...@gmail.com> wrote: > >> On Jan 4, 2016, at 11:55 AM, Tomaz Muraus <to...@apache.org> wrote: >> >> I think it would also be good to get some feedback from the docker and rkt >> community. >> >> We should send an email with background information and all the context >> needed and ask them for feedback :) > > sent couple tweets to get some feedback > >> On Jan 3, 2016 6:48 PM, "anthony shaw" <anthony.p.s...@gmail.com> wrote: >> >>> Hi Everyone, >>> >>> I've had some time to work on this over the holidays. So this PR is >>> now "code complete", please spend some time reviewing: >>> >>> https://github.com/apache/libcloud/pull/666 >>> >>> note I have included sample drivers for Docker, Joyent Triton and Amazon >>> ECS. >>> >>> I would like us to ship this in the next release as an 'experimental' >>> driver and get some feedback from the community. >>> >>> Regards, >>> Anthony >>> >>> On Wed, Dec 23, 2015 at 11:05 AM, anthony shaw <anthony.p.s...@gmail.com> >>> wrote: >>>> Since the consensus was #3. I've started work on a container driver >>>> type, refactoring the original docker Node driver into a Container >>>> driver. >>>> >>>> https://github.com/apache/libcloud/pull/666 >>>> >>>> Please review and comment as necessary. >>>> >>>> Ant >>>> >>>> On Fri, Dec 18, 2015 at 3:37 AM, Eric Johnson <erjoh...@apache.org> >>> wrote: >>>>> +1 to #3 >>>>> >>>>> On Thu, Dec 17, 2015 at 8:31 AM, <philip.kers...@stfc.ac.uk> wrote: >>>>> >>>>>> Hi Sebastien, all, >>>>>> >>>>>> This would be a great development - good to see :) >>>>>> >>>>>> I agree option 3) looks the best. >>>>>> >>>>>>> >>>>>>> It makes sense if we think that various API are going to emerge for >>>>>> containers. In libcloud philosophy, we would provide a single common >>> API >>>>>> for various container runtime. >>>>>>> >>>>>>> We would need to check the OCI to see if an API is being discussed >>>>>> there. Docker has is, and it seems rkt is now providing one: >>>>>>> https://github.com/coreos/rkt/blob/master/api/v1alpha/api.proto >>>>>>> >>>>>>> LXD has a different one: >>>>>>> https://github.com/lxc/lxd/blob/master/specs/rest-api.md >>>>>>> >>>>>>> Providing a wrapper for these might be interesting and coherent with >>>>>> what libcloud has provided so far. >>>>>>> >>>>>> Have you considered wrappers to Kubernetes, Swarm or Marathon? >>>>>> >>>>>> Cheers, >>>>>> Phil >>>>>> >>>>>> >>> >
