Merge pull request #67007 from aireilly/ztp-414-updates

TELCODOCS-1385 - ZTP 4.14 updates

Author: aireilly

.vale/styles/Vocab/OpenShiftDocs/accept.txt

@@ -15,3 +15,6 @@ Operator
 Operators
 [Pp]reinstall
 [Pp]ostinstall
+NICs?
+Mellanox
+VFs?

images/319_OpenShift_PTP_bare-metal_OCP_nodes_1023_RAN_DU.png

@@ -18,6 +18,6 @@ A high-level overview of using {ztp} to provision and maintain bare-metal hosts
 
 * You make the hosts ready for provisioning as managed clusters, and use {rh-rhacm} and the assisted service to install the bare-metal hosts on site.
 
-Installing and deploying the clusters is a two-stage process, involving an initial installation phase, and a subsequent configuration phase. The following diagram illustrates this workflow:
+Installing and deploying the clusters is a two-stage process, involving an initial installation phase, and a subsequent configuration and deployment phase. The following diagram illustrates this workflow:
 
-image::217_OpenShift_Zero_Touch_Provisioning_updates_1022_2.png[Using GitOps and {ztp} to install and deploy managed clusters]
+image::474_OpenShift_OpenShift_RAN_RDS_arch_updates_1023.png[Using GitOps and {ztp} to install and deploy managed clusters]

images/474_OpenShift_OpenShift_RAN_RDS_arch_updates_1023.png

@@ -8,7 +8,7 @@
 
 The following `MachineConfig` CR configures core OpenShift processes and containers to use all available CPU cores during system startup and shutdown. This accelerates the system recovery during initial boot and reboots.
 
-.Recommended accelerated container startup configuration (04-accelerated-container-startup-master.yaml)
+.Recommended accelerated container startup configuration (`04-accelerated-container-startup-master.yaml`)
 [source,yaml]
 ----
 include::snippets/ztp_04-accelerated-container-startup-master.yaml[]

modules/about-ztp.adoc

@@ -15,13 +15,13 @@ For optimal performance, enable crun for control plane and worker nodes in {sno}
 To avoid the cluster rebooting when the CR is applied, apply the change as a {ztp} additional Day 0 install-time manifest.
 ====
 
-.Recommended ContainerRuntimeConfig CR for control plane nodes (enable-crun-master.yaml)
+.Recommended `ContainerRuntimeConfig` CR for control plane nodes (`enable-crun-master.yaml`)
 [source,yaml]
 ----
 include::snippets/ztp_enable-crun-master.yaml[]
 ----
 
-.Recommended ContainerRuntimeConfig CR for worker nodes (enable-crun-worker.yaml)
+.Recommended `ContainerRuntimeConfig` CR for worker nodes (`enable-crun-worker.yaml`)
 [source,yaml]
 ----
 include::snippets/ztp_enable-crun-worker.yaml[]

modules/ztp-sno-du-accelerating-container-startup.adoc

@@ -8,13 +8,13 @@
 
 {sno-caps} clusters that run DU workloads require logging and log forwarding for debugging. The following `ClusterLogging` and `ClusterLogForwarder` custom resources (CRs) are required.
 
-.Recommended cluster logging and log forwarding configuration
+.Recommended cluster logging configuration (`ClusterLogging.yaml`)
 [source,yaml]
 ----
 include::snippets/ztp_ClusterLogging.yaml[]
 ----
 
-.Recommended log forwarding configuration
+.Recommended log forwarding configuration (`ClusterLogForwarder.yaml`)
 [source,yaml]
 ----
 include::snippets/ztp_ClusterLogForwarder.yaml[]

modules/ztp-sno-du-configuring-crun-container-runtime.adoc

@@ -15,13 +15,13 @@ The recommended storage solution for {sno} is the Local Storage Operator. Altern
 
 The following YAML example configures the storage of the node to be available to {product-title} applications.
 
-.Recommended LVMCluster configuration (StorageLVMCluster.yaml)
+.Recommended `LVMCluster` configuration (`StorageLVMCluster.yaml`)
 [source,yaml]
 ----
 include::snippets/ztp_StorageLVMCluster.yaml[]
 ----
 
-.LVMCluster CR options for {sno} clusters
+.`LVMCluster` CR options for {sno} clusters
 [cols=2*, width="90%", options="header"]
 |====
 |LVMCluster CR field

modules/ztp-sno-du-configuring-logging-locally-and-forwarding.adoc

@@ -15,7 +15,7 @@ In earlier versions of {product-title}, the Performance Addon Operator was used
 
 The following example `PerformanceProfile` CR illustrates the required {sno} cluster configuration.
 
-.Recommended performance profile configuration
+.Recommended performance profile configuration (`PerformanceProfile.yaml`)
 [source,yaml]
 ----
 include::snippets/ztp_PerformanceProfile.yaml[]

modules/ztp-sno-du-configuring-lvms.adoc

@@ -6,10 +6,33 @@
 [id="ztp-sno-du-configuring-ptp_{context}"]
 = PTP
 
-{sno-caps} clusters use Precision Time Protocol (PTP) for network time synchronization. The following example `PtpConfig` CR illustrates the required PTP slave configuration.
+{sno-caps} clusters use Precision Time Protocol (PTP) for network time synchronization.
+The following example `PtpConfig` CRs illustrate the required PTP configurations for ordinary clocks, boundary clocks, and grandmaster clocks.
+The exact configuration you apply will depend on the node hardware and specific use case.
 
-.Recommended PTP configuration
+.Recommended PTP ordinary clock configuration (`PtpConfigSlave.yaml`)
 [source,yaml]
 ----
 include::snippets/ztp_PtpConfigSlave.yaml[]
 ----
+
+
+.Recommended boundary clock configuration (`PtpConfigBoundary.yaml`)
+[source,yaml]
+----
+include::snippets/ztp_PtpConfigBoundary.yaml[]
+----
+
+.Recommended PTP Westport Channel e810 grandmaster clock configuration (`PtpConfigGmWpc.yaml`)
+[source,yaml]
+----
+include::snippets/ztp_PtpConfigGmWpc.yaml[]
+----
+
+The following optional `PtpOperatorConfig` CR configures PTP events reporting for the node.
+
+.Recommended PTP events configuration (`PtpOperatorConfigForEvent.yaml`)
+[source,yaml]
+----
+include::snippets/ztp_PtpOperatorConfigForEvent.yaml[]
+----