2015-11-05 21:30 GMT+09:00 Gal Sagie <[email protected]>: > The current OVS binding proposals are not for nested containers. > I am not sure if you are asking about that case or about the nested > containers inside a VM case. > > For the nested containers, we will use Neutron solutions that support this > kind of configuration, for example > if you look at OVN you can define "parent" and "sub" ports, so OVN knows to > perform the logical pipeline in the compute host > and only perform VLAN tagging inside the VM (as Toni mentioned)
I felt that the VLAN-aware VM effort affects many on-going efforts in Neutron stadium including Kuryr through the summit discussion. Let's keep your eyes on VLAN-aware VM effort and your feedback would be appreciated. The initial effort is found in https://review.openstack.org/#/c/210309/ (Trunk port: API extension). Akihiro > > If you need more clarification you can catch me on IRC as well and we can > talk. > > On Thu, Nov 5, 2015 at 8:03 AM, Vikas Choudhary <[email protected]> > wrote: >> >> Hi All, >> >> I would appreciate inputs on following queries: >> 1. Are we assuming nova bm nodes to be docker host for now? >> >> If Not: >> - Assuming nova vm as docker host and ovs as networking plugin: >> This line is from the etherpad[1], "Eachdriver would have an >> executable that receives the name of the veth pair that has to be bound to >> the overlay" . >> 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 ? >> >> Query 2: Are we having double encapsulation(both at vm and >> compute)? Is not it possible to bind vif into compute host br-int? >> >> 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? >> >> >> [1] https://etherpad.openstack.org/p/Kuryr_vif_binding_unbinding >> [2] https://review.openstack.org/#/c/241558/ >> [3] https://review.openstack.org/#/c/232948/1 >> [4] https://review.openstack.org/#/c/227972/ >> >> >> -Vikas Choudhary >> >> __________________________________________________________________________ >> 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 > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
