Hi Russell, Is there any material to explain how OVN parent port work?
Thanks, Tony -----Original Message----- From: WANG, Ming Hao (Tony T) Sent: Wednesday, September 23, 2015 10:02 AM To: OpenStack Development Mailing List (not for usage questions) Subject: RE: [openstack-dev] [neutron] Does neutron ovn plugin support to setup multiple neutron networks for one container? Russell, Thanks for your info. If I want to assign multiple interfaces to a container on different neutron networks(for example, netA and netB), is it mandatory to let the VM hosting containers have network interfaces in netA and netB, and ovn will help to direct the container traffic to its corresponding VM network interfaces? from https://github.com/openvswitch/ovs/blob/master/ovn/CONTAINERS.OpenStack.md : "This VLAN tag is stripped out in the hypervisor by OVN." I suppose when the traffic goes out the VM, the VLAN tag has already been stripped out. When the traffic arrives ovs on physical host, it will be tagged with neutron local vlan. Is it right? Thanks in advance, Tony -----Original Message----- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: Wednesday, September 23, 2015 12:46 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Does neutron ovn plugin support to setup multiple neutron networks for one container? On 09/22/2015 08:08 AM, WANG, Ming Hao (Tony T) wrote: > Dear all, > > For neutron ovn plugin supports containers in one VM, My understanding is one > container can't be assigned two network interfaces in different neutron > networks. Is it right? > The reason: > 1. One host VM only has one network interface. > 2. all the VLAN tags are stripped out when the packet goes out the VM. > > If it is True, does neutron ovn plugin or ovn has plan to support this? You should be able to assign multiple interfaces to a container on different networks. The traffic for each interface will be tagged with a unique VLAN ID on its way in and out of the VM, the same way it is done for each container with a single interface. -- Russell Bryant __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
