From 606fa1205c4530a7d3afb583f3599636cc8a573d Mon Sep 17 00:00:00 2001 From: Tony Mulqueen Date: Fri, 26 Nov 2021 16:34:30 +0000 Subject: [PATCH] TELCODOCS-389 - updating revision numbers --- ...figure_for_irq_dynamic_load_balancing.adoc | 2 +- ...alling-the-performance-addon-operator.adoc | 2 +- ...o-end-tests-for-platform-verification.adoc | 36 +++++++++---------- ...g-real-time-and-low-latency-workloads.adoc | 6 ++-- ...-upgrading-performance-addon-operator.adoc | 6 ++-- 5 files changed, 26 insertions(+), 26 deletions(-) diff --git a/modules/cnf-configure_for_irq_dynamic_load_balancing.adoc b/modules/cnf-configure_for_irq_dynamic_load_balancing.adoc index be7143bbb8..e89c51507a 100644 --- a/modules/cnf-configure_for_irq_dynamic_load_balancing.adoc +++ b/modules/cnf-configure_for_irq_dynamic_load_balancing.adoc @@ -44,7 +44,7 @@ metadata: spec: containers: - name: dynamic-irq-pod - image: "quay.io/openshift-kni/cnf-tests:4.9" + image: "registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10" command: ["sleep", "10h"] resources: requests: diff --git a/modules/cnf-installing-the-performance-addon-operator.adoc b/modules/cnf-installing-the-performance-addon-operator.adoc index f879d84657..be1b834d17 100644 --- a/modules/cnf-installing-the-performance-addon-operator.adoc +++ b/modules/cnf-installing-the-performance-addon-operator.adoc @@ -76,7 +76,7 @@ $ oc get packagemanifest performance-addon-operator -n openshift-marketplace -o .Example output [source,terminal] ---- -4.9 +4.10 ---- .. Create the following Subscription CR and save the YAML in the `pao-sub.yaml` file: diff --git a/modules/cnf-performing-end-to-end-tests-for-platform-verification.adoc b/modules/cnf-performing-end-to-end-tests-for-platform-verification.adoc index a801f9711e..cf34e7290a 100644 --- a/modules/cnf-performing-end-to-end-tests-for-platform-verification.adoc +++ b/modules/cnf-performing-end-to-end-tests-for-platform-verification.adoc @@ -69,7 +69,7 @@ You can use the `ROLE_WORKER_CNF` variable to override the worker pool name: [source,terminal] ---- $ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e -ROLE_WORKER_CNF=custom-worker-pool registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh +ROLE_WORKER_CNF=custom-worker-pool registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh ---- + [NOTE] @@ -84,7 +84,7 @@ Use this command to run in dry-run mode. This is useful for checking what is in [source,terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh -ginkgo.dryRun -ginkgo.v +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh -ginkgo.dryRun -ginkgo.v ---- [id="cnf-performing-end-to-end-tests-disconnected-mode_{context}"] @@ -105,7 +105,7 @@ Run this command from an intermediate machine that has access both to the cluste [source,terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/mirror -registry my.local.registry:5000/ | oc image mirror -f - +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/mirror -registry my.local.registry:5000/ | oc image mirror -f - ---- Then, follow the instructions in the following section about overriding the registry used to fetch the images. @@ -117,7 +117,7 @@ This is done by setting the `IMAGE_REGISTRY` environment variable: [source,terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAGE_REGISTRY="my.local.registry:5000/" -e CNF_TESTS_IMAGE="custom-cnf-tests-image:latests" registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAGE_REGISTRY="my.local.registry:5000/" -e CNF_TESTS_IMAGE="custom-cnf-tests-image:latests" registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh ---- [id="cnf-performing-end-to-end-tests-mirroring-to-cluster-internal-registry_{context}"] @@ -214,7 +214,7 @@ echo "{\"auths\": { \"$REGISTRY\": { \"auth\": $TOKEN } }}" > dockerauth.json + [source,terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/mirror -registry $REGISTRY/cnftests | oc image mirror --insecure=true -a=$(pwd)/dockerauth.json -f - +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/mirror -registry $REGISTRY/cnftests | oc image mirror --insecure=true -a=$(pwd)/dockerauth.json -f - ---- . Run the tests: @@ -236,11 +236,11 @@ $ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAG [ { "registry": "public.registry.io:5000", - "image": "imageforcnftests:4.9" + "image": "imageforcnftests:4.10" }, { "registry": "public.registry.io:5000", - "image": "imagefordpdk:4.9" + "image": "imagefordpdk:4.10" } ] ---- @@ -249,7 +249,7 @@ $ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAG + [source,terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/mirror --registry "my.local.registry:5000/" --images "/kubeconfig/images.json" | oc image mirror -f - +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/mirror --registry "my.local.registry:5000/" --images "/kubeconfig/images.json" | oc image mirror -f - ---- [id="cnf-performing-end-to-end-tests-running-in-single-node-cluster_{context}"] @@ -343,7 +343,7 @@ For example, to change the `CNF_TESTS_IMAGE` with a custom registry run the foll [source,terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e CNF_TESTS_IMAGE="custom-cnf-tests-image:latests" registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e CNF_TESTS_IMAGE="custom-cnf-tests-image:latests" registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh ---- [id="cnf-performing-end-to-end-tests-ginko-parameters_{context}"] @@ -355,7 +355,7 @@ You can use the `-ginkgo.focus` parameter to filter a set of tests: [source,terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh -ginkgo.focus="performance|sctp" +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh -ginkgo.focus="performance|sctp" ---- You can run only the latency test using the `-ginkgo.focus` parameter. @@ -364,7 +364,7 @@ To run only the latency test, you must provide the `-ginkgo.focus` parameter and [source,terminal] ---- -$ docker run --rm -v $KUBECONFIG:/kubeconfig -e KUBECONFIG=/kubeconfig -e LATENCY_TEST_RUN=true -e LATENCY_TEST_RUNTIME=600 -e OSLAT_MAXIMUM_LATENCY=20 -e PERF_TEST_PROFILE= registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh -ginkgo.focus="\[performance\]\[config\]|\[performance\]\ Latency\ Test" +$ docker run --rm -v $KUBECONFIG:/kubeconfig -e KUBECONFIG=/kubeconfig -e LATENCY_TEST_RUN=true -e LATENCY_TEST_RUNTIME=600 -e OSLAT_MAXIMUM_LATENCY=20 -e PERF_TEST_PROFILE= registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh -ginkgo.focus="\[performance\]\[config\]|\[performance\]\ Latency\ Test" ---- [NOTE] @@ -526,7 +526,7 @@ Assuming the `kubeconfig` file is in the current folder, the command for running [source,terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh ---- This allows your `kubeconfig` file to be consumed from inside the running container. @@ -577,7 +577,7 @@ To perform the `hwlatdetect`, run the following command: [source, terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e LATENCY_TEST_RUN=true -e DISCOVERY_MODE=true -e ROLE_WORKER_CNF=worker-cnf -e LATENCY_TEST_RUNTIME=600 -e MAXIMUM_LATENCY=20 registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh -ginko.focus=”hwladetect” +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e LATENCY_TEST_RUN=true -e DISCOVERY_MODE=true -e ROLE_WORKER_CNF=worker-cnf -e LATENCY_TEST_RUNTIME=600 -e MAXIMUM_LATENCY=20 registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh -ginko.focus=”hwladetect” ---- The above command runs the `hwlatdetect` tool for 10 minutes (600 seconds). The test runs successfully when the maximum observed latency is lower than `MAXIMUM_LATENCY` (20 μs), and the command line displays `SUCCESS!`. @@ -647,7 +647,7 @@ To perform the `cyclictest`, run the following command: [source, terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e LATENCY_TEST_RUN=true -e DISCOVERY_MODE=true -e ROLE_WORKER_CNF=worker-cnf -e LATENCY_TEST_CPUS=10 -e LATENCY_TEST_RUNTIME=600 -e MAXIMUM_LATENCY=20 registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh -ginkgo.focus="cyclictest" +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e LATENCY_TEST_RUN=true -e DISCOVERY_MODE=true -e ROLE_WORKER_CNF=worker-cnf -e LATENCY_TEST_CPUS=10 -e LATENCY_TEST_RUNTIME=600 -e MAXIMUM_LATENCY=20 registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh -ginkgo.focus="cyclictest" ---- The above command runs the `cyclictest` tool for 10 minutes (600 seconds). The test runs successfully when the maximum observed latency is lower than `MAXIMUM_LATENCY` (20 μs), and the command line displays `SUCCESS!`. @@ -731,7 +731,7 @@ More histogram entries ... [source, terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e LATENCY_TEST_RUN=true -e DISCOVERY_MODE=true -e ROLE_WORKER_CNF=worker-cnf -e LATENCY_TEST_CPUS=7 -e LATENCY_TEST_RUNTIME=600 -e MAXIMUM_LATENCY=20 registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh -ginkgo.focus="oslat" +$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e LATENCY_TEST_RUN=true -e DISCOVERY_MODE=true -e ROLE_WORKER_CNF=worker-cnf -e LATENCY_TEST_CPUS=7 -e LATENCY_TEST_RUNTIME=600 -e MAXIMUM_LATENCY=20 registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh -ginkgo.focus="oslat" ---- The above command runs the `cyclictest` tool for 10 minutes (600 seconds). The test runs successfully when the maximum observed latency is lower than `MAXIMUM_LATENCY` (20 μs), and the command line displays `SUCCESS!`. @@ -845,7 +845,7 @@ A JUnit-compliant XML is produced by passing the `--junit` parameter together wi [source,terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -v $(pwd)/junitdest:/path/to/junit -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh --junit /path/to/junit +$ docker run -v $(pwd)/:/kubeconfig -v $(pwd)/junitdest:/path/to/junit -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh --junit /path/to/junit ---- [id="cnf-performing-end-to-end-tests-test-failure-report_{context}"] @@ -855,7 +855,7 @@ A report with information about the cluster state and resources for troubleshoot [source,terminal] ---- -$ docker run -v $(pwd)/:/kubeconfig -v $(pwd)/reportdest:/path/to/report -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh --report /path/to/report +$ docker run -v $(pwd)/:/kubeconfig -v $(pwd)/reportdest:/path/to/report -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh --report /path/to/report ---- [id="cnf-performing-end-to-end-tests-podman_{context}"] @@ -916,5 +916,5 @@ To override the performance profile, the manifest must be mounted inside the con [source,termal] ---- -$ docker run -v $(pwd)/:/kubeconfig:Z -e KUBECONFIG=/kubeconfig/kubeconfig -e PERFORMANCE_PROFILE_MANIFEST_OVERRIDE=/kubeconfig/manifest.yaml registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh +$ docker run -v $(pwd)/:/kubeconfig:Z -e KUBECONFIG=/kubeconfig/kubeconfig -e PERFORMANCE_PROFILE_MANIFEST_OVERRIDE=/kubeconfig/manifest.yaml registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh ---- diff --git a/modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc b/modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc index 586f6953f3..7d31f7dff8 100644 --- a/modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc +++ b/modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc @@ -13,7 +13,7 @@ The cluster administrator can use this performance profile configuration to make [WARNING] ==== -The usage of execution probes in conjunction with applications that require guaranteed CPUs can cause latency spikes. It is recommended to use other probes, such as a properly configured set of network probes, as an alternative. +The usage of execution probes in conjunction with applications that require guaranteed CPUs can cause latency spikes. It is recommended to use other probes, such as a properly configured set of network probes, as an alternative. ==== [id="performance-addon-operator-known-limitations-for-real-time_{context}"] @@ -125,7 +125,7 @@ Use this command to verify that the real-time kernel is installed: $ oc get node -o wide ---- -Note the worker with the role `worker-rt` that contains the string `4.18.0-211.rt5.23.el8.x86_64`: +Note the worker with the role `worker-rt` that contains the string `4.18.0-305.30.1.rt7.102.el8_4.x86_64 cri-o://1.23.0-99.rhaos4.10.gitc3131de.el8`: [source,terminal] ---- @@ -134,7 +134,7 @@ EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME rt-worker-0.example.com Ready worker,worker-rt 5d17h v1.23.0 128.66.135.107 Red Hat Enterprise Linux CoreOS 46.82.202008252340-0 (Ootpa) -4.18.0-211.rt5.23.el8.x86_64 cri-o://1.23.0-90.rhaos4.9.git4a0ac05.el8-rc.1 +4.18.0-305.30.1.rt7.102.el8_4.x86_64 cri-o://1.23.0-99.rhaos4.10.gitc3131de.el8 [...] ---- diff --git a/modules/cnf-upgrading-performance-addon-operator.adoc b/modules/cnf-upgrading-performance-addon-operator.adoc index 7666d2a7ab..e33720fda0 100644 --- a/modules/cnf-upgrading-performance-addon-operator.adoc +++ b/modules/cnf-upgrading-performance-addon-operator.adoc @@ -45,7 +45,7 @@ You can manually upgrade Performance Addon Operator to the next minor version by . In the *Update channel* pane, click the pencil icon on the right side of the version number to open the *Change Subscription update channel* window. -. Select the next minor version. For example, if you want to upgrade to Performance Addon Operator 4.9, select *4.9*. +. Select the next minor version. For example, if you want to upgrade to Performance Addon Operator 4.10, select *4.10*. . Click *Save*. @@ -116,7 +116,7 @@ $ oc get csv [source,terminal] ---- VERSION REPLACES PHASE -4.9.0 performance-addon-operator.v4.9.0 Installing +4.10.0 performance-addon-operator.v4.10.0 Installing 4.8.0 Replacing ---- @@ -131,5 +131,5 @@ VERSION REPLACES PHASE [source,terminal] ---- NAME DISPLAY VERSION REPLACES PHASE -performance-addon-operator.v4.9.0 Performance Addon Operator 4.9.0 performance-addon-operator.v4.8.0 Succeeded +performance-addon-operator.v4.10.0 Performance Addon Operator 4.10.0 performance-addon-operator.v4.8.0 Succeeded ----