Bug 1432099

Summary:	[RFE] Add cron job that provisions fluentd and collectd on engine and hosts
Product:	[oVirt] ovirt-engine-metrics	Reporter:	Shirly Radco <sradco>
Component:	RFEs	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED DEFERRED	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1.0.0	CC:	bugs, didi, lsvaty, mperina, sradco, ylavi
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	sradco: ovirt-4.2? lsvaty: testing_plan_complete+ ylavi: planning_ack+ sradco: devel_ack? lsvaty: testing_ack+
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:	2017-10-24 09:10:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1402901

Description Shirly Radco 2017-03-14 14:15:35 UTC

Description of problem:
Add cron job that checks for fluentd and collectd changes and update the engine and hosts if there was a change

We want this to be updated automatically without the user require to manually trigger it.

Comment 1 Yaniv Kaul 2017-06-19 11:42:24 UTC

Please talk to Martin P. on integrating the metrics Ansible script into the oVirt Ansible host deploy batch of scripts. Once you do that, we can close this bug, IMHO.

Comment 2 Yedidyah Bar David 2017-07-16 11:42:17 UTC

Discussed and agreed to add '--quiet' and pass it from the cron job, so that no noise is logged if config.yml is missing.

Comment 3 Yaniv Lavi 2017-09-06 08:30:32 UTC

No need to check for changes as Ansible handles this.

Comment 4 Shirly Radco 2017-09-07 10:22:36 UTC

(In reply to Yaniv Kaul from comment #1)
> Please talk to Martin P. on integrating the metrics Ansible script into the
> oVirt Ansible host deploy batch of scripts. Once you do that, we can close
> this bug, IMHO.

Since we now have the cluster name as part of the record, and it only updates when running the metrics ansible, I think it would be valuable to run this at least once a day so if a host cluster was updated then it will be updated for the metrics as well.

Comment 5 Shirly Radco 2017-09-07 11:58:53 UTC

The cron job does not need to check for changes.
It just needs to run the script once in an interval.

Yaniv L, what do you think should we set the interval to?

Comment 6 Yaniv Lavi 2017-09-07 14:19:51 UTC

(In reply to Shirly Radco from comment #5)
> The cron job does not need to check for changes.
> It just needs to run the script once in an interval.
> 
> Yaniv L, what do you think should we set the interval to?

If doesn't cost us much I would run it every hour.

Comment 7 Yaniv Kaul 2017-09-26 07:10:41 UTC

Shirly, we decided it is not needed anymore?

Comment 8 Shirly Radco 2017-09-26 07:56:07 UTC

The script should be run was part of the ansible host deploy playbooks.

When setting up oVirt metrics or if the user changes the metrics store parameters , move a host from cluster to cluster, update configuration files, etc. it will require running it manually.

Comment 9 Shirly Radco 2017-10-24 09:10:26 UTC

Closing for now. Will re-open if we feel this is indeed required.