Bug 1514927 – [RFE] Add ovirt metrics to the ovirt-ansible host deploy playbook

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1514927 - [RFE] Add ovirt metrics to the ovirt-ansible host deploy playbook

Summary:	[RFE] Add ovirt metrics to the ovirt-ansible host deploy playbook

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	ovirt-engine
Classification:	oVirt
Component:	Host-Deploy (Show other bugs)
Sub Component:
Version:	4.2.0
Hardware:	Unspecified Unspecified

Priority	high Severity high (vote)
Target Milestone:	ovirt-4.2.2
Target Release:	---
Assigned To:	Shirly Radco
QA Contact:	Lukas Svaty
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:	1538998 1549163
Blocks:	1523289 1544241
	Show dependency tree / graph

Reported:	2017-11-19 09:02 EST by Shirly Radco
Modified:	2018-04-08 08:33 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	ovirt-engine-4.2.1.1
Doc Type:	Enhancement
Doc Text:	Previously, newly deployed hosts had to be individually configured to collect metrics and logs. In this release, for systems in which both the Metrics Store server and the Manager and hosts have already been configured to collect metrics and logs, all newly-deployed hosts will be configured automatically.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-03-29 07:13:45 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Metrics
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	rule-engine: ovirt‑4.2+ ylavi: exception+ lsvaty: testing_plan_complete- ylavi: planning_ack+ sradco: devel_ack+ lsvaty: testing_ack+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	84331	master	MERGED	packaging: Add oVirt.metrics role to host deploy	2018-01-10 02:29 EST
oVirt gerrit	84756	master	MERGED	fluentd: add role that reads engine variables	2017-12-04 04:31 EST
oVirt gerrit	85092	master	ABANDONED	ansible: add initial_validations role	2017-12-20 07:04 EST
oVirt gerrit	85192	master	ABANDONED	ansible: seperate out the manage_services	2017-12-13 09:10 EST
oVirt gerrit	85311	master	ABANDONED	ansible: Remove group vars and add them to the roles	2017-12-20 07:04 EST
oVirt gerrit	85415	master	MERGED	ansible: Updated ovirt metrics repo structure	2018-01-04 07:58 EST
oVirt gerrit	86126	master	MERGED	fluentd: fix condition for fluentd_elasticsearch_host	2018-01-09 11:41 EST

Groups: None (edit)

Description Shirly Radco 2017-11-19 09:02:29 EST

Description of problem:

We would like to deploy oVirt metrics on every new host, in case there is already a metrics store configured.

Comment 1 Lukas Svaty 2017-12-07 11:30:55 EST

Hi Shirly, can you please share some bits about the design of this RFE? What is expected behaviour?

Comment 2 Shirly Radco 2018-01-03 06:02:34 EST

I created a new role oVirt.metrics.

All of the ovirt-engine-metrics roles will now be installed at /usr/share/ansible/roles/oVirt.metrics/ .

When a new hosts is added or reinstalled, the oVirt metrics role will be run as part of the ovirt engine host deploy ansible scripts.

If the metrics store is already configured, the host will be configured to send metrics and logs to the remote metrics store.

If it is not, the the playbook will end with a message that the metrics store is not configured so this host will not be configured to send metrics.

Comment 3 Lukas Svaty 2018-01-26 10:12:34 EST

this is currently not working, and caused installation of new hosts to engine already set up with metrics to get stuck (see BZ#1538998)

Comment 4 Lukas Svaty 2018-03-20 07:23:47 EDT

verified in ovirt-host-4.2.2-2.el7ev.x86_64

Comment 5 Sandro Bonazzola 2018-03-29 07:13:45 EDT

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Note You need to log in before you can comment on or make changes to this bug.