yahoo-eng-team team mailing list archive

[QunyingRan <ran.qunying@xxxxxxxxxx>]

Public bug reported:

Mechanism_drivers some used for ovs VN, and others used for direct, macvtap, and so on, but when we create any VM, the all mechanism_drivers will be executed and not select suitable Mechanism_driver to bind port. 
For example, 'openvswitch' and 'sriovnicswitch' in ml2 configuration mechanism_drivers, and then created a sriov VM, only 'bind_port' in 'SriovNicSwitchMechanismDriver' should be run,  but we found function 'bind_port' in OpenvswitchMechanismDriver also has been used.

** Affects: neutron
     Importance: Undecided
     Assignee: QunyingRan (ran-qunying)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => QunyingRan (ran-qunying)

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

Title:
  why  all mechanism_drivers in configuration will be excuted when any
  vnic_type VM created

Status in neutron:
  New

Bug description:
  Mechanism_drivers some used for ovs VN, and others used for direct, macvtap, and so on, but when we create any VM, the all mechanism_drivers will be executed and not select suitable Mechanism_driver to bind port. 
  For example, 'openvswitch' and 'sriovnicswitch' in ml2 configuration mechanism_drivers, and then created a sriov VM, only 'bind_port' in 'SriovNicSwitchMechanismDriver' should be run,  but we found function 'bind_port' in OpenvswitchMechanismDriver also has been used.

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