From 9bb6819eb997fd792f139de8ce99a08d886f5a33 Mon Sep 17 00:00:00 2001 From: srir Date: Tue, 4 Nov 2025 14:35:05 +0530 Subject: [PATCH] TELCODOCS#2536: Doc updates for multiple bugs --- .../ztp-sno-additional-worker-node.adoc | 2 +- .../telco-core-openshift-data-foundation.adoc | 17 +++++++--- .../ztp-worker-node-preparing-policies.adoc | 2 +- .../telco-core-rds.adoc | 2 +- ...pg-ztp-worker-node-preparing-policies.adoc | 34 +++---------------- 5 files changed, 19 insertions(+), 38 deletions(-) diff --git a/edge_computing/ztp-sno-additional-worker-node.adoc b/edge_computing/ztp-sno-additional-worker-node.adoc index e795be90ea..c46503923d 100644 --- a/edge_computing/ztp-sno-additional-worker-node.adoc +++ b/edge_computing/ztp-sno-additional-worker-node.adoc @@ -1,5 +1,5 @@ [id="ztp-sno-additional-worker-node"] -= Expanding {sno} clusters with {ztp} += Expanding single-node OpenShift clusters with GitOps ZTP include::_attributes/common-attributes.adoc[] :context: sno-additional-worker diff --git a/modules/telco-core-openshift-data-foundation.adoc b/modules/telco-core-openshift-data-foundation.adoc index e71e66bec0..4f17b146ae 100644 --- a/modules/telco-core-openshift-data-foundation.adoc +++ b/modules/telco-core-openshift-data-foundation.adoc @@ -11,19 +11,26 @@ New in this release:: * No reference design updates in this release. Description:: -{rh-storage} is a software-defined storage service for containers. -{rh-storage} can be deployed in one of two modes: +{rh-storage} is a software-defined storage service for containers. {rh-storage} can be deployed in one of two modes: ++ +-- * Internal mode, where {rh-storage} software components are deployed as software containers directly on the {product-title} cluster nodes, together with other containerized applications. * External mode, where {rh-storage} is deployed on a dedicated storage cluster, which is usually a separate Red Hat Ceph Storage cluster running on {op-system-base-full}. +-- ++ These storage services are running externally to the application workload cluster. - ++ For telco core clusters, storage support is provided by {rh-storage} storage services running in external mode, for several reasons: - ++ +-- * Separating dependencies between {product-title} and Ceph operations allows for independent {product-title} and {rh-storage} updates. * Separation of operations functions for the Storage and {product-title} infrastructure layers, is a typical customer requirement for telco core use cases. * External Red Hat Ceph Storage clusters can be re-used by multiple {product-title} clusters deployed in the same region. - +-- ++ +-- {rh-storage} supports separation of storage traffic using secondary CNI networks. +-- Limits and requirements:: * In an IPv4/IPv6 dual-stack networking environment, {rh-storage} uses IPv4 addressing. diff --git a/modules/ztp-worker-node-preparing-policies.adoc b/modules/ztp-worker-node-preparing-policies.adoc index 370023462b..bdddd04f10 100644 --- a/modules/ztp-worker-node-preparing-policies.adoc +++ b/modules/ztp-worker-node-preparing-policies.adoc @@ -20,7 +20,7 @@ ifeval::["{policy-gen-cr}" == "PolicyGenerator"] include::snippets/pg-ztp-worker-node-preparing-policies.adoc[] endif::[] -A generic `MachineConfig` CR is used to configure workload partitioning on the worker node. You can generate the content of `crio` and `kubelet` configuration files. +You can generate the content of `crio` and `kubelet` configuration files. -- . Add the created policy template to the Git repository monitored by the ArgoCD `policies` application. diff --git a/scalability_and_performance/telco-core-rds.adoc b/scalability_and_performance/telco-core-rds.adoc index 14012b9906..817335d811 100644 --- a/scalability_and_performance/telco-core-rds.adoc +++ b/scalability_and_performance/telco-core-rds.adoc @@ -162,7 +162,7 @@ include::modules/telco-core-gitops-operator-and-ztp-plugins.adoc[leveloffset=+3] * xref:../edge_computing/policygentemplate_for_ztp/ztp-advanced-policy-config.adoc#ztp-adding-new-content-to-gitops-ztp_ztp-advanced-policy-config[Adding custom content to the {ztp} pipeline] -include::modules/telco-core-monitoring.adoc[leveloffset=+3] +include::modules/telco-core-monitoring.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources diff --git a/snippets/pg-ztp-worker-node-preparing-policies.adoc b/snippets/pg-ztp-worker-node-preparing-policies.adoc index 299da20a7c..9e0cda7198 100644 --- a/snippets/pg-ztp-worker-node-preparing-policies.adoc +++ b/snippets/pg-ztp-worker-node-preparing-policies.adoc @@ -31,36 +31,12 @@ policies: policyAnnotations: ran.openshift.io/ztp-deploy-wave: "10" manifests: - - path: source-crs/MachineConfigGeneric.yaml <2> - patches: - - metadata: - labels: - machineconfiguration.openshift.io/role: worker <3> - name: enable-workload-partitioning - spec: - config: - storage: - files: - - contents: - source: data:text/plain;charset=utf-8;base64,W2NyaW8ucnVudGltZS53b3JrbG9hZHMubWFuYWdlbWVudF0KYWN0aXZhdGlvbl9hbm5vdGF0aW9uID0gInRhcmdldC53b3JrbG9hZC5vcGVuc2hpZnQuaW8vbWFuYWdlbWVudCIKYW5ub3RhdGlvbl9wcmVmaXggPSAicmVzb3VyY2VzLndvcmtsb2FkLm9wZW5zaGlmdC5pbyIKcmVzb3VyY2VzID0geyAiY3B1c2hhcmVzIiA9IDAsICJjcHVzZXQiID0gIjAtMyIgfQo= - mode: 420 - overwrite: true - path: /etc/crio/crio.conf.d/01-workload-partitioning - user: - name: root - - contents: - source: data:text/plain;charset=utf-8;base64,ewogICJtYW5hZ2VtZW50IjogewogICAgImNwdXNldCI6ICIwLTMiCiAgfQp9Cg== - mode: 420 - overwrite: true - path: /etc/kubernetes/openshift-workload-pinning - user: - name: root - path: source-crs/PerformanceProfile-MCP-worker.yaml patches: - metadata: name: openshift-worker-node-performance-profile spec: - cpu: <4> + cpu: <2> isolated: 4-47 reserved: 0-3 hugepages: @@ -81,7 +57,7 @@ policies: summary=Configuration changes profile inherited from performance created tuned include=openshift-node-performance-openshift-worker-node-performance-profile [bootloader] - cmdline_crash=nohz_full=4-47 <5> + cmdline_crash=nohz_full=4-47 <3> [sysctl] kernel.timer_migration=1 [scheduler] @@ -94,7 +70,5 @@ policies: - profile: performance-patch-worker ---- <1> The policies are applied to all clusters with this label. -<2> This generic `MachineConfig` CR is used to configure workload partitioning on the worker node. -<3> The `MCP` field must be set to `worker`. -<4> The `cpu.isolated` and `cpu.reserved` fields must be configured for each particular hardware platform. -<5> The `cmdline_crash` CPU set must match the `cpu.isolated` set in the `PerformanceProfile` section. +<2> The `cpu.isolated` and `cpu.reserved` fields must be configured for each specific hardware platform. +<3> The `cmdline_crash` CPU set must match the `cpu.isolated` set in the `PerformanceProfile` section. \ No newline at end of file