Comment 141 for bug 1578989

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

commit df5cb28737453e2dfee17e177160fa6d7a59b7e0
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.

    Partial-Bug: #1578989

    Change-Id: I8ba38b8ace8852009fba8712aafa9f88c2b93ccb