mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 09:46:53 +01:00
96 lines
5.5 KiB
Plaintext
96 lines
5.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * metering/metering-installing-metering.adc
|
|
|
|
[id="metering-install-verify_{context}"]
|
|
= Verifying the metering installation
|
|
|
|
You can verify the metering installation by performing any of the following checks:
|
|
|
|
* Check the Metering Operator ClusterServiceVersion (CSV) for the metering version. This can be done through either the web console or CLI.
|
|
+
|
|
--
|
|
.Procedure (UI)
|
|
. Navigate to *Operators* -> *Installed Operators* in the `openshift-metering` namespace.
|
|
. Click *Metering Operator*.
|
|
. Click *Subscription* for *Subscription Details*.
|
|
. Check the *Installed Version*.
|
|
|
|
.Procedure (CLI)
|
|
* Check the Metering Operator CSV in the `openshift-metering` namespace:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc --namespace openshift-metering get csv
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal,subs="attributes+"]
|
|
----
|
|
NAME DISPLAY VERSION REPLACES PHASE
|
|
elasticsearch-operator.{product-version}.0-202006231303.p0 Elasticsearch Operator {product-version}.0-202006231303.p0 Succeeded
|
|
metering-operator.v{product-version}.0 Metering {product-version}.0 Succeeded
|
|
----
|
|
--
|
|
|
|
* Check that all required pods in the `openshift-metering` namespace are created. This can be done through either the web console or CLI.
|
|
+
|
|
--
|
|
[NOTE]
|
|
====
|
|
Many pods rely on other components to function before they themselves can be considered ready. Some pods may restart if other pods take too long to start. This is to be expected during the Metering Operator installation.
|
|
====
|
|
|
|
.Procedure (UI)
|
|
* Navigate to *Workloads* -> *Pods* in the metering namespace and verify that pods are being created. This can take several minutes after installing the metering stack.
|
|
|
|
.Procedure (CLI)
|
|
* Check that all required pods in the `openshift-metering` namespace are created:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc -n openshift-metering get pods
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME READY STATUS RESTARTS AGE
|
|
hive-metastore-0 2/2 Running 0 3m28s
|
|
hive-server-0 3/3 Running 0 3m28s
|
|
metering-operator-68dd64cfb6-2k7d9 2/2 Running 0 5m17s
|
|
presto-coordinator-0 2/2 Running 0 3m9s
|
|
reporting-operator-5588964bf8-x2tkn 2/2 Running 0 2m40s
|
|
----
|
|
--
|
|
|
|
* Verify that the `ReportDataSources` are beginning to import data, indicated by a valid timestamp in the `EARLIEST METRIC` column. This might take several minutes. Filter out the "-raw" `ReportDataSources`, which do not import data:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get reportdatasources -n openshift-metering | grep -v raw
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME EARLIEST METRIC NEWEST METRIC IMPORT START IMPORT END LAST IMPORT TIME AGE
|
|
node-allocatable-cpu-cores 2019-08-05T16:52:00Z 2019-08-05T18:52:00Z 2019-08-05T16:52:00Z 2019-08-05T18:52:00Z 2019-08-05T18:54:45Z 9m50s
|
|
node-allocatable-memory-bytes 2019-08-05T16:51:00Z 2019-08-05T18:51:00Z 2019-08-05T16:51:00Z 2019-08-05T18:51:00Z 2019-08-05T18:54:45Z 9m50s
|
|
node-capacity-cpu-cores 2019-08-05T16:51:00Z 2019-08-05T18:29:00Z 2019-08-05T16:51:00Z 2019-08-05T18:29:00Z 2019-08-05T18:54:39Z 9m50s
|
|
node-capacity-memory-bytes 2019-08-05T16:52:00Z 2019-08-05T18:41:00Z 2019-08-05T16:52:00Z 2019-08-05T18:41:00Z 2019-08-05T18:54:44Z 9m50s
|
|
persistentvolumeclaim-capacity-bytes 2019-08-05T16:51:00Z 2019-08-05T18:29:00Z 2019-08-05T16:51:00Z 2019-08-05T18:29:00Z 2019-08-05T18:54:43Z 9m50s
|
|
persistentvolumeclaim-phase 2019-08-05T16:51:00Z 2019-08-05T18:29:00Z 2019-08-05T16:51:00Z 2019-08-05T18:29:00Z 2019-08-05T18:54:28Z 9m50s
|
|
persistentvolumeclaim-request-bytes 2019-08-05T16:52:00Z 2019-08-05T18:30:00Z 2019-08-05T16:52:00Z 2019-08-05T18:30:00Z 2019-08-05T18:54:34Z 9m50s
|
|
persistentvolumeclaim-usage-bytes 2019-08-05T16:52:00Z 2019-08-05T18:30:00Z 2019-08-05T16:52:00Z 2019-08-05T18:30:00Z 2019-08-05T18:54:36Z 9m49s
|
|
pod-limit-cpu-cores 2019-08-05T16:52:00Z 2019-08-05T18:30:00Z 2019-08-05T16:52:00Z 2019-08-05T18:30:00Z 2019-08-05T18:54:26Z 9m49s
|
|
pod-limit-memory-bytes 2019-08-05T16:51:00Z 2019-08-05T18:40:00Z 2019-08-05T16:51:00Z 2019-08-05T18:40:00Z 2019-08-05T18:54:30Z 9m49s
|
|
pod-persistentvolumeclaim-request-info 2019-08-05T16:51:00Z 2019-08-05T18:40:00Z 2019-08-05T16:51:00Z 2019-08-05T18:40:00Z 2019-08-05T18:54:37Z 9m49s
|
|
pod-request-cpu-cores 2019-08-05T16:51:00Z 2019-08-05T18:18:00Z 2019-08-05T16:51:00Z 2019-08-05T18:18:00Z 2019-08-05T18:54:24Z 9m49s
|
|
pod-request-memory-bytes 2019-08-05T16:52:00Z 2019-08-05T18:08:00Z 2019-08-05T16:52:00Z 2019-08-05T18:08:00Z 2019-08-05T18:54:32Z 9m49s
|
|
pod-usage-cpu-cores 2019-08-05T16:52:00Z 2019-08-05T17:57:00Z 2019-08-05T16:52:00Z 2019-08-05T17:57:00Z 2019-08-05T18:54:10Z 9m49s
|
|
pod-usage-memory-bytes 2019-08-05T16:52:00Z 2019-08-05T18:08:00Z 2019-08-05T16:52:00Z 2019-08-05T18:08:00Z 2019-08-05T18:54:20Z 9m49s
|
|
----
|
|
|
|
After all pods are ready and you have verified that data is being imported, you can begin using metering to collect data and report on your cluster.
|