<div dir="ltr">Thanks Daneyon for raising the integration in your IRC meeting and for starting the ether pad. (i hope to attend your next online meeting)<div>As requested i will start writing a detailed spec about Kuryr where everyone can add and comment.</div><div>We already have a basic design document [1] describing the mapping model to Neutron API. (thanks to Taku)</div><div><br></div><div>We haven't made any hard decisions design wise, we have our goals and roadmap but we are at a learning period</div><div>where we want to learn and understand the use cases and missing parts in Neutron and in Containers networking to address them.</div><div>I believe (and i am sure the rest of Kuryr team agrees) that Magnum use cases and integration is top priority for us and we want</div><div>to learn and work together with you guys.</div><div><br></div><div>At this stage we are focusing on mapping Kuryr to Neutron for host containers networking (and all the configuration</div><div>options needed for that) and building containerised Neutron plugins (form existing plugins) </div><div>with Kuryr adding the missing parts (VIF-binding the container to the networking infrastructure).</div><div><br></div><div>It is obvious that this same solution can be applied to nested VM, but as you mentioned in the IRC talk</div><div>this has its overhead and we want to provide agent less solution which fits Magnum use cases.</div><div><br></div><div>Its important to note that Neutron doesn't nessaccraily mean the OVS-L2 Agent, this is just one implementation of Neutron</div><div>and we already have Neutron implementations which support the use cases of containers in nested VM's</div><div>(And i am sure more will come in the future like Midonet)</div><div><br></div><div>For example if we look at OVN (which has Neutron plugin): (and i have CC'ed shettyg from VMware which works on that for corrections/additions)</div><div><br></div><div>We can configure container ports in OVN that are in a nested VM (with a parent-port) and attach these ports</div><div>to any logical Neutron network we desire (which can be different from the port of the VM), OVN in the host will make sure to apply</div><div>all the needed logic in the host and in the VM docker only need to attach the container port to OVS bridge with the correct VLAN</div><div>(Which is dynamically allocated by Neutron/OVN plugin).</div><div><br></div><div>I tried to keep this description minimal here but you can read more about it in my blog [2] and also i intend to describe </div><div>this in more detail in the spec.</div><div>We want to formalise his part with Kuryr to fit other solutions as well (and future solutions) and adjust Neutron missing parts, and i believe with something like that Magnum</div><div>can leverage nested containers without the overhead of agent in the VM (Magnum or Kuryr at this point will need to just provide the binding and VLAN attachment in the VM)</div><div><br></div><div>Hope that make sense and lets continue iterating in IRC/over email and in Kuryr spec which i will provide next week.</div><div><br></div><div>Feel free to share any thoughts/comments you have on this</div><div><br></div><div>[1] <a href="https://github.com/openstack/kuryr/blob/master/doc/source/design.rst">https://github.com/openstack/kuryr/blob/master/doc/source/design.rst</a></div><div>[2] <a href="http://galsagie.github.io/sdn/openstack/ovs/2015/04/26/ovn-containers/">http://galsagie.github.io/sdn/openstack/ovs/2015/04/26/ovn-containers/</a></div><div> <br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 13, 2015 at 10:16 PM, Daneyon Hansen (danehans) <span dir="ltr"><<a href="mailto:danehans@cisco.com" target="_blank">danehans@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div><br>
</div>
<div>The Magnum Networking Subteam just concluded our weekly meeting. Feel free to review the logs[1], as Kuryr integration was an agenda topic that drew considerable discussion. An etherpad[2] has been created to foster collaboration on the topic. Kuryr integration
is scheduled as a topic for next week’s agenda. It would be a big help if the Kuryr team can review the etherpad and have representation during next week's meeting[3]. I look forward to our continued collaboration.</div>
<div><br>
</div>
<div>[1] <a href="http://eavesdrop.openstack.org/meetings/container_networking/2015/container_networking.2015-08-13-18.00.log.txt" target="_blank">http://eavesdrop.openstack.org/meetings/container_networking/2015/container_networking.2015-08-13-18.00.log.txt</a></div>
<div>[2] <a href="https://etherpad.openstack.org/p/magnum-kuryr" target="_blank">https://etherpad.openstack.org/p/magnum-kuryr</a></div>
<div>[3] <a href="https://wiki.openstack.org/wiki/Meetings/Containers#Container_Networking_Subteam_Meeting" target="_blank">https://wiki.openstack.org/wiki/Meetings/Containers#Container_Networking_Subteam_Meeting</a></div>
<div><br>
</div>
<div>
<div>Regards,</div>
<div>Daneyon Hansen</div>
<div></div>
</div>
</div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Best Regards ,<br><br>The G. </div>
</div>