<div dir="ltr"><div>@Gal, I was asking about "container in nova vm" case.</div><div>Not sure if you were referring to this case as nested containers case. I guess nested containers case would be "containers inside containers" and this could be hosted on nova vm and nova bm node. Is my understanding correct?</div><div><br></div><div>Thanks Gal and Toni, for now i got answer to my query related to "container in vm" case. <br></div><div><br></div><div>-Vikas</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 5, 2015 at 6:00 PM, Gal Sagie <span dir="ltr"><<a href="mailto:gal.sagie@gmail.com" target="_blank">gal.sagie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>The current OVS binding proposals are not for nested containers.<br></div>I am not sure if you are asking about that case or about the nested containers inside a VM case.<br><br></div>For the nested containers, we will use Neutron solutions that support this kind of configuration, for example<br></div>if you look at OVN you can define "parent" and "sub" ports, so OVN knows to perform the logical pipeline in the compute host<br></div>and only perform VLAN tagging inside the VM (as Toni mentioned)<br></div><br></div>If you need more clarification you can catch me on IRC as well and we can talk.<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Thu, Nov 5, 2015 at 8:03 AM, Vikas Choudhary <span dir="ltr"><<a href="mailto:choudharyvikas16@gmail.com" target="_blank">choudharyvikas16@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hi All,<div><br></div><div>I would appreciate inputs on following queries:</div><div>1. Are we assuming nova bm nodes to be docker host for now? </div><div><br></div><div>If Not:</div><div> - Assuming nova vm as docker host and ovs as networking plugin:</div><div> This line is from the etherpad[1], "<span style="color:rgb(0,0,0);font-family:'Helvetica Neue',Arial,sans-serif;font-size:12px;line-height:16px;background-color:rgb(188,236,200)">Eachdriver would have an executable that receives the name of the veth pair that has to be bound to the overlay</span>" .</div><div> Query 1: As per current ovs binding proposals by Feisky[2] and Diga[3], vif seems to be binding with br-int on vm. I am unable to understand how overlay will work. AFAICT , neutron will configure br-tun of compute machines ovs only. How overlay(br-tun) configuration will happen inside vm ?</div><div> </div><div> Query 2: Are we having double encapsulation(both at vm and compute)? Is not it possible to bind vif into compute host br-int?</div><div> </div><div> Query3: I did not see subnet tags for network plugin being passed in any of the binding patches[2][3][4]. Dont we need that?</div><div><br></div><div><br></div><div>[1] <a href="https://etherpad.openstack.org/p/Kuryr_vif_binding_unbinding" target="_blank">https://etherpad.openstack.org/p/Kuryr_vif_binding_unbinding</a></div><div>[2] <a href="https://review.openstack.org/#/c/241558/" target="_blank">https://review.openstack.org/#/c/241558/</a></div><div>[3] <a href="https://review.openstack.org/#/c/232948/1" style="text-decoration:none;color:rgb(6,84,172);font-family:sans-serif" target="_blank">https://review.openstack.org/#/c/232948/1</a></div><div><span style="color:rgb(0,0,0);font-family:sans-serif">[4] </span><font color="#000000" face="sans-serif"><a href="https://review.openstack.org/#/c/227972/" target="_blank">https://review.openstack.org/#/c/227972/</a></font><span style="color:rgb(0,0,0);font-family:sans-serif"> </span></div><span><font color="#888888"><div><br></div><div><br></div><div>-Vikas Choudhary</div></font></span></div>
<br></div></div><span class="">__________________________________________________________________________<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></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><div>Best Regards ,<br><br>The G. </div>
</font></span></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></div>