[openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

2015-08-15 Thread Antoni Segura Puimedon
On Fri, Aug 14, 2015 at 5:36 PM, Adrian Otto adrian.o...@rackspace.com wrote: That's clear, thanks Gal. The feature benchmark should be parity with how the majority of other (complete) remote drivers for libnetwork behave. From a Magnum perspective we value consistency from an end user

Re: [openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

2015-08-14 Thread Gal Sagie
Hi feisky, I think thats a great question, not because of port-mapping in particular :) but because we need to think on a feature by feature basis and map all the features the dockers API allow which we cannot support directly with Neutron API or its services sub-projects API. (apuimedo, maybe we

Re: [openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

2015-08-14 Thread Adrian Otto
The port mapping feature is the -p flag on the docker run command. It determines which ports in the network namespace of the container are exposed to the root namespace. It configures iptables rules and docker proxy capabilities to achieve the desired result. This feature is essential, so we

Re: [openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

2015-08-14 Thread Gal Sagie
Hi Adrian, Thanks for the explanation, i agree with you that we shouldn't break anything useful in docker, but from what i understand (and please correct me if i am wrong) you are describing an implementation detail of docker networking (at its default current state). Kuryr is not an

Re: [openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

2015-08-14 Thread Adrian Otto
That's clear, thanks Gal. The feature benchmark should be parity with how the majority of other (complete) remote drivers for libnetwork behave. From a Magnum perspective we value consistency from an end user perspective when you use containers on OpenStack compared to when you run them outside

Re: [openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

2015-08-14 Thread Dmitry
I would suggest considering docker port mapping as a creation of an apropriate security group's rule and also creation of something which was never exist in Neutron before which will be responsible for port forwarding. This feature could be useful for VMs also instead of/jointly with using

[openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

2015-08-13 Thread Adrian Otto
Kyle, Can we please arrange for an official design specification for Kuyyr so members of the Magnum team can relay input to be sure that our mutual interests in this work are addressed? Thanks, Adrian __ OpenStack

Re: [openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

2015-08-13 Thread Kyle Mestery
On Thu, Aug 13, 2015 at 1:56 PM, Adrian Otto adrian.o...@rackspace.com wrote: Kyle, Can we please arrange for an official design specification for Kuyyr so members of the Magnum team can relay input to be sure that our mutual interests in this work are addressed? I agree 100%. See Gals

Re: [openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

2015-08-13 Thread feisky
Will Kuryr supports docker's port-mapping? -- View this message in context: http://openstack.10931.n7.nabble.com/neutron-kuryr-magnum-Design-Specification-for-Kuryr-tp82256p82299.html Sent from the Developer mailing list archive at Nabble.com.

Re: [openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

2015-08-13 Thread Gal Sagie
Sure, will have it ready for review next week and put the link here for everyone. On Thu, Aug 13, 2015 at 10:17 PM, Kyle Mestery mest...@mestery.com wrote: On Thu, Aug 13, 2015 at 1:56 PM, Adrian Otto adrian.o...@rackspace.com wrote: Kyle, Can we please arrange for an official design