yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1918702@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description of problem:
When a QoS policy with an egress BW limit rule is assigned to a SR-IOV port (type direct or macvtap), the corresponding rule should be managed by the SR-IOV agent and should not be added to the OVN NBDB's QoS table.

However, the entry on the QoS table is created for that port, which is
wrong.

The rule is also applied to the dataplane traffic shaper, which is
correct.

Steps to Reproduce:
1) Create qos policy with an egress bw limit rule and assing it to an SRIOV port:
   # openstack network qos policy create p0
   # openstack network qos rule create p0 --type bandwidth-limit --max-kbps 500000000 \
     --max-burst-kbits 40000000
   # openstack port set --qos-policy p0 0917ed75-6362-4522-a468-c3a8c89712fd

2) Check qos ovn nbdb table
   # ovn-nbctl --db=tcp:10.20.1.73:6641 list qos | grep -C5 $qos_uuid

_uuid               : c2758e23-195e-4efa-8f9f-c057955ba6c3
action              : {}
bandwidth           : {burst=40000000, rate=540000}
direction           : from-lport
external_ids        : {}
match               : "inport == \"0917ed75-6362-4522-a468-c3a8c89712fd\""
priority            : 2002

This kind of testing is not available in the Opendev CI because there
are not SR-IOV environments.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1936527

** Affects: neutron
     Importance: Undecided
     Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)

** Description changed:

  Description of problem:
  When a QoS policy with an egress BW limit rule is assigned to a SR-IOV port (type direct or macvtap), the corresponding rule should be managed by the SR-IOV agent and should not be added to the OVN NBDB's QoS table.
  
  However, the entry on the QoS table is created for that port, which is
  wrong.
  
  The rule is also applied to the dataplane traffic shaper, which is
  correct.
  
  Steps to Reproduce:
  1) Create qos policy with an egress bw limit rule and assing it to an SRIOV port:
-    # openstack network qos policy create p0
-    # openstack network qos rule create p0 --type bandwidth-limit --max-kbps 500000000 \
-      --max-burst-kbits 40000000
-    # openstack port set --qos-policy p0 0917ed75-6362-4522-a468-c3a8c89712fd
+    # openstack network qos policy create p0
+    # openstack network qos rule create p0 --type bandwidth-limit --max-kbps 500000000 \
+      --max-burst-kbits 40000000
+    # openstack port set --qos-policy p0 0917ed75-6362-4522-a468-c3a8c89712fd
  
  2) Check qos ovn nbdb table
-    # ovn-nbctl --db=tcp:10.20.1.73:6641 list qos | grep -C5 $qos_uuid
+    # ovn-nbctl --db=tcp:10.20.1.73:6641 list qos | grep -C5 $qos_uuid
  
  _uuid               : c2758e23-195e-4efa-8f9f-c057955ba6c3
  action              : {}
  bandwidth           : {burst=40000000, rate=540000}
  direction           : from-lport
  external_ids        : {}
  match               : "inport == \"0917ed75-6362-4522-a468-c3a8c89712fd\""
  priority            : 2002
  
- 
- This kind of testing is not available in the Opendev CI because there are not SR-IOV environment.
+ This kind of testing is not available in the Opendev CI because there
+ are not SR-IOV environments.
  
  Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1936527

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

Title:
  [OVN] BW limit QoS rules assigned to SR-IOV ports are created on NBDB

Status in neutron:
  New

Bug description:
  Description of problem:
  When a QoS policy with an egress BW limit rule is assigned to a SR-IOV port (type direct or macvtap), the corresponding rule should be managed by the SR-IOV agent and should not be added to the OVN NBDB's QoS table.

  However, the entry on the QoS table is created for that port, which is
  wrong.

  The rule is also applied to the dataplane traffic shaper, which is
  correct.

  Steps to Reproduce:
  1) Create qos policy with an egress bw limit rule and assing it to an SRIOV port:
     # openstack network qos policy create p0
     # openstack network qos rule create p0 --type bandwidth-limit --max-kbps 500000000 \
       --max-burst-kbits 40000000
     # openstack port set --qos-policy p0 0917ed75-6362-4522-a468-c3a8c89712fd

  2) Check qos ovn nbdb table
     # ovn-nbctl --db=tcp:10.20.1.73:6641 list qos | grep -C5 $qos_uuid

  _uuid               : c2758e23-195e-4efa-8f9f-c057955ba6c3
  action              : {}
  bandwidth           : {burst=40000000, rate=540000}
  direction           : from-lport
  external_ids        : {}
  match               : "inport == \"0917ed75-6362-4522-a468-c3a8c89712fd\""
  priority            : 2002

  This kind of testing is not available in the Opendev CI because there
  are not SR-IOV environments.

  Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1936527

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