Comment 7 for bug 1991965

Reviewed: https://review.opendev.org/c/openstack/neutron/+/860639
Committed: https://opendev.org/openstack/neutron/commit/3ebdfe612a931a044877b2041a4ab68489bde5b7
Submitter: "Zuul (22348)"
Branch: master

commit 3ebdfe612a931a044877b2041a4ab68489bde5b7
Author: Rodolfo Alonso Hernandez <email address hidden>
Date: Sun Oct 2 17:29:32 2022 +0200

    Support for minimum bandwidth rules in tunnelled networks

    This patch adds support for QoS minimum bandwidth rules in tunnelled
    networks. Now the ML2/OVS and ML2/OVN mechanism drivers can represent
    in the Placement API the available bandwidth of the tunnelled networks
    in each compute host.

    Both mechanism drivers represent the compute VTEP (VXLAN) or TEP
    (Geneve) interface as an IP address. This new resource provider
    (by default called "rp_tunnelled") represents the available bandwidth
    of this interface. Any new port created in a compute node that belongs
    to a tunnelled network, will request to the Placement API the
    corresponding bandwidth from the resource provider inventory.

    This patch does not provide backend enforcement support for minimum
    bandwidth rules.

    RFE spec: https://review.opendev.org/c/openstack/neutron-specs/+/860859

    What is missing and will be added in next patches:
    * Tempest tests, that will be pushed to the corresponding repository.

    Depends-On: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/863880

    Partial-Bug: #1991965
    Related-Bug: #1578989
    Change-Id: I3bfc2c0f9566bcc6861ca91339e32257ea92c7e9