<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 21, 2015 at 8:04 AM, Fox, Kevin M <span dir="ltr"><<a href="mailto:Kevin.Fox@pnnl.gov" target="_blank">Kevin.Fox@pnnl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
Since docker 1.7 is suposed to support advanced networking, could that just be plugged into neutron?<br></div></blockquote><div> <br>Yes, we'd be looking at doing a docker libnetwork driver that uses the remote driver interface.<br></div><div> <br>The
remote driver would request the ports/networks to neutron and then use
that information and the port type to plug the port into the container
in the appropriate way.<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
Thanks,<br>
Kevin <b>
<div><font face="Tahoma" color="#000000" size="2"> </font></div>
</b>
<hr>
<font face="Tahoma" size="2"><b>From:</b> Brenden Blanco<br>
<b>Sent:</b> Thursday, May 21, 2015 6:40:37 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Neutron][Magnum] Container + OpenStack Integration<br>
</font><div><div class="h5"><br>
<div></div>
<div>
<div dir="ltr">Hi,
<div><br>
</div>
<div>Just brainstorming here, but IMHO it would be good to keep it extensible and not to lock in VLAN as the sole container "VIF" mechanism. For instance, there is the ipvlan [1] technology that was purpose-built to be more appropriate for container systems.
This tech actually comes from some of the Google folks that deploy containers at scale, if my memory serves correctly. So, we may want to start with VLAN as the reference implementation but should leave it open to try out an alternative such as the above in
the near future. Perhaps in practice this implies that the vid field of the neutron side isn't strictly an int field, not sure.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Brenden Blanco</div>
<div><br>
</div>
<div>[1] <a href="https://lwn.net/Articles/620087/" target="_blank">https://lwn.net/Articles/620087/</a></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, May 20, 2015 at 11:21 PM, Kevin Benton <span dir="ltr">
<<a href="mailto:blak111@gmail.com" target="_blank">blak111@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I wasn't able to make it to the session but from the etherpad I saw<br>
that the VLAN-aware VMs mentioned there. Would that be enough to cover<br>
this particular use-case?<br>
<span><br>
On Wed, May 20, 2015 at 3:28 AM, Adrian Otto <<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.com</a>> wrote:<br>
> Magnum and Neutron Teams,<br>
><br>
> If you are in Vancouver today and can help design or implement native<br>
> networking support to obviate the need for overlay networks when using<br>
> containers, please join this design session:<br>
><br>
> <a href="http://sched.co/3CjK" target="_blank">http://sched.co/3CjK</a> (3:30 PM, Room 303)<br>
><br>
> This will be based on feedback gathered at the Fishbowl session earlier in<br>
> the day: <a href="http://sched.co/3B0z" target="_blank">http://sched.co/3B0z</a> (11:00 AM, Room 306)<br>
><br>
> Thanks,<br>
><br>
> Adrian<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
<br>
</span><span><font color="#888888">--<br>
Kevin Benton<br>
</font></span>
<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" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</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" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>