yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #90695
[Bug 1998108] Re: Move "ChassisBandwidthConfigEvent" registration to "OvnSbIdl" class initialization
Reviewed: https://review.opendev.org/c/openstack/neutron/+/865857
Committed: https://opendev.org/openstack/neutron/commit/49eab7d308b598e4c4966110d6aa61cd091cc3f6
Submitter: "Zuul (22348)"
Branch: master
commit 49eab7d308b598e4c4966110d6aa61cd091cc3f6
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date: Thu Nov 17 21:14:40 2022 +0100
Move registration "ChassisBandwidthConfigEvent" to OvnSbIdl init
The "ChassisBandwidthConfigEvent" event registration is now done in the
"OvnSbIdl" class initialization. That ensures this event is registered
in a worker thread.
If the event is called before the "OVNMechanismDriver"'s "OVNClient"
has been instantiated, the event is skipped. When the OVN placement
extension is loaded, all chassis configurations are read and loaded,
thus any previous event is not relevant.
This patch also adds a "match_fn" check to
"ChassisBandwidthConfigEvent". If during an update event, the bandwidth
options are not modified, this class does not update the resource
provider inventories.
Closes-Bug: #1998108
Related-Bug: #1578989
Change-Id: I74883041c642b9498299ebf2b5bf885776e241e0
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1998108
Title:
Move "ChassisBandwidthConfigEvent" registration to "OvnSbIdl" class
initialization
Status in neutron:
Fix Released
Bug description:
The event "ChassisBandwidthConfigEvent", that is an OVN SB DB event,
should be registered in the "OvnSbIdl" class initialization. This
class is instantiated for the worker threads. Because we use the
"OvnDbNotifyHandler", the event will be treated by just one single OVN
Client at a time.
If the placement extension is not loaded yet, the class will skip any
event.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1998108/+subscriptions
References