Bug 1615348

Hi Shirly,

can you share a bit more information about this? For QA Ack we need requirements specification, to ensure we have all that is needed.

Verification steps/feature page would be great as well.

Thanks,
LS

Sure,

1. The user needs to update in the /etc/ovirt-engine-metrics/config.yml the node he wants to deploy elasticsearch on, based on the example file /etc/ovirt-engine-metrics/config.yml.example.

2. There should be one master node and additional nodes in the fluentd_elasticsearch_nodes parameter. In our use case the master nodes and additional nodes are vms in oVirt.

3. The nodes hardware requirements are stated here https://docs.okd.io/latest/architecture/infrastructure_components/kubernetes_infrastructure.html#node

4. In order to run the playbook run:
/usr/share/ovirt-engine-metrics/configure_ovirt_machines_for_metrics.sh -vvv --playbook=ovirt-metrics-store-installation.yml

5. The playbook will automatically either :
  5.1. Install OpenShift logging all-in-one on a single node if only fluentd_elasticsearch_host is configured
  5.2.  Install OpenShift logging on several nodes
  5.3.  Add additional nodes

6. The playbook runs the openshift-ansible playbooks from the engine machine. This is a change from the way we run them before (From the master node itself).

7. In the beginning of the playbook it creates passwordless connection to the nodes, the user will be prompt for password and the engine public key will be automatically copied to the nodes.

8. The parameters that set  the OpenShift version and distribution are:
openshift_version: 3.9
openshift_distribution: origin
They can be updated in the /etc/ovirt-engine-metrics/config.yml file or by adding a new vars file to the /etc/ovirt-engine-metrics/config.yml.d/ directory.

In d/s the the rpm package includes a vars file called "00-rhvm-defaults.yml" that is added to /etc/ovirt-engine-metrics/config.yml.d/ and sets openshift_distribution: ocp


**Note: I encountered one time an ssh connection timeout after the openshift-ansible playbooks finished , but rerunning the ovirt-metrics-store-installation.yml playbook ( /usr/share/ovirt-engine-metrics/configure_ovirt_machines_for_metrics.sh -vvv --playbook=ovirt-metrics-store-installation.yml)  fixed the issue.

**Note: The playbook does not upgrade OpenShift.

The link for the nodes hardware requirments is incorrect in #comment2.
This is the correct link :https://docs.okd.io/3.10/install/prerequisites.html

Since there is already work on having a generic OKD/OCP on oVirt/RHV, This bug will be based on it and only add the relevant oVirt metrics parameters and additional relevant tasks.

*** Bug 1647462 has been marked as a duplicate of this bug. ***

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

*** Bug 1599589 has been marked as a duplicate of this bug. ***

4.3.1 has been released, please re-target this bug as soon as possible.

Since the metrics installation changed quite a bit from the initial expectations, I tested it with the current official documentation.

Steps:
1) Install metrics store according to this documentation: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3-beta/html/metrics_store_installation_guide/index

Result:
Installation was successful, the metrics store is created and working, all pods, services and routes are running and ready.

Verified in: 
ovirt-engine-4.2.8.5-0.1.el7ev.noarch
ovirt-engine-metrics-1.2.1.3-1.el7ev.noarch

Also verified in:
ovirt-engine-4.3.3.1-0.1.el7.noarch
ovirt-engine-metrics-1.2.1.3-1.el7ev.noarch

If you think this is not enough for the verification, feel free to reopen the bug.

This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.3 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.