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 need to set this as a future task for us)
But we also need to understand the use cases for supporting these API's so we can address them and give them priorities (and this is something we as a community need to decide how to handle). For your question, given that we have network isolation and security from neutron API's and given we have NAT support (by Neutron API and the plugins implementing the network) , what do you see as a use case to use the port-mapping ? I welcome you and everyone else to raise and describe these use cases so the Neutron/Kuryr community can think how to solve and help, and if needed also adjust or add extensions for support. Thanks Gal. On Fri, Aug 14, 2015 at 7:28 AM, feisky <[email protected]> wrote: > 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. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Best Regards , The G.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
