yahoo-eng-team team mailing list archive

[sean mooney <sean.k.mooney@xxxxxxxxx>]

Public bug reported:

* Summary: neutron bridge name is not always set for ml2/ovs

* High level description: to enable live migration between different ml2
drivers utilizing multiple port bindings nova cannot assume the bridge name of
the destination host when generating the vm domain(e.g. libvirt xml)
to this end the ovs bridge name which is set when using trunk ports
also needs to be set in the general case.

* Expected output: 
when a port is bound by the ml2/ovs mech driver the bridge
name is set in the vif binding-details.

* Actual output: 
because the bridge name is not in the general case when you live migrate
from linux bridge to ovs the vm is attach to a new ovs bridge using the linux
bridge, bride name of the source node node instead attaching the vm interface
to the br-int bridge. as a result while the migration is successful 
the vm will have no network connectivity as this new bridge is not connect to the
br-int via a patch port pair.


* Version:
  ** OpenStack version master/Rocky RC1
  ** Centos 7.5
  ** DevStack

* Environment: multinode default devstack install.

* Perceived severity: low( it is a trival fix but it does prevent
migrating form lb to ovs hosts)

Click on extra options for the following:

** Affects: neutron
     Importance: Undecided
     Assignee: sean mooney (sean-k-mooney)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => sean mooney (sean-k-mooney)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1788009

Title:
  neutron bridge name is not always set for ml2/ovs

Status in neutron:
  New

Bug description:
  * Summary: neutron bridge name is not always set for ml2/ovs

  * High level description: to enable live migration between different ml2
  drivers utilizing multiple port bindings nova cannot assume the bridge name of
  the destination host when generating the vm domain(e.g. libvirt xml)
  to this end the ovs bridge name which is set when using trunk ports
  also needs to be set in the general case.

  * Expected output: 
  when a port is bound by the ml2/ovs mech driver the bridge
  name is set in the vif binding-details.

  * Actual output: 
  because the bridge name is not in the general case when you live migrate
  from linux bridge to ovs the vm is attach to a new ovs bridge using the linux
  bridge, bride name of the source node node instead attaching the vm interface
  to the br-int bridge. as a result while the migration is successful 
  the vm will have no network connectivity as this new bridge is not connect to the
  br-int via a patch port pair.

  
  * Version:
    ** OpenStack version master/Rocky RC1
    ** Centos 7.5
    ** DevStack

  * Environment: multinode default devstack install.

  * Perceived severity: low( it is a trival fix but it does prevent
  migrating form lb to ovs hosts)

  Click on extra options for the following:

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1788009/+subscriptions