Merge pull request openshift#34819 from StephenJamesSmith/TELCODOCS-8…

…2-cluster-provisioning

modules/ztp-applying-the-ran-policies-for-monitoring-cluster-activity.adoc

@@ -5,7 +5,7 @@
 [id="ztp-applying-the-ran-policies-for-monitoring-cluster-activity_{context}"]
 = Applying the RAN policies for monitoring cluster activity
 
-Zero touch provisioning (ZTP) uses {rh-rhacm-first} as an orchestrator to apply the radio access network (RAN) policies using a policy-based governance approach to automatically monitor cluster activity.
+Zero touch provisioning (ZTP) uses {rh-rhacm-first} to apply the radio access network (RAN) policies using a policy-based governance approach to automatically monitor cluster activity.
 
 The policy generator (PolicyGen) is a Kustomize plugin that facilitates creating ACM policies from predefined custom resources.
 There are three main items: Policy Categorization, Source CR policy, and PolicyGenTemplate. PolicyGen relies on these to generate the policies and

modules/ztp-cluster-provisioning.adoc

@@ -0,0 +1,20 @@
+// Module included in the following assemblies:
+//
+// scalability_and_performance/ztp-deploying-disconnected.adoc
+
+[id="ztp-cluster-provisioning_{context}"]
+= Cluster provisioning
+
+Zero touch provisioning (ZTP) provisions clusters using a layered approach.
+The base components consist of {op-system-first}, the basic operating system
+for the cluster, and {product-title} (OCP). After these components are installed,
+the worker node can join the existing cluster. When the node has joined the existing cluster, the 5G RAN profile Operators are applied.
+
+The following RAN Operators are deployed on every cluster:
+
+* Machine Config
+* Precision Time Protocol (PTP)
+* Performance Addon Operator
+* SR-IOV
+* Local Storage Operator
+* Logging Operator

modules/ztp-machine-config-operator.adoc

@@ -0,0 +1,10 @@
+// Module included in the following assemblies:
+//
+// scalability_and_performance/ztp-deploying-disconnected.adoc
+
+[id="ztp-machine-config-operator_{context}"]
+= Machine Config Operator
+
+The Machine Config Operator enables system definitions and low-level system settings such as workload partitioning, NTP, and SCTP. This Operator is installed with  {product-title}.
+
+A performance profile and its created products are applied to a node according to an associated machine config pool (MCP). The MCP holds valuable information about the progress of applying the machine configurations created by performance addons that encompass kernel args, kube config, huge pages allocation, and deployment of the realtime kernel (rt-kernel). The performance addons controller monitors changes in the MCP and updates the performance profile status accordingly.

modules/ztp-performance-addon-operator.adoc

@@ -0,0 +1,15 @@
+// Module included in the following assemblies:
+//
+// scalability_and_performance/ztp-deploying-disconnected.adoc
+
+[id="ztp-performance-addon-operator_{context}"]
+= Performance Addon Operator
+
+The Performance Addon Operator provides the ability to enable advanced node performance tunings on a set of nodes.
+
+{product-title} (OCP) provides a Performance Addon Operator to implement automatic tuning to achieve low latency
+performance for OpenShift 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.

modules/ztp-precision-time-protocol-operator.adoc

@@ -0,0 +1,10 @@
+// Module included in the following assemblies:
+//
+// scalability_and_performance/ztp-deploying-disconnected.adoc
+
+[id="ztp-precision-time-protocol-operator_{context}"]
+= Precision Time Protocol Operator
+
+The Precision Time Protocol (PTP) Operator is a protocol used to synchronize clocks in a network. When used in conjunction with hardware support, PTP is capable of sub-microsecond accuracy. PTP support is divided between the kernel and user space.
+
+The clocks synchronized by PTP are organized in a master-worker hierarchy. The workers are synchronized to their masters, which may be workers to their own masters. The hierarchy is created and updated automatically by the best master clock (BMC) algorithm, which runs on every clock. When a clock has only one port, it can be master or worker, such a clock is called an ordinary clock (OC). A clock with multiple ports can be master on one port and worker on another, such a clock is called a boundary clock (BC). The top-level master is called the grandmaster clock, which can be synchronized by using a Global Positioning System (GPS) time source. By using a GPS-based time source, disparate networks can be synchronized with a high-degree of accuracy.

modules/ztp-sriov-operator.adoc

@@ -0,0 +1,12 @@
+// Module included in the following assemblies:
+//
+// scalability_and_performance/ztp-deploying-disconnected.adoc
+
+[id="ztp-sriov-operator_{context}"]
+= SR-IOV Operator
+
+The Single Root I/O Virtualization (SR-IOV) Network Operator manages the SR-IOV network devices and network attachments in your cluster.
+
+The SR-IOV Operator allows network interfaces to be virtual and shared at a device level with networking functions running within the cluster.
+
+The SR-IOV Network Operator adds the `SriovOperatorConfig.sriovnetwork.openshift.io` CustomResourceDefinition resource. The Operator automatically creates a SriovOperatorConfig custom resource named `default` in the `openshift-sriov-network-operator` namespace. The `default` custom resource contains the SR-IOV Network Operator configuration for your cluster.