Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 1983626

Summary:	[ovn] Exclude Chassis_Private table from unconditional monitoring
Product:	Red Hat Enterprise Linux Fast Datapath	Reporter:	Daniel Alvarez Sanchez <dalvarez>
Component:	ovn2.13	Assignee:	OVN Team <ovnteam>
Status:	CLOSED WONTFIX	QA Contact:	Jianlin Shi <jishi>
Severity:	high	Docs Contact:
Priority:	high
Version:	FDP 21.B	CC:	ctrautma, dceara, ihrachys, jiji, mmichels, ralongi
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-28 17:12:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Alvarez Sanchez 2021-07-19 09:22:06 UTC

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).

Comment 1 Dumitru Ceara 2021-07-19 15:07:36 UTC

(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.

Comment 2 Mark Michelson 2022-10-24 20:13:54 UTC

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.

Comment 3 Mark Michelson 2023-07-28 17:12:13 UTC

No response in 10 months. Closing.

Comment 4 Red Hat Bugzilla 2023-11-26 04:25:08 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days