Merge pull request #47958 from rohennes/TELCODOCS-809-PAO-cleanup

TELCODOCS#809: Reworking any remaining references of PAO with references to NTO, including IDs and file names

Author: opayne1

modules/cnf-about-the-profile-creator-tool.adoc

@@ -6,7 +6,7 @@
 [id="cnf-about-the-profile-creator-tool_{context}"]
 = About the Performance Profile Creator
 
-The Performance Profile Creator (PPC) is a command-line tool, delivered with the Performance Addon Operator, used to create the performance profile.
+The Performance Profile Creator (PPC) is a command-line tool, delivered with the Node Tuning Operator, used to create the performance profile.
 The tool consumes `must-gather` data from the cluster and several user-supplied profile arguments. The PPC generates a performance profile that is appropriate for your hardware and topology.
 
 The tool is run by one of the following methods:

modules/cnf-about_hyperthreading_for_low_latency_and_real_time_applications.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc
+// scalability_and_performance/cnf-low-latency-tuning.adoc
 
 :_content-type: CONCEPT
 [id="about_hyperthreading_for_low_latency_and_real_time_applications_{context}"]

modules/cnf-adjusting-nic-queues-with-the-performance-profile.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //CNF-1483 (4.8)
-// * scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc
+// * scalability_and_performance/low-latency-tuning.adoc
 
 :_content-type: PROCEDURE
 [id="adjusting-nic-queues-with-the-performance-profile_{context}"]
@@ -29,7 +29,7 @@ Unsupported network devices:
 
 .Procedure
 
-. Log in to the {product-title} cluster running the Performance Addon Operator as a user with `cluster-admin` privileges.
+. Log in to the {product-title} cluster running the Node Tuning Operator as a user with `cluster-admin` privileges.
 
 . Create and apply a performance profile appropriate for your hardware and topology. For guidance on creating a profile, see the "Creating a performance profile" section.
 

modules/cnf-allocating-multiple-huge-page-sizes.adoc

@@ -1,14 +1,14 @@
 // CNF-538 Promote Multiple Huge Pages Sizes for Pods and Containers to beta
 // Module included in the following assemblies:
 //
-// *scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc
+// *scalability_and_performance/cnf-low-latency-tuning.adoc
 
 [id="cnf-allocating-multiple-huge-page-sizes_{context}"]
 = Allocating multiple huge page sizes
 
 You can request huge pages with different sizes under the same container. This allows you to define more complicated pods consisting of containers with different huge page size needs.
 
-For example, you can define sizes `1G` and `2M` and the Performance Addon Operator will configure both sizes on the node, as shown here:
+For example, you can define sizes `1G` and `2M` and the Node Tuning Operator will configure both sizes on the node, as shown here:
 
 [source,yaml]
 ----
@@ -22,4 +22,4 @@ spec:
     - count: 4
       node: 1
       size: 1G
-----
+----

modules/cnf-collecting-low-latency-tuning-debugging-data-for-red-hat-support.adoc

@@ -1,7 +1,7 @@
 // CNF-643 Support and debugging tools for CNF
 // Module included in the following assemblies:
 //
-// *scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc
+// *scalability_and_performance/cnf-low-latency-tuning.adoc
 
 :_content-type: PROCEDURE
 [id="cnf-collecting-low-latency-tuning-debugging-data-for-red-hat-support_{context}"]
@@ -29,20 +29,25 @@ You can specify one or more images when you run the command by including the `--
 
 Use the `oc adm must-gather` CLI command to collect information about your cluster, including features and objects associated with low latency tuning, including:
 
-* The Performance Addon Operator namespaces and child objects.
+* The Node Tuning Operator namespaces and child objects.
 * `MachineConfigPool` and associated `MachineConfig` objects.
 * The Node Tuning Operator and associated Tuned objects.
 * Linux Kernel command line options.
 * CPU and NUMA topology
 * Basic PCI device information and NUMA locality.
 
-To collect Performance Addon Operator debugging information with `must-gather`, you must specify the Performance Addon Operator `must-gather` image:
+To collect debugging information with `must-gather`, you must specify the Performance Addon Operator `must-gather` image:
 
 [source,terminal,subs="attributes+"]
 ----
 --image=registry.redhat.io/openshift4/performance-addon-operator-must-gather-rhel8:v{product-version}.
 ----
 
+[NOTE]
+====
+In earlier versions of {product-title}, the Performance Addon Operator provided automatic, low latency performance tuning for applications. In {product-title} 4.11, these functions are part of the Node Tuning Operator. However, you must still use the `performance-addon-operator-must-gather` image when running the `must-gather` command.
+====
+
 [id="cnf-about-gathering-data_{context}"]
 == Gathering data about specific features
 
@@ -53,6 +58,11 @@ You can gather debugging information about specific features by using the `oc ad
 To collect the default `must-gather` data in addition to specific feature data, add the `--image-stream=openshift/must-gather` argument.
 ====
 
+[NOTE]
+====
+In earlier versions of {product-title}, the Performance Addon Operator provided automatic, low latency performance tuning for applications. In {product-title} 4.11, these functions are part of the Node Tuning Operator. However, you must still use the `performance-addon-operator-must-gather` image when running the `must-gather` command.
+====
+
 .Prerequisites
 
 * Access to the cluster as a user with the `cluster-admin` role.
@@ -62,7 +72,7 @@ To collect the default `must-gather` data in addition to specific feature data,
 
 . Navigate to the directory where you want to store the `must-gather` data.
 
-. Run the `oc adm must-gather` command with one or more `--image` or `--image-stream` arguments. For example, the following command gathers both the default cluster data and information specific to the Performance Addon Operator:
+. Run the `oc adm must-gather` command with one or more `--image` or `--image-stream` arguments. For example, the following command gathers both the default cluster data and information specific to the Node Tuning Operator:
 +
 [source,terminal,subs="attributes+"]
 ----

modules/cnf-configure_for_irq_dynamic_load_balancing.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc
+// scalability_and_performance/cnf-low-latency-tuning.adoc
 
 [id="configuring_for_irq_dynamic_load_balancing_{context}"]
 = Configuring a node for IRQ dynamic load balancing

modules/cnf-configuring-huge-pages.adoc

@@ -1,13 +1,13 @@
 // Module included in the following assemblies:
 //CNF-78 (4.4)
-// * scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc
+// * scalability_and_performance/cnf-low-latency-tuning.adoc
 
 [id="cnf-configuring-huge-pages_{context}"]
 = Configuring huge pages
 
-Nodes must pre-allocate huge pages used in an {product-title} cluster. Use the Performance Addon Operator to allocate huge pages on a specific node.
+Nodes must pre-allocate huge pages used in an {product-title} cluster. Use the Node Tuning Operator to allocate huge pages on a specific node.
 
-{product-title} provides a method for creating and allocating huge pages. Performance Addon Operator provides an easier method for doing  this using the performance profile.
+{product-title} provides a method for creating and allocating huge pages. Node Tuning Operator provides an easier method for doing  this using the performance profile.
 
 For example, in the `hugepages` `pages` section of the performance profile, you can specify multiple blocks of `size`, `count`, and, optionally, `node`:
 

modules/cnf-configuring-workload-hints.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc
+// scalability_and_performance/cnf-low-latency-tuning.adoc
 
 :_content-type: CONCEPT
 [id="configuring-workload-hints_{context}"]

modules/cnf-cpu-infra-container.adoc

@@ -1,12 +1,12 @@
 // Module included in the following assemblies:
 //
-// scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc
+// scalability_and_performance/cnf-low-latency-tuning.adoc
 
 :_content-type: PROCEDURE
 [id="cnf-cpu-infra-container_{context}"]
 = Restricting CPUs for infra and application containers
 
-Generic housekeeping and workload tasks use CPUs in a way that may impact latency-sensitive processes. By default, the container runtime uses all online CPUs to run all containers together, which can result in context switches and spikes in latency. Partitioning the CPUs prevents noisy processes from interfering with latency-sensitive processes by separating them from each other. The following table describes how processes run on a CPU after you have tuned the node using the Performance Add-On Operator:
+Generic housekeeping and workload tasks use CPUs in a way that may impact latency-sensitive processes. By default, the container runtime uses all online CPUs to run all containers together, which can result in context switches and spikes in latency. Partitioning the CPUs prevents noisy processes from interfering with latency-sensitive processes by separating them from each other. The following table describes how processes run on a CPU after you have tuned the node using the Node Tuning Operator:
 
 .Process' CPU assignments
 [%header,cols=2*]

modules/cnf-creating-the-performance-profile-object.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 // Epic CNF-78
-// * scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc
+// * scalability_and_performance/cnf-low-latency-tuning.adoc
 
 [id="cnf-creating-the-performance-profile-object_{context}"]
 = Creating the PerformanceProfile object