OpenStack makes use of the Chassis_Private table to avoid unnecessary notifications being broadcasted to all SB connections. This makes a great impact on the scale when conditional monitoring is enabled. However, the benefits of this table are lost when ovn-monitor-all is set to True. This BZ is to request the exclusion of Chassis_Private for the unconditional monitoring that way that we can still benefit from the use of this table (eg. liveness checks).
(In reply to Daniel Alvarez Sanchez from comment #0) > OpenStack makes use of the Chassis_Private table to avoid unnecessary > notifications being broadcasted to all SB connections. This makes a great > impact on the scale when conditional monitoring is enabled. > > However, the benefits of this table are lost when ovn-monitor-all is set to > True. > > This BZ is to request the exclusion of Chassis_Private for the unconditional > monitoring that way that we can still benefit from the use of this table > (eg. liveness checks). We need some additional investigation to see if this is possible. Currently Chassis_Private is included in the same monitor as all other tables. Conditional monitoring is enabled/disabled per-monitor so it might not be enough to bypass ovn-monitor-all for Chassis_Private. We might need a separate monitor.
Hi, this issue was discussed during today's OVN core team meeting. We're still at a point where trying to have such conditional monitoring for only one table but unconditional monitoring for everything else is quite a difficult ask. However, OVSDB in particular has evolved quite a bit and we're curious if this same issue is really that much of a problem when using ovs2.17 or later. Thanks.
No response in 10 months. Closing.