Skip to content

Commit 8687caa

Browse files
author
Christopher Tauchen
authored
Merge pull request #39295 from tmulquee/TELCODOCS-389
TELCODOCS-389 - updating revision numbers
2 parents ef6982e + 2d4a19d commit 8687caa

5 files changed

+26
-26
lines changed

‎modules/cnf-configure_for_irq_dynamic_load_balancing.adoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ metadata:
4444
spec:
4545
containers:
4646
- name: dynamic-irq-pod
47-
image: "quay.io/openshift-kni/cnf-tests:4.9"
47+
image: "registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10"
4848
command: ["sleep", "10h"]
4949
resources:
5050
requests:

‎modules/cnf-installing-the-performance-addon-operator.adoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ $ oc get packagemanifest performance-addon-operator -n openshift-marketplace -o
7676
.Example output
7777
[source,terminal]
7878
----
79-
4.9
79+
4.10
8080
----
8181

8282
.. Create the following Subscription CR and save the YAML in the `pao-sub.yaml` file:

‎modules/cnf-performing-end-to-end-tests-for-platform-verification.adoc‎

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ You can use the `ROLE_WORKER_CNF` variable to override the worker pool name:
6969
[source,terminal]
7070
----
7171
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e
72-
ROLE_WORKER_CNF=custom-worker-pool registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh
72+
ROLE_WORKER_CNF=custom-worker-pool registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh
7373
----
7474
+
7575
[NOTE]
@@ -84,7 +84,7 @@ Use this command to run in dry-run mode. This is useful for checking what is in
8484

8585
[source,terminal]
8686
----
87-
$ 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
87+
$ 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
8888
----
8989

9090
[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
105105

106106
[source,terminal]
107107
----
108-
$ 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 -
108+
$ 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 -
109109
----
110110

111111
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:
117117

118118
[source,terminal]
119119
----
120-
$ 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
120+
$ 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
121121
----
122122

123123
[id="cnf-performing-end-to-end-tests-mirroring-to-cluster-internal-registry_{context}"]
@@ -214,7 +214,7 @@ echo "{\"auths\": { \"$REGISTRY\": { \"auth\": $TOKEN } }}" > dockerauth.json
214214
+
215215
[source,terminal]
216216
----
217-
$ 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 -
217+
$ 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 -
218218
----
219219

220220
. Run the tests:
@@ -236,11 +236,11 @@ $ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAG
236236
[
237237
{
238238
"registry": "public.registry.io:5000",
239-
"image": "imageforcnftests:4.9"
239+
"image": "imageforcnftests:4.10"
240240
},
241241
{
242242
"registry": "public.registry.io:5000",
243-
"image": "imagefordpdk:4.9"
243+
"image": "imagefordpdk:4.10"
244244
}
245245
]
246246
----
@@ -249,7 +249,7 @@ $ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAG
249249
+
250250
[source,terminal]
251251
----
252-
$ 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 -
252+
$ 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 -
253253
----
254254

255255
[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
343343

344344
[source,terminal]
345345
----
346-
$ 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
346+
$ 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
347347
----
348348

349349
[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:
355355

356356
[source,terminal]
357357
----
358-
$ 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"
358+
$ 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"
359359
----
360360

361361
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
364364

365365
[source,terminal]
366366
----
367-
$ 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=<performance_profile_name> registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh -ginkgo.focus="\[performance\]\[config\]|\[performance\]\ Latency\ Test"
367+
$ 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=<performance_profile_name> registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh -ginkgo.focus="\[performance\]\[config\]|\[performance\]\ Latency\ Test"
368368
----
369369

370370
[NOTE]
@@ -526,7 +526,7 @@ Assuming the `kubeconfig` file is in the current folder, the command for running
526526

527527
[source,terminal]
528528
----
529-
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh
529+
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh
530530
----
531531

532532
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:
577577

578578
[source, terminal]
579579
----
580-
$ 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”
580+
$ 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”
581581
----
582582

583583
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:
647647

648648
[source, terminal]
649649
----
650-
$ 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"
650+
$ 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"
651651
----
652652

653653
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 ...
731731
732732
[source, terminal]
733733
----
734-
$ 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"
734+
$ 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"
735735
----
736736
737737
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
845845

846846
[source,terminal]
847847
----
848-
$ 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
848+
$ 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
849849
----
850850

851851
[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
855855

856856
[source,terminal]
857857
----
858-
$ 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
858+
$ 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
859859
----
860860

861861
[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
916916

917917
[source,termal]
918918
----
919-
$ 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
919+
$ 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
920920
----

‎modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ The cluster administrator can use this performance profile configuration to make
1313

1414
[WARNING]
1515
====
16-
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.
16+
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.
1717
====
1818

1919
[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:
125125
$ oc get node -o wide
126126
----
127127

128-
Note the worker with the role `worker-rt` that contains the string `4.18.0-211.rt5.23.el8.x86_64`:
128+
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`:
129129

130130
[source,terminal]
131131
----
@@ -134,7 +134,7 @@ EXTERNAL-IP OS-IMAGE KERNEL-VERSION
134134
CONTAINER-RUNTIME
135135
rt-worker-0.example.com Ready worker,worker-rt 5d17h v1.23.0
136136
128.66.135.107 <none> Red Hat Enterprise Linux CoreOS 46.82.202008252340-0 (Ootpa)
137-
4.18.0-211.rt5.23.el8.x86_64 cri-o://1.23.0-90.rhaos4.9.git4a0ac05.el8-rc.1
137+
4.18.0-305.30.1.rt7.102.el8_4.x86_64 cri-o://1.23.0-99.rhaos4.10.gitc3131de.el8
138138
[...]
139139
----
140140

‎modules/cnf-upgrading-performance-addon-operator.adoc‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ You can manually upgrade Performance Addon Operator to the next minor version by
4545

4646
. 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.
4747

48-
. Select the next minor version. For example, if you want to upgrade to Performance Addon Operator 4.9, select *4.9*.
48+
. Select the next minor version. For example, if you want to upgrade to Performance Addon Operator 4.10, select *4.10*.
4949

5050
. Click *Save*.
5151

@@ -116,7 +116,7 @@ $ oc get csv
116116
[source,terminal]
117117
----
118118
VERSION REPLACES PHASE
119-
4.9.0 performance-addon-operator.v4.9.0 Installing
119+
4.10.0 performance-addon-operator.v4.10.0 Installing
120120
4.8.0 Replacing
121121
----
122122

@@ -131,5 +131,5 @@ VERSION REPLACES PHASE
131131
[source,terminal]
132132
----
133133
NAME DISPLAY VERSION REPLACES PHASE
134-
performance-addon-operator.v4.9.0 Performance Addon Operator 4.9.0 performance-addon-operator.v4.8.0 Succeeded
134+
performance-addon-operator.v4.10.0 Performance Addon Operator 4.10.0 performance-addon-operator.v4.8.0 Succeeded
135135
----

0 commit comments

Comments
 (0)