Open Stack

All,

The container networking spec below has gone through a fairly significant design change in the past few days. To summarize, Magnum will not create any new network plugins or network-specific abstractions to support container networking. Instead, the spec suggests standardizing on libnetwork [4] and its associated Container Network Model to support a range of container networking implementations. The Magnum community intends to integrate with Kuryr [5] in the long-term and both communities are starting the integration planning process [6].

I would like to thank everyone who provided feedback on the spec. If you have provided feedback to earlier patch sets, I ask that you review the latest patch set and provide an updated vote. If you issue a -1 vote, please include specific feedback on what is needed for your +1/+2 vote.

[4] https://github.com/docker/libnetwork/blob/master/docs/design.md
[5] https://github.com/openstack/kuryr/blob/master/doc/source/design.rst
[6] https://etherpad.openstack.org/p/magnum-kuryr

Regards,
Daneyon

From: Cisco Employee <danehans at cisco.com<mailto:danehans at cisco.com>>
Date: Wednesday, July 22, 2015 at 9:40 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [Magnum] Container Networking Spec

All,

I have just submitted the container networking spec[1] for review. Thank you to everyone [2-3] who participated in contributing to the spec. If you are interested in container networking within Magnum, I urge you to review the spec and provide your feedback.

[1] https://review.openstack.org/#/c/204686
[2] http://eavesdrop.openstack.org/meetings/container_networking/2015/container_networking.2015-06-25-18.00.html
[3] http://eavesdrop.openstack.org/meetings/container_networking/2015/container_networking.2015-07-16-18.03.html

Regards,
Daneyon Hansen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150804/42358df4/attachment.html>