[RFE] Strict minimum bandwidth support for tunnelled networks

[Rodolfo Alonso]

This bug is related to https://bugs.launchpad.net/neutron/+bug/1578989.

The aim of this RFE is to improve LP#1578989. This feature implemented all the code necessary to allow Neutron to report the available network resources. Neutron was responsible of retrieving the administrator configuration and send it to Placement. Each node would be represented as a resource provider; the ML2 agents would be child RP resources and the physical network would be child RPs of the ML2 agents.

  RP host 1
  --> RP OVS agent
      --> physnet 1: egress BW, ingress BW

This feature had a 1:1 representation of the physical networks available in each node (compute node). Each physical network had associated a physical device (a network interface) and this device had an associated egress and ingress bandwidth. We can see that as saying that "if we have a 10Gb NIC connected to physnet1, we'll assign those 10Gb for ingress/egress".

Currently we don't model the overlay networks (tunnelled networks). This is because there is no way to model the tunnelled networks. This RFE proposes to use a unique resource provider identifier to model the overlay networks in a host. Both in ML2/OVS and ML2/OVN (ML2/SR-IOV doesn't support tunnelled networks), the overlay traffic is sent to the "local_ip", that is the host IP address set on the local VTEP.

This "tunnelled resource provider" inventory will be requested for any port min-bw QoS rule that belongs to a tunnelled network (VXLAN, Geneve).

Related bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2097932

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/neutron/+/860639

[Lajos Katona (lajos-katona)]

We discussed this RFE on the last drivers meeting, and accepted it, see the logs:
https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-10-07-14.00.log.html

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/neutron-specs/+/860859

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/863880

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron-specs/+/860859
Committed: https://opendev.org/openstack/neutron-specs/commit/5c12c2b8b85aec899904defe43784367c11f5a46
Submitter: "Zuul (22348)"
Branch: master

commit 5c12c2b8b85aec899904defe43784367c11f5a46
Author: Rodolfo Alonso Hernandez <email address hidden>
Date: Mon Oct 3 10:02:30 2022 +0200

    Strict minimum bandwidth support for tunnelled networks

    The aim of the RFE is to improve the previous implemented RFE
    Strict minimum bandwidth support [1].

    [1]https://bugs.launchpad.net/neutron/+bug/1578989

    Related-Bug: #1991965
    Change-Id: I21a1d9bee1d195f704a518ea3dbd3f2b1e35a357

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/863880
Committed: https://opendev.org/openstack/neutron-tempest-plugin/commit/aca1ac73ad7dda89afa8288f73fc9af8e234a66a
Submitter: "Zuul (22348)"
Branch: master

commit aca1ac73ad7dda89afa8288f73fc9af8e234a66a
Author: Rodolfo Alonso Hernandez <email address hidden>
Date: Mon Nov 7 14:12:18 2022 +0000

    Skip "test_port_resource_request_no_provider_net_conflict"

    Skip this test while LP#1991965 is being implemented. This new
    feature will avoid having ports with minimum bandwidth rules on
    overlay networks. Once implemented, this test will be removed
    and new tests added to this repository.

    Change-Id: I275495299866310d6bd0df50fd22d7ea7116a23b
    Related-Bug: #1991965

[OpenStack Infra (hudson-openstack)]

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

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

This RFE is implemented in [1].

[1]https://review.opendev.org/c/openstack/neutron/+/860639