Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

Can we move the discussion of deprecating veth pairs to here? https://bugs.launchpad.net/neutron/+bug/1587296 https://review.openstack.org/323310 As you can see in the related bugs and linked patches there are some complications. Some of the veth config options were already deprecated and the

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 16 June 2016 at 03:33, Matt Riedemann wrote: > On 6/13/2016 3:35 AM, Daniel P. Berrange wrote: > >> On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: >> >>> Hi, >>> >>> You may or may not be aware of the vlan-aware-vms effort [1] in >>> Neutron. If

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 16 June 2016 at 03:33, Matt Riedemann wrote: > On 6/13/2016 3:35 AM, Daniel P. Berrange wrote: > >> On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: >> >>> Hi, >>> >>> You may or may not be aware of the vlan-aware-vms effort [1] in >>> Neutron. If

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 16 June 2016 at 00:31, Carl Baldwin wrote: > I know I've been pretty quiet since I started this thread. Y'all have > been doing so well, I've just been reading the thread every day and > enjoying it. I thought I'd top post here to kind of summarize. > > I see wisdom in

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 6/13/2016 3:35 AM, Daniel P. Berrange wrote: On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: Hi, You may or may not be aware of the vlan-aware-vms effort [1] in Neutron. If not, there is a spec and a fair number of patches in progress for this. Essentially, the goal is to

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

I know I've been pretty quiet since I started this thread. Y'all have been doing so well, I've just been reading the thread every day and enjoying it. I thought I'd top post here to kind of summarize. I see wisdom in the strategy suggested by Sean Mooney to make a very minimal change to os-vif

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

>I wouldn't say linux bridges are totally outside of its domain because it relies on them for security groups. It relies on a side effect of their existence - iptables rules being applied to the veth interface. It does nothing to the actual linux bridge itself. If there was a way to plug a veth

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Wednesday, June 15, 2016 12:45 PM, Mooney, Sean K [sean.k.moo...@intel.com] wrote: > > On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub) > > wrote: > > > >which generates an arbitrary name > > > > > > I'm not a fan of this approach because it requires coordinated > >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

> Subject: Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability > for wiring trunk ports > > On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub) > wrote: > > >which generates an arbitrary name > > > > I'm not a fan of this approach beca

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Wed, Jun 15, 2016 at 2:01 PM, Peters, Rawlin wrote: > On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub) wrote: >> >which generates an arbitrary name >> >> I'm not a fan of this approach because it requires coordinated assumptions. >> With the OVS hybrid

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Tuesday, June 14, 2016 6:27 PM, Kevin Benton (ke...@benton.pub) wrote: > >which generates an arbitrary name > > I'm not a fan of this approach because it requires coordinated assumptions. > With the OVS hybrid plug strategy we have to make guesses on the agent side > about the presence of

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

>which generates an arbitrary name I'm not a fan of this approach because it requires coordinated assumptions. With the OVS hybrid plug strategy we have to make guesses on the agent side about the presence of bridges with specific names that we never explicitly requested and that we were never

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Tuesday, June 14, 2016 3:43 AM, Daniel P. Berrange (berra...@redhat.com) wrote: > > On Tue, Jun 14, 2016 at 02:35:57AM -0700, Kevin Benton wrote: > > In strategy 2 we just pass 1 bridge name to Nova. That's the one that > > is ensures is created and plumbs the VM to. Since it's not

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 06/14/2016 11:43 AM, Daniel P. Berrange wrote: Ok, so we're already passing that bridge name - all we need change is make sure it is actuall created if it doesn't already exist ? If so that sounds simple enough to add to os-vif - we already have exactly the same logic for the linux_bridge

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

vin Benton [mailto:ke...@benton.pub] Sent: Tuesday, June 14, 2016 10:49 AM To: Daniel P. Berrange <berra...@redhat.com> Cc: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports Yep, and both strategies depend on tha

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

Yep, and both strategies depend on that "create if not exists" logic so it makes sense to at least get that implemented while we continue to argue about which strategy to use. On Jun 14, 2016 02:43, "Daniel P. Berrange" wrote: > On Tue, Jun 14, 2016 at 02:35:57AM -0700,

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Tue, Jun 14, 2016 at 02:35:57AM -0700, Kevin Benton wrote: > In strategy 2 we just pass 1 bridge name to Nova. That's the one that is > ensures is created and plumbs the VM to. Since it's not responsible for > patch ports it doesn't need to know anything about the other bridge. Ok, so we're

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

In strategy 2 we just pass 1 bridge name to Nova. That's the one that is ensures is created and plumbs the VM to. Since it's not responsible for patch ports it doesn't need to know anything about the other bridge. On Tue, Jun 14, 2016 at 2:30 AM, Daniel P. Berrange wrote: >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Tue, Jun 14, 2016 at 02:10:52AM -0700, Kevin Benton wrote: > Strategy 1 is being pitched to make it easier to implement with the current > internals of the Neutron OVS agent (using integration bridge plugging > events). I'm not sure that's better architecturally long term because the > OVS

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

Strategy 1 is being pitched to make it easier to implement with the current internals of the Neutron OVS agent (using integration bridge plugging events). I'm not sure that's better architecturally long term because the OVS agent has to have logic to wire up patch ports for the sub-interfaces

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Mon, Jun 13, 2016 at 11:35:17PM +, Peters, Rawlin wrote: > That said, there are currently a couple of vif-plugging strategies > we could go with for wiring trunk ports for OVS, each of them > requiring varying levels of os-vif augmentation: > > Strategy 1) When Nova is plugging a trunk

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

t;openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports +1. Neutron should already be able to tell Nova which bridge to use for an OVS port.[1] For the Linux bridge implementation it's a matter of creating vlan interfaces

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Monday, June 13, 2016 6:28 AM, Daniel P. Berrange wrote: > > On Mon, Jun 13, 2016 at 07:39:29AM -0400, Assaf Muller wrote: > > On Mon, Jun 13, 2016 at 4:35 AM, Daniel P. Berrange > wrote: > > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > >> Hi, > >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

+1. Neutron should already be able to tell Nova which bridge to use for an OVS port.[1] For the Linux bridge implementation it's a matter of creating vlan interfaces and plugging them into bridges like regular VM ports, which is all the responsibility of the L2 agent. We shouldn't need any changes

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

> -Original Message- > From: Daniel P. Berrange [mailto:berra...@redhat.com] > Sent: Monday, June 13, 2016 1:12 PM > To: Armando M. > Cc: Carl Baldwin ; OpenStack Development Mailing > List ; Jay Pipes >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Mon, Jun 13, 2016 at 07:39:29AM -0400, Assaf Muller wrote: > On Mon, Jun 13, 2016 at 4:35 AM, Daniel P. Berrange > wrote: > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > >> Hi, > >> > >> You may or may not be aware of the vlan-aware-vms effort [1] in >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 13 June 2016 at 14:11, Daniel P. Berrange wrote: > On Mon, Jun 13, 2016 at 02:08:30PM +0200, Armando M. wrote: > > On 13 June 2016 at 10:35, Daniel P. Berrange > wrote: > > > > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > > >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Mon, Jun 13, 2016 at 02:08:30PM +0200, Armando M. wrote: > On 13 June 2016 at 10:35, Daniel P. Berrange wrote: > > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > > Hi, > > > > > > You may or may not be aware of the vlan-aware-vms effort [1] in > > >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On 13 June 2016 at 10:35, Daniel P. Berrange wrote: > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > Hi, > > > > You may or may not be aware of the vlan-aware-vms effort [1] in > > Neutron. If not, there is a spec and a fair number of patches in > >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Mon, Jun 13, 2016 at 4:35 AM, Daniel P. Berrange wrote: > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: >> Hi, >> >> You may or may not be aware of the vlan-aware-vms effort [1] in >> Neutron. If not, there is a spec and a fair number of patches in >>

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > Hi, > > You may or may not be aware of the vlan-aware-vms effort [1] in > Neutron. If not, there is a spec and a fair number of patches in > progress for this. Essentially, the goal is to allow a VM to connect > to multiple Neutron

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

Here's a link directly to the current design proposal [1] that might be of interest. [1] https://review.openstack.org/#/c/318317/4/doc/source/devref/openvswitch_agent.rst@463 On Thu, Jun 9, 2016 at 5:31 PM, Carl Baldwin wrote: > Hi, > > You may or may not be aware of the