Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update metrics-store-installation-guide.html.md #1097

Merged
merged 2 commits into from Jul 30, 2017
Merged

Update metrics-store-installation-guide.html.md #1097

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7e8e69b
Update metrics-store-installation-guide.html.md
sradco Jul 26, 2017
77ac89c
Update metrics-store-installation-guide.html.md
sradco Jul 30, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
24 changes: 18 additions & 6 deletions ...lop/release-management/features/engine/metrics-store-installation-guide.html.md
View file
Open in desktop
Expand Up @@ -17,6 +17,22 @@ feature_status: In Development
**Note:** Currently, the oVirt Metrics Store should be installed on a new machine, separate from the engine.
It can be installed on a dedicated VM.

Before starting the installation please choose an environment name ("ovirt_env_name"). It will be used to identify data sent from more than one oVirt engine and collected in a single central store.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ovirt_env_name variable should have a default and this default should be mentioned here

The default name for ovirt_env_name is "engine".

Use the following convention: Only include alphanumeric characters and hyphens ( "-" ). Name cannot begin with a hyphen or a number,
or end with a hyphen. Maximum of 49 characters. Wildcard patterns (e.g. ovirt-metrics*) cannot be used.

During the installation in the step [Configuring mux](https://github.com/ViaQ/Main/blob/master/README-mux.md#configuring-mux) , use the following namespaces to create the indexes:

MUX_NAMESPACES="ovirt-metrics-<ovirt_env_name> ovirt-logs-<ovirt_env_name>"

For example:
If ovirt_env_name= test-engine then the `MUX_NAMESPACES` will be:
MUX_NAMESPACES="ovirt-metrics-test-engine ovirt-logs-test-engine"

The indexes in elasticsearch will be created with "project." prefix.

Please follow the installation instructions: [Metrics Store setup on top of OpenShift](https://github.com/ViaQ/Main/blob/master/README-mux.md)

In oVirt 4.2 there will be an option to add SSO: [Metrics Store setup on top of OpenShift with oVirt Engine SSO](https://www.ovirt.org/blog/2017/05/openshift-openId-integration-with-engine-sso/)
Expand Down Expand Up @@ -111,11 +127,7 @@ This procedure will define the curator pod so that it deletes metrics indexes th
runminute: 0


5. The ovirt_env_name value represents the environment name. It is used to identify data sent from more than one oVirt engine and collected in a single central store.

Update the environment name using the following convention: Only include alphanumeric characters and hyphens ( "-" ). Name cannot begin with a hyphen or a number,
or end with a hyphen. Maximum of 49 characters. Wildcard patterns (e.g. ovirt-metrics*) cannot be used.

5. Update "ovirt_env_name". **Use the same name you configured earlier**.
6. Run

# oc rollout latest dc/logging-curator
Expand Down Expand Up @@ -157,7 +169,7 @@ Now we need to deploy and configure collectd and fluentd to send the data to the

* "/path/to/fluentd_ca_cert.pem" - The path to the fluentd CA certificate

* "ovirt_env_name" - The environment name. Can be used to identify data collected in a single central store sent from more than one oVirt engine. **Use the same name you configured earlier**.
* "ovirt_env_name" - **Use the same name you configured earlier**.

6. On the engine machine, run as root:

Expand Down