Merge pull request #75650 from aireilly/rds-4.14-ptp-features

Author: aireilly

modules/telco-core-414-whats-new-ref-design.adoc renamed to modules/telco-core-whats-new-ref-design.adoc

@@ -41,4 +41,6 @@ Use a default offset of less than or equal to 5.
 Engineering considerations::
 * Configurations are provided for ordinary clock, boundary clock, or grandmaster clock
 
-* PTP fast event notifications uses `ConfigMap` CRs to store PTP event subscriptions.
+* PTP fast event notifications uses `ConfigMap` CRs to store PTP event subscriptions
+
+* Use Intel E810-XXV-4T Westport Channel NICs for PTP grandmaster clocks with GPS timing, minimum firmware version 4.40

modules/telco-ran-ptp-operator.adoc

@@ -3,7 +3,7 @@
 // * telco_ref_design_specs/ran/telco-ran-ref-design-spec.adoc
 
 :_mod-docs-content-type: CONCEPT
-[id="telco-ran-414-ref-design-features_{context}"]
+[id="telco-ran-ref-design-features_{context}"]
 = {product-title} {product-version} features for {rds}
 
 The following features that are included in {product-title} {product-version} and are leveraged by the {rds} reference design specification (RDS) have been added or updated.
@@ -26,27 +26,25 @@ a|You can now use custom CRs alongside the reference configuration CRs provided
 
 * link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-advanced-policy-config.html#ztp-adding-new-content-to-gitops-ztp_ztp-advanced-policy-config[Adding custom content to the {ztp} pipeline]
 
-//CNF-7078
-//|Intel Westport Channel e810 NIC as PTP Grandmaster clock
-//a|You can use the Intel Westport Channel E810-XXVDA4T as a GNSS-sourced grandmaster clock.
-//The NIC is automatically configured by the PTP Operator with the E810 hardware plugin.
-//This feature is scheduled for an upcoming 4.14 z-stream release.
+//CNF-8035
+|Using custom node labels in the `SiteConfig` CR with {ztp}
+a|You can now use the `nodeLabels` field in the `SiteConfig` CR to create custom roles for nodes in managed clusters.
 
-//* link:https://docs.openshift.com/container-platform/4.14/networking/using-ptp.html#configuring-linuxptp-services-as-grandmaster-clock_using-ptp[Configuring linuxptp services as a grandmaster clock]
+* link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-deploying-far-edge-sites.html#ztp-sno-siteconfig-config-reference_ztp-deploying-far-edge-sites[{sno-caps} SiteConfig CR installation reference]
 
-//CNF-6527
-//|PTP Operator hardware specific functionality plugin
-//a|A new E810 NIC hardware plugin is now available in the PTP Operator.
-//You can use the E810 plugin to configure the NIC directly.
-//This feature is scheduled for an upcoming 4.14 z-stream release.
+//CNF-7078
+|Intel Westport Channel e810 NIC as PTP Grandmaster clock (Technology Preview)
+a|You can use the Intel Westport Channel E810-XXVDA4T as a GNSS-sourced grandmaster clock.
+The NIC is automatically configured by the PTP Operator with the E810 hardware plugin.
 
-// * link:https://docs.openshift.com/container-platform/4.14/networking/ptp/configuring-ptp.html#nw-ptp-wpc-hardware-pins-reference_configuring-ptp[Intel Westport Channel E810 hardware configuration reference]
+* link:https://docs.openshift.com/container-platform/4.14/networking/ptp/configuring-ptp.html#configuring-linuxptp-services-as-grandmaster-clock-dual-nic_configuring-ptp[Configuring linuxptp services as a grandmaster clock for dual E810 Westport Channel NICs]
 
-//CNF-8035
-|Using custom node labels in the `SiteConfig` CR with {ztp}
-a|you can now use the `nodeLabels` field in the `SiteConfig` CR to create custom roles for nodes in managed clusters.
+//CNF-6527
+|PTP Operator hardware specific functionality plugin (Technology Preview)
+a|A new E810 NIC hardware plugin is now available in the PTP Operator.
+You can use the E810 plugin to configure the NIC directly.
 
-* link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-deploying-far-edge-sites.html#ztp-sno-siteconfig-config-reference_ztp-deploying-far-edge-sites[{sno} SiteConfig CR installation reference]
+* link:https://docs.openshift.com/container-platform/4.14/networking/ptp/configuring-ptp.html#nw-ptp-wpc-hardware-pins-reference_configuring-ptp[Intel Westport Channel E810 hardware configuration reference]
 
 //OCPBUGS-13050, CTONET-3072
 |PTP events and metrics
@@ -60,11 +58,17 @@ a|You can now precache application workload images before upgrading your applica
 
 * link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-precaching-tool.html#ztp-pre-staging-tool[Precaching images for {sno} deployments]
 
-//CNF-6318
+//CNF-6318, OCPVE-630
 |Using OpenShift capabilities to further reduce the {sno} DU footprint
 a|Use cluster capabilities to enable or disable optional components before you install the cluster.
 In {product-title} {product-version}, the following optional capabilities are available:
-`baremetal`, `marketplace`, `openshift-samples`, `Console`, `Insights`, `Storage`, `CSISnapshot`, `NodeTuning`, `MachineAPI`. The reference configuration includes only those features required for RAN DU.
+`image-registry`, `baremetal`, `marketplace`, `openshift-samples`, `Console`, `Insights`, `Storage`, `CSISnapshot`, `NodeTuning`, `MachineAPI`. The reference configuration includes only those features required for RAN DU.
 
 * link:https://docs.openshift.com/container-platform/4.15/installing/cluster-capabilities.html#cluster-capabilities[Cluster capabilities]
+
+//CNF-5997
+|Set `vectord` as the default log collector in the DU profile
+a| {sno} clusters that run DU workloads require logging and log forwarding.
+
+* link:https://docs.openshift.com/container-platform/4.14/scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.html#ztp-sno-du-configuring-logging-locally-and-forwarding_sno-configure-for-vdu[Cluster logging and log forwarding]
 |====

modules/telco-ran-414-ref-design-features.adoc renamed to modules/telco-ran-ref-design-features.adoc

@@ -9,6 +9,6 @@ toc::[]
 
 The {rds} reference design specification (RDS) configures a {product-title} cluster running on commodity hardware to host {rds} workloads.
 
-include::modules/telco-core-414-whats-new-ref-design.adoc[leveloffset=+1]
+include::modules/telco-core-whats-new-ref-design.adoc[leveloffset=+1]
 
 :!telco-core:

telco_ref_design_specs/core/telco-core-rds-overview.adoc

@@ -10,7 +10,7 @@ toc::[]
 The {rds-first} {product-version} reference design configures an {product-title} {product-version} cluster running on commodity hardware to host {rds} workloads.
 It captures the recommended, tested, and supported configurations to get reliable and repeatable performance for a cluster running the {rds} profile.
 
-include::modules/telco-ran-414-ref-design-features.adoc[leveloffset=+1]
+include::modules/telco-ran-ref-design-features.adoc[leveloffset=+1]
 
 include::modules/telco-ran-architecture-overview.adoc[leveloffset=+1]