commit a6f975ac035ca7c67d0d126b76eb280e1b9d1829
Author: Rodolfo Alonso Hernandez <email address hidden>
Date: Fri Feb 19 17:27:39 2021 +0000
[OVN][Placement] Add a SB Chassis event to track changes in BW config
Added a new OVN Client extension: OVNClientPlacementExtension. This
extension is in charge of handling the bandwidth information stored
in the OVN database, in the "Chassis" registers on the
"ovn-cms-options" dictionary.
Three new keys are created to store the resource provider information
needed to parameterize the network backend bandwidth information,
following the implementation done in OVS and SR-IOV:
- resource_provider_bandwidths
- resource_provider_inventory_defaults
- resource_provider_hypervisors
When the OVN Client is started, the Placement extension will check if
the "placement" extension is loaded. It will also create an event to
check any configuration change done in any "Chassis" register.
The Placement extension will read the initial configuration stored
in the OVN database and will populate it to Placement API, creating
the needed resource providers, traits and inventories.
NOTE: This patch belongs to a series of patches to implement
minimum bandwidth scheduling blueprint in OVN backend. The next
patch will make OVN backend scheduling aware using the information
stored in Placement API and the port information passed by Nova when
a VM is created.
NOTE: this patch improves [1], fixing the error [2] reported in [3].
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/801712 /opendev. org/openstack/ neutron/ commit/ a6f975ac035ca7c 67d0d126b76eb28 0e1b9d1829
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit a6f975ac035ca7c 67d0d126b76eb28 0e1b9d1829
Author: Rodolfo Alonso Hernandez <email address hidden>
Date: Fri Feb 19 17:27:39 2021 +0000
[OVN] [Placement] Add a SB Chassis event to track changes in BW config
Added a new OVN Client extension: OVNClientPlacem entExtension. This cms-options" dictionary.
extension is in charge of handling the bandwidth information stored
in the OVN database, in the "Chassis" registers on the
"ovn-
Three new keys are created to store the resource provider information provider_ bandwidths provider_ inventory_ defaults provider_ hypervisors
needed to parameterize the network backend bandwidth information,
following the implementation done in OVS and SR-IOV:
- resource_
- resource_
- resource_
When the OVN Client is started, the Placement extension will check if
the "placement" extension is loaded. It will also create an event to
check any configuration change done in any "Chassis" register.
The Placement extension will read the initial configuration stored
in the OVN database and will populate it to Placement API, creating
the needed resource providers, traits and inventories.
NOTE: This patch belongs to a series of patches to implement
minimum bandwidth scheduling blueprint in OVN backend. The next
patch will make OVN backend scheduling aware using the information
stored in Placement API and the port information passed by Nova when
a VM is created.
NOTE: this patch improves [1], fixing the error [2] reported in [3].
[1]https:/ /review. opendev. org/c/openstack /neutron/ +/776701 /paste. opendev. org/show/ 807614/ /launchpad. net/bugs/ 1936983
[2]https:/
[3]https:/
Partial-Bug: #1578989 226ff2cfe91f16c 97913c137e8
Change-Id: I63e81aebce2621