Bug 1480381

Summary:	[RFE] IPA telemetry
Product:	Red Hat OpenStack	Reporter:	Ilya Etingof <ietingof>
Component:	openstack-ironic	Assignee:	Ilya Etingof <ietingof>
Status:	CLOSED DEFERRED	QA Contact:	mlammon
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	bfournie, jkreger, mburns, racedoro, srevivo
Target Milestone:	Upstream M2	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://bugs.launchpad.net/ironic-python-agent/+bug/1709983
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-14 18:04:27 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 Ilya Etingof 2017-08-10 22:17:43 UTC

Currently, when IPA spawns a tool to perform a long-running task on the node (like wiping out the storage on node clean up), there is no way for the operator to figure out the progress of that long-running operation (is it still running or maybe hung?) as well as to have an estimation on when it might finish.

Possible solution can be to capture the information at the standard output streams of a spawned tool, buffer that and eventually deliver the data to the Ironic conductor (probably piggy-backing the heartbeats) for further consumption by the cli or web-ui clients.

Comment 2 Ilya Etingof 2017-08-11 12:56:15 UTC

Proposed spec: https://review.openstack.org/492702

Comment 8 Bob Fournier 2018-08-29 15:23:36 UTC

Moving out of OSP-15, bumping to 16.

Comment 15 Julia Kreger 2020-09-14 18:04:27 UTC

I'm marking closed/deferred as the community pushed back on this effort and deploy_steps in Victoria at least answers the "what exactly is going on" portion of what this sought to answer.