openshift · slovern · Jul 10, 2025
diff --git a/modules/telco-ran-deviations-from-the-ref-design.adoc b/modules/telco-ran-deviations-from-the-ref-design.adoc
@@ -0,0 +1,19 @@
+// Module included in the following assemblies:
+//
+// * scalability_and_performance/telco-ran-du-rds.adoc
+
+:_mod-docs-content-type: CONCEPT
+[id="telco-ran-deviations-from-the-ref-design_{context}"]
+= Deviations from the reference design
+
+Deviation from the validated configuration contained in this document and the linked CRs may have significant impact beyond the specific component or feature and will require additional analysis or engineering in the context of the full solution.
+Deviation from the RDS can have some or all of the following consequences:
+
+* Long times to resolve issues with customers - poor customer service and customer satisfaction
+* Escalations with key partners at executive levels
+* Risk of missing project SLAs
+* Risk of missing project timelines
+* Risk of missing end provider performance requirements
+* Requests for approval of deviations are made through RFE or Support Exception
+* All unapproved deviations will be escalated to VP of Ecosystem Engineering
+* Servicing of requests on deviations will be prioritized based on the TLT engagement priorities
diff --git a/modules/telco-ran-engineering-considerations-for-the-ran-du-use-model.adoc b/modules/telco-ran-engineering-considerations-for-the-ran-du-use-model.adoc
@@ -39,36 +39,9 @@ Workloads::
 . DU workloads are described in xref:../scalability_and_performance/telco-ran-du-rds.adoc#telco-ran-du-application-workloads_telco-ran-du[Telco RAN DU application workloads].
 . DU worker nodes are Intel 3rd Generation Xeon (IceLake) 2.20 GHz or newer with host firmware tuned for maximum performance.
 
-
 Resources::
 The maximum number of running pods in the system, inclusive of application workload and {product-title} pods, is 120.
 
-Resource utilization::
-+
---
-{product-title} resource utilization varies depending on many factors such as the following application workload characteristics:
-
-* Pod count
-* Type and frequency of probes
-* Messaging rates on the primary or secondary CNI with kernel networking
-* API access rate
-* Logging rates
-* Storage IOPS
-
-Resource utilization is measured for clusters configured as follows:
-
-. The cluster is a single host with {sno} installed.
-. The cluster runs the representative application workload described in "Reference application workload characteristics".
-. The cluster is managed under the constraints detailed in "Hub cluster management characteristics".
-. Components noted as "optional" in the use model configuration are not included.
-
-[NOTE]
-====
-Configuration outside the scope of the RAN DU RDS that do not meet these criteria requires additional analysis to determine the impact on resource utilization and ability to meet KPI targets.
-You might need to allocate additional cluster resources to meet these requirements.
-====
---
-
 Reference application workload characteristics::
 . Uses 15 pods and 30 containers for the vRAN application including its management and control functions
 . Uses an average of 2 `ConfigMap` and 4 `Secret` CRs per pod
@@ -117,3 +90,29 @@ The system is engineered to 3 CPUs (3000mc) at steady-state to allow for periodi
 
 |====
 --
+
+Resource utilization::
++
+--
+{product-title} resource utilization varies depending on many factors such as the following application workload characteristics:
+
+* Pod count
+* Type and frequency of probes
+* Messaging rates on the primary or secondary CNI with kernel networking
+* API access rate
+* Logging rates
+* Storage IOPS
+
+Resource utilization is measured for clusters configured as follows:
+
+. The cluster is a single host with {sno} installed.
+. The cluster runs the representative application workload described in "Reference application workload characteristics".
+. The cluster is managed under the constraints detailed in "Hub cluster management characteristics".
+. Components noted as "optional" in the use model configuration are not included.
+
+[NOTE]
+====
+Configuration outside the scope of the RAN DU RDS that do not meet these criteria requires additional analysis to determine the impact on resource utilization and ability to meet KPI targets.
+You might need to allocate additional cluster resources to meet these requirements.
+====
+--
diff --git a/modules/telco-ran-rds-scope.adoc b/modules/telco-ran-rds-scope.adoc
@@ -0,0 +1,15 @@
+// Module included in the following assemblies:
+//
+// * scalability_and_performance/telco-ran-du-rds.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="telco-ran-rds-scope_{context}"]
+= Reference design scope
+
+This document captures the set of released features and supported configurations that have been engineered and telco QE validated for the described use models.
+The configurations provide a baseline {product-name} platform which meets the feature and KPI targets for the use-models.
+Expected variations are noted in the configurations and further detailed in this specification.
+The validation of this reference configuration includes many long duration and at-scale tests.
+
+These configurations are updated on each major ("y-stream") release of {product-name}.
+Patch ("z-stream") releases are periodically re-tested against this lineup, including many long duration validations.
diff --git a/scalability_and_performance/telco-ran-du-rds.adoc b/scalability_and_performance/telco-ran-du-rds.adoc
@@ -16,9 +16,9 @@ Specific limits, requirements, and engineering considerations for individual com
 
 include::modules/telco-ref-design-overview.adoc[leveloffset=+1]
 
-include::modules/telco-ran-core-ref-design-spec.adoc[leveloffset=+1]
+include::modules/telco-ran-rds-scope.adoc[leveloffset=+1]
 
-include::modules/telco-deviations-from-the-ref-design.adoc[leveloffset=+1]
+include::modules/telco-ran-deviations-from-the-ref-design.adoc[leveloffset=+1]
 
 include::modules/telco-ran-engineering-considerations-for-the-ran-du-use-model.adoc[leveloffset=+1]