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

Bug 1619537

Summary:	[Docs][OVN] Document the agents API
Product:	Red Hat OpenStack	Reporter:	Lucy Bopf <lbopf>
Component:	documentation	Assignee:	James Smith <jamsmith>
Status:	CLOSED NOTABUG	QA Contact:	Joanne O'Flynn <joflynn>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	dcadzow, sclewis, srevivo
Target Milestone:	beta	Keywords:	Documentation, FutureFeature
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-26 17:09:33 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:
Bug Depends On:	1495692
Bug Blocks:

Description Lucy Bopf 2018-08-21 07:10:36 UTC

Name of function:
Implement the agents API

User story:
As a cloud operator, I need to know if there are connectivity problems between controllers and compute nodes and I need to be able to control this from one place, especially for clusters.

Purpose of function:
With this feature, the command line: 'openstack network agent list' will display the status of OVN services of each node.  Although there are no agents in OVN (like there are in ODL), the user should get an indication of the connection status between OVN services of each node (Controller & compute nodes)

Work required (from detail plan):
Procedural 
------
How to display the status of OVN services of each node (check if there’s existing docs and update)
------

Conceptual 
------
N/A
------

Reference
------
N/A
------

Comment 2 Lucy Bopf 2018-08-21 07:22:38 UTC

Accepting into RHOSP 14 documentation program.

Comment 3 Lucy Bopf 2018-08-28 04:27:15 UTC

Assigning to James for review, and targeting at 14-Beta.

Comment 5 Derek 2018-09-26 17:09:33 UTC

This bug can be closed since there's no doc impact to the source bug (according to the input from the detailed planning meeting with the DFG).