Skip to content

Commit f2862b2

Browse files
vikram-redhatvikram-redhat
authored
Merge pull request #33875 from kquinn1204/TELCODOCS-237
TELCODOCS-237: updating version number 4.7 to 4.8
2 parents b24c6b1 + 4167aa3 commit f2862b2

6 files changed

+29
-29
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.6"
47+
image: "quay.io/openshift-kni/cnf-tests:4.8"
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
@@ -75,7 +75,7 @@ $ oc get packagemanifest performance-addon-operator -n openshift-marketplace -o
7575
.Example output
7676
[source,terminal]
7777
----
78-
4.7
78+
4.8
7979
----
8080

8181
.. 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: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ You can use the `ROLE_WORKER_CNF` variable to override the worker pool name:
6868
[source,terminal]
6969
----
7070
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e
71-
ROLE_WORKER_CNF=custom-worker-pool registry.redhat.io/openshift4/cnf-tests-rhel8:v4.6 /usr/bin/test-run.sh
71+
ROLE_WORKER_CNF=custom-worker-pool registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/test-run.sh
7272
----
7373
+
7474
[NOTE]
@@ -82,7 +82,7 @@ Assuming the `kubeconfig` file is in the current folder, the command for running
8282

8383
[source,terminal]
8484
----
85-
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.6 /usr/bin/test-run.sh
85+
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/test-run.sh
8686
----
8787

8888
This allows your `kubeconfig` file to be consumed from inside the running container.
@@ -104,7 +104,7 @@ To perform the latency tests, run the following command:
104104

105105
[source,termina]
106106
----
107-
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e LATENCY_TEST_RUN=true -e LATENCY_TEST_RUNTIME=600 -e OSLAT_MAXIMUM_LATENCY=20 registry.redhat.io/openshift4/cnf-tests-rhel8:v4.7 /usr/bin/test-run.sh
107+
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e LATENCY_TEST_RUN=true -e LATENCY_TEST_RUNTIME=600 -e OSLAT_MAXIMUM_LATENCY=20 registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/test-run.sh
108108
----
109109
[NOTE]
110110
====
@@ -114,7 +114,7 @@ You must run the latency test in discovery mode. For more information, see the D
114114
.Excerpt of a sample result of a 10-second latency test using the following command:
115115
[source,terminal]
116116
----
117-
[root@cnf12-installer ~]# podman run --rm -v $KUBECONFIG:/kubeconfig:Z -e PERF_TEST_PROFILE=worker-cnf-2 -e KUBECONFIG=/kubeconfig -e LATENCY_TEST_RUN=true -e LATENCY_TEST_RUNTIME=10 -e OSLAT_MAXIMUM_LATENCY=20 -e DISCOVERY_MODE=true registry.redhat.io/openshift4/cnf-tests-rhel8:v4.7 /usr/bin/test-run.sh
117+
[root@cnf12-installer ~]# podman run --rm -v $KUBECONFIG:/kubeconfig:Z -e PERF_TEST_PROFILE=worker-cnf-2 -e KUBECONFIG=/kubeconfig -e LATENCY_TEST_RUN=true -e LATENCY_TEST_RUNTIME=10 -e OSLAT_MAXIMUM_LATENCY=20 -e DISCOVERY_MODE=true registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/test-run.sh
118118
-ginkgo.focus="Latency"
119119
running /0_config.test -ginkgo.focus=Latency
120120
----
@@ -174,7 +174,7 @@ For example, to change the `CNF_TESTS_IMAGE` with a custom registry run the foll
174174

175175
[source,terminal]
176176
----
177-
$ 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.7 /usr/bin/test-run.sh
177+
$ 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.8 /usr/bin/test-run.sh
178178
----
179179

180180
[id="cnf-performing-end-to-end-tests-ginko-parameters_{context}"]
@@ -186,7 +186,7 @@ You can use the `-ginkgo.focus` parameter to filter a set of tests:
186186

187187
[source,terminal]
188188
----
189-
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.7 /usr/bin/test-run.sh -ginkgo.focus="performance|sctp"
189+
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/test-run.sh -ginkgo.focus="performance|sctp"
190190
----
191191

192192
You can run only the latency test using the `-ginkgo.focus` parameter.
@@ -195,7 +195,7 @@ To run only the latency test, you must provide the `-ginkgo.focus` parameter and
195195

196196
[source,terminal]
197197
----
198-
$ 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.7 /usr/bin/test-run.sh -ginkgo.focus="\[performance\]\[config\]|\[performance\]\ Latency\ Test"
198+
$ 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.8 /usr/bin/test-run.sh -ginkgo.focus="\[performance\]\[config\]|\[performance\]\ Latency\ Test"
199199
----
200200

201201
[NOTE]
@@ -223,7 +223,7 @@ Use this command to run in dry-run mode. This is useful for checking what is in
223223

224224
[source,terminal]
225225
----
226-
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.7 /usr/bin/test-run.sh -ginkgo.dryRun -ginkgo.v
226+
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/test-run.sh -ginkgo.dryRun -ginkgo.v
227227
----
228228

229229
[id="cnf-performing-end-to-end-tests-disconnected-mode_{context}"]
@@ -244,7 +244,7 @@ Run this command from an intermediate machine that has access both to the cluste
244244

245245
[source,terminal]
246246
----
247-
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.7 /usr/bin/mirror -registry my.local.registry:5000/ | oc image mirror -f -
247+
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/mirror -registry my.local.registry:5000/ | oc image mirror -f -
248248
----
249249

250250
Then, follow the instructions in the following section about overriding the registry used to fetch the images.
@@ -256,7 +256,7 @@ This is done by setting the `IMAGE_REGISTRY` environment variable:
256256

257257
[source,terminal]
258258
----
259-
$ 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.7 /usr/bin/test-run.sh
259+
$ 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.8 /usr/bin/test-run.sh
260260
----
261261

262262
[id="cnf-performing-end-to-end-tests-mirroring-to-cluster-internal-registry_{context}"]
@@ -333,7 +333,7 @@ echo "{\"auths\": { \"$REGISTRY\": { \"auth\": $TOKEN } }}" > dockerauth.json
333333
+
334334
[source,terminal]
335335
----
336-
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.6 /usr/bin/mirror -registry $REGISTRY/cnftests | oc image mirror --insecure=true -a=$(pwd)/dockerauth.json -f -
336+
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/mirror -registry $REGISTRY/cnftests | oc image mirror --insecure=true -a=$(pwd)/dockerauth.json -f -
337337
----
338338

339339
. Run the tests:
@@ -355,11 +355,11 @@ $ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAG
355355
[
356356
{
357357
"registry": "public.registry.io:5000",
358-
"image": "imageforcnftests:4.7"
358+
"image": "imageforcnftests:4.8"
359359
},
360360
{
361361
"registry": "public.registry.io:5000",
362-
"image": "imagefordpdk:4.7"
362+
"image": "imagefordpdk:4.8"
363363
}
364364
]
365365
----
@@ -368,7 +368,7 @@ $ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAG
368368
+
369369
[source,terminal]
370370
----
371-
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.6 /usr/bin/mirror --registry "my.local.registry:5000/" --images "/kubeconfig/images.json" | oc image mirror -f -
371+
$ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/mirror --registry "my.local.registry:5000/" --images "/kubeconfig/images.json" | oc image mirror -f -
372372
----
373373

374374
[id="discovery-mode_{context}"]
@@ -561,7 +561,7 @@ A JUnit-compliant XML is produced by passing the `--junit` parameter together wi
561561

562562
[source,terminal]
563563
----
564-
$ docker run -v $(pwd)/:/kubeconfig -v $(pwd)/junitdest:/path/to/junit -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.6 /usr/bin/test-run.sh --junit /path/to/junit
564+
$ docker run -v $(pwd)/:/kubeconfig -v $(pwd)/junitdest:/path/to/junit -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/test-run.sh --junit /path/to/junit
565565
----
566566

567567
[id="cnf-performing-end-to-end-tests-test-failure-report_{context}"]
@@ -571,7 +571,7 @@ A report with information about the cluster state and resources for troubleshoot
571571

572572
[source,terminal]
573573
----
574-
$ docker run -v $(pwd)/:/kubeconfig -v $(pwd)/reportdest:/path/to/report -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.6 /usr/bin/test-run.sh --report /path/to/report
574+
$ docker run -v $(pwd)/:/kubeconfig -v $(pwd)/reportdest:/path/to/report -e KUBECONFIG=/kubeconfig/kubeconfig registry.redhat.io/openshift4/cnf-tests-rhel8:v4.8 /usr/bin/test-run.sh --report /path/to/report
575575
----
576576

577577
[id="cnf-performing-end-to-end-tests-podman_{context}"]
@@ -612,9 +612,9 @@ spec:
612612
hugepages:
613613
defaultHugepagesSize: "1G"
614614
pages:
615-
-size: "1G"
616-
count: 16
617-
node: 0
615+
- size: "1G"
616+
count: 16
617+
node: 0
618618
realTimeKernel:
619619
enabled: true
620620
numa:
@@ -632,7 +632,7 @@ To override the performance profile, the manifest must be mounted inside the con
632632

633633
[source,termal]
634634
----
635-
$ 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.6 /usr/bin/test-run.sh
635+
$ 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.8 /usr/bin/test-run.sh
636636
----
637637

638638
[id="cnf-performing-end-to-end-tests-cluster-impacts_{context}"]

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ EXTERNAL-IP OS-IMAGE KERNEL-VERSION
8989
CONTAINER-RUNTIME
9090
cnf-worker-0.example.com Ready worker,worker-rt 5d17h v1.21.0
9191
128.66.135.107 <none> Red Hat Enterprise Linux CoreOS 46.82.202008252340-0 (Ootpa)
92-
4.18.0-211.rt5.23.el8.x86_64 cri-o://1.21.0-90.rhaos4.6.git4a0ac05.el8-rc.1
92+
4.18.0-211.rt5.23.el8.x86_64 cri-o://1.21.0-90.rhaos4.8.git4a0ac05.el8-rc.1
9393
[...]
9494
----
9595

‎modules/cnf-tuning-nodes-for-low-latency-via-performanceprofile.adoc‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,9 @@ spec:
2828
hugepages:
2929
defaultHugepagesSize: "1G"
3030
pages:
31-
-size: "1G"
32-
count: 16
33-
node: 0
31+
- size: "1G"
32+
count: 16
33+
node: 0
3434
realTimeKernel:
3535
enabled: true <3>
3636
numa: <4>

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

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

3939
. Access the OpenShift web console and navigate to *Operators → Installed Operators*.
4040

41-
. Click *Performance Addon Operator* to open the *Operator Details* page.
41+
. Click *Performance Addon Operator* to open the *Operator details* page.
4242

43-
. Click the *Subscription* tab to open the *Subscription Overview* page.
43+
. Click the *Subscription* tab to open the *Subscription details* page.
4444

45-
. In the *Channel* pane, click the pencil icon on the right side of the version number to open the *Change Subscription Update Channel* window.
45+
. 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.
4646

4747
. Select the next minor version. For example, if you want to upgrade to Performance Addon Operator 4.8, select *4.8*.
4848

0 commit comments

Comments
 (0)