yahoo-eng-team team mailing list archive

[Armando Migliaccio <1624570@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Change [1], introduced a device_owner for trunk sub-ports. However, it
was overlooked that device_owner is used by QoS to determine whether to
process the port and apply QoS rules [2,3,4].

Right now there is not active coverage that ensures that QoS and Trunk
are indeed compatible but as we stand right now, they clearly cannot as
the code forbids applying rules to anything whose device_owner starts
with 'network:' or 'neutron:'.

We need to figure out a way to solve the conundrum.

[1] https://review.openstack.org/#/c/368289/
[2] https://github.com/openstack/neutron/blob/master/neutron/objects/qos/rule.py#L84

** Affects: neutron
     Importance: Medium
         Status: New


** Tags: newton-rc-potential

** Tags added: newton-rc-potential

** Changed in: neutron
   Importance: Undecided => Medium

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

Title:
  qos rules are not applied to trunk subports

Status in neutron:
  New

Bug description:
  Change [1], introduced a device_owner for trunk sub-ports. However, it
  was overlooked that device_owner is used by QoS to determine whether
  to process the port and apply QoS rules [2,3,4].

  Right now there is not active coverage that ensures that QoS and Trunk
  are indeed compatible but as we stand right now, they clearly cannot
  as the code forbids applying rules to anything whose device_owner
  starts with 'network:' or 'neutron:'.

  We need to figure out a way to solve the conundrum.

  [1] https://review.openstack.org/#/c/368289/
  [2] https://github.com/openstack/neutron/blob/master/neutron/objects/qos/rule.py#L84

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