Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Cool. That works. On Mon, Oct 5, 2015 at 9:05 AM, Russell Bryant wrote: > On 10/05/2015 04:28 PM, Murali R wrote: > > Yes. So we can define multiple logical switches per network and ovn > > keeps vlan maps that ovs agent used to maintain and do the tunneling. My > >

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Yes. So we can define multiple logical switches per network and ovn keeps vlan maps that ovs agent used to maintain and do the tunneling. My confusion was from lport-add command that did not have host info, so if there is no neutron, the cms has to maintain the host to lport association and we

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 10/05/2015 04:28 PM, Murali R wrote: > Yes. So we can define multiple logical switches per network and ovn > keeps vlan maps that ovs agent used to maintain and do the tunneling. My > confusion was from lport-add command that did not have host info, so if > there is no neutron, the cms has to

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/27/2015 04:18 PM, Russell Bryant wrote: > On 09/27/2015 06:50 AM, Kevin Benton wrote: >> Assuming it implements the normal provider networks API, you just >> specify the segmentation_id when you create the network. >> >> neutron net-create NET_NAME --provider:network_type vlan >>

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Hi Russell, Thank you these are really good. Had a quick question. When you create a logical switch in your first script (line 23) - at what point is it associated with br-int ? Is it on line 45? So I can create any switch and when I associated logical port it associates logical switch ? Or is

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 10/02/2015 02:26 PM, Murali R wrote: > Hi Russell, > > Thank you these are really good. Had a quick question. When you create a > logical switch in your first script (line 23) - at what point is it > associated with br-int ? Is it on line 45? So I can create any switch > and when I associated

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/30/2015 06:01 PM, Murali R wrote: > Yes, sfc without nsh is what I am looking into and I am thinking ovn can > have a better approach. > > I did an implementation of sfc around nsh that used ovs & flows from > custom ovs-agent back in mar-may. I added fields in ovs agent to send >

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Russell, " These logical flows look similar to OpenFlow, but it talks about network resources in the logical sense (not based on where they are physically located). I think we can implement SFC purely in the logical space. " Exactly. I was in the ovn presentation at Vancouver and at that time

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Apologize typo "...us get overboard." ==> should be "... get us onboard" :) On Thu, Oct 1, 2015 at 11:38 AM, Murali R wrote: > Russell, > > " These logical flows > look similar to OpenFlow, but it talks about network resources in the > logical sense (not based on where

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Russell, Are any additional options fields used in geneve between hypervisors at this time? If so, how do they translate to vxlan when it hits gw? For instance, I am interested to see if we can translate a custom header info in vxlan to geneve headers and vice-versa. And if there are flow

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/30/2015 03:29 PM, Murali R wrote: > Russell, > > Are any additional options fields used in geneve between hypervisors at > this time? If so, how do they translate to vxlan when it hits gw? For > instance, I am interested to see if we can translate a custom header > info in vxlan to geneve

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/30/2015 04:09 PM, Murali R wrote: > Russel, > > For instance if I have a nsh header embedded in vxlan in the incoming > packet, I was wondering if I can transfer that to geneve options > somehow. This is just as an example. I may have header other info either > in vxlan or ip that needs to

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Russel, For instance if I have a nsh header embedded in vxlan in the incoming packet, I was wondering if I can transfer that to geneve options somehow. This is just as an example. I may have header other info either in vxlan or ip that needs to enter the ovn network and if we have generic ovs

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Yes, sfc without nsh is what I am looking into and I am thinking ovn can have a better approach. I did an implementation of sfc around nsh that used ovs & flows from custom ovs-agent back in mar-may. I added fields in ovs agent to send additional info for actions as well. Neutron side was quite

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/27/2015 06:50 AM, Kevin Benton wrote: > Assuming it implements the normal provider networks API, you just > specify the segmentation_id when you create the network. > > neutron net-create NET_NAME --provider:network_type vlan > --provider:physical_network physnet1

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/27/2015 02:26 AM, WANG, Ming Hao (Tony T) wrote: > Russell, > > Thanks for your valuable information. > I understood Geneve is some kind of tunnel format for network virtualization > encapsulation, just like VxLAN. > But I'm still confused by the connection between Geneve and VTEP. > I

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Hao (Tony T) Subject: Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container? On 09/27/2015 06:50 AM, Kevin Benton wrote: > Assuming it implements the normal provider networks API, you just > specify the segmentation_id wh

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

ony T) Sent: Sunday, September 27, 2015 2:26 PM To: 'Russell Bryant'; OpenStack Development Mailing List (not for usage questions) Subject: RE: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container? Russell, Thanks for your v

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

NG, Ming Hao (Tony T); OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container? On 09/24/2015 10:37 AM, WANG, Ming Hao (Tony T) wrote: > Russell, > > Thank

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

ed > as a tunnel endpoint for Geneve? > > Thanks, > Tony > -Original Message- > From: Russell Bryant [mailto:rbry...@redhat.com] > Sent: Friday, September 25, 2015 12:04 AM > To: WANG, Ming Hao (Tony T); OpenStack Development Mailing List (not for > usage quest

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container? I'll reply to each of your 3 messages here: On 09/23/2015 05:57 AM, WANG, Ming Hao (Tony T) wrote: > Hi Russell, > > I just realized OVN plugin is an independent plugin of O

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/24/2015 10:37 AM, WANG, Ming Hao (Tony T) wrote: > Russell, > > Thanks for your detail explanation and kind help! > I have understand how container in VM can acquire network interfaces in > different neutron networks now. > For the connections between compute nodes, I think I need to study

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

, September 23, 2015 1:58 PM To: WANG, Ming Hao (Tony T); 'OpenStack Development Mailing List (not for usage questions)' Subject: RE: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container? Hi Russell, Is there any material to explain how OVN

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

t; -Original Message- > From: WANG, Ming Hao (Tony T) > Sent: Wednesday, September 23, 2015 1:58 PM > To: WANG, Ming Hao (Tony T); 'OpenStack Development Mailing List (not for > usage questions)' > Subject: RE: [openstack-dev] [neutron + ovn] Does neutron ovn plugin supp

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

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