3ebdfe612a
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
11 lines
475 B
YAML
11 lines
475 B
YAML
---
|
|
features:
|
|
- |
|
|
ML2/OVS and ML2/OVN now support modelling tunnelled networks in the
|
|
Placement API. The "tunnelled_network_rp_name" configuration option
|
|
defines the resource provider name used to represent all tunnelled
|
|
networks in a compute node (by default "rp_tunnelled"). If this string
|
|
is present in the "resource_provider_bandwidths" dictionary, the
|
|
corresponding mechanism driver will create a resource provider for
|
|
the overlay traffic.
|