Skip to content

Commit 00788aa

Browse files
author
Padraig O'Grady
committed
TELCODOCS-1990: Docfooding feedback openshift#6 applied
1 parent f5b2c1b commit 00788aa

5 files changed

+5
-25
lines changed

modules/cnf-performing-end-to-end-tests-running-cyclictest.adoc

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -13,14 +13,6 @@ The `cyclictest` tool measures the real-time kernel scheduler latency on the spe
1313
When executing `podman` commands as a non-root or non-privileged user, mounting paths can fail with `permission denied` errors. To make the `podman` command work, append `:Z` to the volumes creation; for example, `-v $(pwd)/:/kubeconfig:Z`. This allows `podman` to do the proper SELinux relabeling.
1414
====
1515

16-
.Prerequisites
17-
18-
* You have logged in to `registry.redhat.io` with your Customer Portal credentials.
19-
20-
* You have installed the real-time kernel in the cluster.
21-
22-
* You have applied a cluster performance profile by using Node Tuning Operator.
23-
2416
.Procedure
2517

2618
* To perform the `cyclictest`, run the following command, substituting variable values as appropriate:

modules/cnf-performing-end-to-end-tests-running-hwlatdetect.adoc

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,12 +13,6 @@ The `hwlatdetect` tool is available in the `rt-kernel` package with a regular su
1313
When executing `podman` commands as a non-root or non-privileged user, mounting paths can fail with `permission denied` errors. To make the `podman` command work, append `:Z` to the volumes creation; for example, `-v $(pwd)/:/kubeconfig:Z`. This allows `podman` to do the proper SELinux relabeling.
1414
====
1515

16-
.Prerequisites
17-
18-
* You have installed the real-time kernel in the cluster.
19-
20-
* You have logged in to `registry.redhat.io` with your Customer Portal credentials.
21-
2216
.Procedure
2317

2418
* To run the `hwlatdetect` tests, run the following command, substituting variable values as appropriate:

modules/cnf-performing-end-to-end-tests-running-oslat.adoc

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,6 @@ The `oslat` test simulates a CPU-intensive DPDK application and measures all the
1313
When executing `podman` commands as a non-root or non-privileged user, mounting paths can fail with `permission denied` errors. To make the `podman` command work, append `:Z` to the volumes creation; for example, `-v $(pwd)/:/kubeconfig:Z`. This allows `podman` to do the proper SELinux relabeling.
1414
====
1515

16-
.Prerequisites
17-
18-
* You have logged in to `registry.redhat.io` with your Customer Portal credentials.
19-
* You have applied a cluster performance profile by using the Node Tuning Operator.
20-
2116
.Procedure
2217

2318
* To perform the `oslat` test, run the following command, substituting variable values as appropriate:

modules/cnf-performing-end-to-end-tests-running-the-tests.adoc

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,6 @@ Run the cluster latency tests to validate node tuning for your Cloud-native Netw
1313
When executing `podman` commands as a non-root or non-privileged user, mounting paths can fail with `permission denied` errors. Depending on your local OS and SELinux configuration, you might also experience issues running these commands from your home directory. To make the `podman` commands work, run the commands from a folder that is not your home directory, and append `:Z` to the volumes creation. For example, `-v $(pwd)/:/kubeconfig:Z`. This allows `podman` to do the proper SELinux relabeling.
1414
====
1515

16-
.Prerequisites
17-
18-
* Using the `podman login` command, you have logged in to `registry.redhat.io` with your Customer Portal credentials.
19-
20-
2116
.Procedure
2217

2318
. Open a shell prompt in the directory containing the `kubeconfig` file.

scalability_and_performance/low_latency_tuning/cnf-performing-platform-verification-latency-tests.adoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,12 +15,16 @@ The `cnf-tests` container image is available at `registry.redhat.io/openshift4/c
1515

1616
Your cluster must meet the following requirements before you can run the latency tests:
1717

18-
. You have configured a performance profile with the Node Tuning Operator.
18+
. You have installed the real-time kernel in the cluster.
1919

2020
. You have applied all the required CNF configurations in the cluster.
2121

22+
. You have applied and configured a cluster performance profile by using the Node Tuning Operator.
23+
2224
. You have a pre-existing `MachineConfigPool` CR applied in the cluster. The default worker pool is `worker-cnf`.
2325

26+
. You have logged in to `registry.redhat.io` with your Customer Portal credentials by using the `podman login` command.
27+
2428
[role="_additional-resources"]
2529
.Additional resources
2630

0 commit comments

Comments
 (0)