yahoo-eng-team team mailing list archive

[OpenStack Infra <1863852@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/711317
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b098239d72d79469677bdc1e45daf7454b2eeb47
Submitter: Zuul
Branch:    master

commit b098239d72d79469677bdc1e45daf7454b2eeb47
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Wed Mar 4 16:39:35 2020 +0000

    Refactor OVN client QoS extension
    
    The QoS OVN client extension is moved to the ML2 driver. This
    extension is called from the OVN driver in the events of:
    - create port
    - update port
    - delete port
    - update network
    
    The QoS OVN client extension now can accept several rules per policy
    as documented in the SUPPORTED_RULES. The QoS OVN client extension
    can write one OVN QoS rule per flow direction and each OVN QoS rule
    register can hold both a bandwidth limit rule and a DSCP marking rule.
    
    The "update_policy" method is called from the OVN QoS driver, when
    a QoS policy or its rules are updated.
    
    The QoS OVN client extension updates the QoS OVN registers
    exclusively, based on the related events.
    
    Closes-Bug: #1863852
    
    Change-Id: I4833ed0c9a2741bdd007d4ebb3e8c1cb4c30d4c7


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  [OVN]Could not support more than one qos rule in one policy

Status in neutron:
  Fix Released

Bug description:
  Currently,the networking-ovn doesn't consider such qos policy, which has both ingress and egress rule.
  So when we apply such policy to port or network, only one of them will works.

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