TELCODOCS-593: reworking references to PAO

Author: rohennes

modules/sno-du-configuring-performance-addons.adoc

@@ -4,13 +4,13 @@
 
 :_content-type: PROCEDURE
 [id="sno-du-configuring-performance-addons_{context}"]
-= Configuring the Performance Addon Operator
+= Configuring the Node Tuning Operator
 
 This is a key configuration for the single node distributed unit (DU). Many of the real-time capabilities and service assurance are configured here.
 
 .Procedure
 
-* Configure the performance addons using the following example:
+* Configure the performance profile using the following example:
 +
 [source,yaml]
 ----

modules/sno-du-configuring-the-operators.adoc

@@ -6,7 +6,7 @@
 [id="sno-du-configuring-the-operators_{context}"]
 = Creating OperatorGroups for Operators
 
-This configuration is provided to enable addition of the Operators needed to configure the platform post-installation. It adds the `Namespace` and `OperatorGroup` objects for the Local Storage Operator, Logging Operator, Performance Addon Operator, PTP Operator, and SRIOV Network Operator.
+This configuration is provided to enable addition of the Operators needed to configure the platform post-installation. It adds the `Namespace` and `OperatorGroup` objects for the Local Storage Operator, Logging Operator, PTP Operator, and SR-IOV Network Operator.
 
 .Procedure
 
@@ -54,27 +54,6 @@ spec:
     - openshift-logging
 ----
 +
-.Performance Addon Operator
-+
-[source,yaml]
-----
-apiVersion: v1
-kind: Namespace
-metadata:
-  annotations:
-    workload.openshift.io/allowed: management
-  labels:
-    openshift.io/cluster-monitoring: "true"
-  name: openshift-performance-addon-operator
-spec: {}
----
-apiVersion: operators.coreos.com/v1
-kind: OperatorGroup
-metadata:
-  name: performance-addon-operator
-  namespace: openshift-performance-addon-operator
-----
-+
 .PTP Operator
 +
 [source,yaml]
@@ -98,7 +77,7 @@ spec:
     - openshift-ptp
 ----
 +
-.SRIOV Network Operator
+.SR-IOV Network Operator
 +
 [source,yaml]
 ----

modules/sno-du-subscribing-to-the-operators-needed-for-platform-configuration.adoc

@@ -41,23 +41,11 @@ spec:
 ---
 apiVersion: operators.coreos.com/v1alpha1
 kind: Subscription
-metadata:
-  name: performance-addon-operator
-  namespace: openshift-performance-addon-operator
-spec:
-  channel: "4.10" <4>
-  name: performance-addon-operator
-  source: performance-addon-operator
-  sourceNamespace: openshift-marketplace
-  installPlanApproval: Manual
----
-apiVersion: operators.coreos.com/v1alpha1
-kind: Subscription
 metadata:
     name: ptp-operator-subscription
     namespace: openshift-ptp
 spec:
-  channel: "stable" <5>
+  channel: "stable" <4>
   name: ptp-operator
   source: redhat-operators
   sourceNamespace: openshift-marketplace
@@ -69,7 +57,7 @@ metadata:
   name: sriov-network-operator-subscription
   namespace: openshift-sriov-network-operator
 spec:
-  channel: "stable" <6>
+  channel: "stable" <5>
   name: sriov-network-operator
   source: redhat-operators
   sourceNamespace: openshift-marketplace
@@ -78,6 +66,5 @@ spec:
 <1> Specify the channel to get the `cluster-logging` Operator.
 <2> Specify `Manual` or `Automatic`. In `Automatic` mode, the Operator automatically updates to the latest versions in the channel as they become available in the registry. In `Manual` mode, new Operator versions are installed only after they are explicitly approved.
 <3> Specify the channel to get the `local-storage-operator` Operator.
-<4> Specify the channel to get the `performance-addon-operator` Operator.
-<5> Specify the channel to get the `ptp-operator` Operator.
-<6> Specify the channel to get the `sriov-network-operator` Operator.
+<4> Specify the channel to get the `ptp-operator` Operator.
+<5> Specify the channel to get the `sriov-network-operator` Operator.

modules/ztp-node-tuning-operator.adoc

@@ -0,0 +1,18 @@
+// Module included in the following assemblies:
+//
+// scalability_and_performance/ztp-deploying-disconnected.adoc
+
+:_content-type: CONCEPT
+[id="ztp-node-tuning-operator_{context}"]
+= Node Tuning Operator
+
+The Node Tuning Operator provides the ability to enable advanced node performance tunings on a set of nodes.
+
+{product-title} provides a Node Tuning Operator to implement automatic tuning to achieve low latency performance for {product-title} applications. The cluster administrator uses this performance profile configuration that makes it easier to make these changes in a more reliable way.
+
+The administrator can specify updating the kernel to `rt-kernel`, reserving CPUs for management workloads, and using CPUs for running the workloads.
+
+[NOTE]
+====
+In earlier versions of {product-title}, the Performance Addon Operator was used to implement automatic tuning to achieve low latency performance for OpenShift applications. In {product-title} 4.11, these functions are part of the Node Tuning Operator. 
+====

modules/ztp-performance-addon-operator.adoc

@@ -14,10 +14,10 @@ The minimum number of reserved CPUs required for the management partition for a
 
 Workload partitioning isolates the user workloads away from the platform workloads using the normal scheduling capabilities of Kubernetes to manage the number of pods that can be placed onto those cores, and avoids mixing cluster management workloads and user workloads.
 
-When using workload partitioning, you must install the Performance Addon Operator and apply the performance profile:
+When applying workload partitioning, use the Node Tuning Operator to implement the performance profile:
 
 * Workload partitioning pins the {product-title} infrastructure pods to a defined `cpuset` configuration.
-* The Performance Addon Operator performance profile pins the systemd services to a defined `cpuset` configuration.
+* The performance profile pins the systemd services to a defined `cpuset` configuration.
 * This `cpuset` configuration must match.
 
 Workload partitioning introduces a new extended resource of `<workload-type>.workload.openshift.io/cores`

scalability_and_performance/sno-du-enabling-workload-partitioning-on-single-node-openshift.adoc

@@ -93,7 +93,7 @@ include::modules/ztp-cluster-provisioning.adoc[leveloffset=+1]
 
 include::modules/ztp-machine-config-operator.adoc[leveloffset=+2]
 
-include::modules/ztp-performance-addon-operator.adoc[leveloffset=+2]
+include::modules/ztp-node-tuning-operator.adoc[leveloffset=+2]
 
 include::modules/ztp-sriov-operator.adoc[leveloffset=+2]