TELCODOCS-2171#Generalize Day2Ops for Telco

Conflicts solved

Author: amolnar-gh

_topic_maps/_topic_map.yml

@@ -3562,23 +3562,23 @@ Topics:
       File: telco-update-completing-the-y-stream-update
     - Name: Completing the z-stream update
       File: telco-update-completing-the-z-stream-update
-  - Name: Troubleshooting and maintaining telco core CNF clusters
+  - Name: Troubleshooting and maintaining OpenShift Container Platform clusters
     Dir: troubleshooting
     Topics:
-    - Name: Troubleshooting and maintaining telco core CNF clusters
-      File: telco-troubleshooting-intro
+    - Name: Troubleshooting and maintaining OpenShift Container Platform clusters
+      File: troubleshooting-intro
     - Name: General troubleshooting
-      File: telco-troubleshooting-general-troubleshooting
+      File: troubleshooting-general-troubleshooting
     - Name: Cluster maintenance
-      File: telco-troubleshooting-cluster-maintenance
+      File: troubleshooting-cluster-maintenance
     - Name: Security
-      File: telco-troubleshooting-security
+      File: troubleshooting-security
     - Name: Certificate maintenance
-      File: telco-troubleshooting-cert-maintenance
+      File: troubleshooting-cert-maintenance
     - Name: Machine Config Operator
-      File: telco-troubleshooting-mco
+      File: troubleshooting-mco
     - Name: Bare-metal node maintenance
-      File: telco-troubleshooting-bmn-maintenance
+      File: troubleshooting-bmn-maintenance
   - Name: Observability
     Dir: observability
     Topics:

edge_computing/day_2_core_cnf_clusters/telco-day-2-welcome.adoc

@@ -11,7 +11,7 @@ You can use the following Day 2 operations to manage telco core CNF clusters.
 Updating a telco core CNF cluster:: Updating your cluster is a critical task that ensures that bugs and potential security vulnerabilities are patched.
 For more information, see xref:../day_2_core_cnf_clusters/updating/telco-update-welcome.adoc#telco-update-welcome[Updating a telco core CNF cluster].
 
-Troubleshooting and maintaining telco core CNF clusters:: To maintain and troubleshoot a bare-metal environment where high-bandwidth network throughput is required, see xref:../day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-intro.adoc#telco-troubleshooting-intro[Troubleshooting and maintaining telco core CNF clusters].
+Troubleshooting and maintaining telco core CNF clusters:: To maintain and troubleshoot a bare-metal environment where high-bandwidth network throughput is required, see xref:../day_2_core_cnf_clusters/troubleshooting/troubleshooting-intro.adoc#troubleshooting-intro[Troubleshooting and maintaining {product-title} clusters].
 
 Observability in telco core CNF clusters:: {product-title} generates a large amount of data, such as performance metrics and logs from the platform and the workloads running on it.
 As an administrator, you can use tools to collect and analyze the available data.

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-cluster-maintenance.adoc

@@ -1,29 +1,29 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-bmn-maintenance"]
+[id="troubleshooting-bmn-maintenance"]
 = Bare-metal node maintenance
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-bmn-maintenance
+:context: troubleshooting-bmn-maintenance
 
 toc::[]
 
 You can connect to a node for general troubleshooting.
 However, in some cases, you need to perform troubleshooting or maintenance tasks on certain hardware components.
-This section discusses topics that you need to perform that hardware maintenance.
+This section discusses topics that you need to perform for hardware maintenance.
 
-include::modules/telco-troubleshooting-bmn-connect-to-node.adoc[leveloffset=+1]
-include::modules/telco-troubleshooting-bmn-move-apps-to-pods.adoc[leveloffset=+1]
+include::modules/troubleshooting-bmn-connect-to-node.adoc[leveloffset=+1]
+include::modules/troubleshooting-bmn-move-apps-to-pods.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../nodes/nodes/nodes-nodes-working.adoc#nodes-nodes-working_nodes-nodes-working[Working with nodes]
 
-include::modules/telco-troubleshooting-bmn-replace-dimm.adoc[leveloffset=+1]
+include::modules/troubleshooting-bmn-replace-dimm.adoc[leveloffset=+1]
+include::modules/troubleshooting-bmn-replace-disk.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../storage/index.adoc#storage-overview_storage-overview[{product-title} storage overview]
 
-include::modules/telco-troubleshooting-bmn-replace-disk.adoc[leveloffset=+1]
-include::modules/telco-troubleshooting-bmn-replace-nw-card.adoc[leveloffset=+1]
+include::modules/troubleshooting-bmn-replace-nw-card.adoc[leveloffset=+1]

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-mco.adoc

@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-cert-maintenance"]
+[id="troubleshooting-cert-maintenance"]
 = Certificate maintenance
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-cert-maintenance
+:context: troubleshooting-cert-maintenance
 
 toc::[]
 
@@ -14,22 +14,22 @@ Learn about certificates in {product-title} and how to maintain them by using th
 * link:https://access.redhat.com/solutions/5018231[Which OpenShift certificates do rotate automatically and which do not in Openshift 4.x?]
 * link:https://access.redhat.com/solutions/7000968[Checking etcd certificate expiry in OpenShift 4]
 
-include::modules/telco-troubleshooting-certs-manual.adoc[leveloffset=+1]
-include::modules/telco-troubleshooting-certs-manual-proxy.adoc[leveloffset=+2]
+include::modules/troubleshooting-certs-manual.adoc[leveloffset=+1]
+include::modules/troubleshooting-certs-manual-proxy.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../security/certificate_types_descriptions/proxy-certificates.adoc#cert-types-proxy-certificates[Proxy certificates]
 
-include::modules/telco-troubleshooting-certs-manual-user-provisioned.adoc[leveloffset=+2]
+include::modules/troubleshooting-certs-manual-user-provisioned.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../security/certificate_types_descriptions/user-provided-certificates-for-api-server.adoc#cert-types-user-provided-certificates-for-the-api-server[User-provisioned certificates for the API server]
 
-include::modules/telco-troubleshooting-certs-auto.adoc[leveloffset=+1]
+include::modules/troubleshooting-certs-auto.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
@@ -44,21 +44,21 @@ include::modules/telco-troubleshooting-certs-auto.adoc[leveloffset=+1]
 * xref:../../../security/certificate_types_descriptions/control-plane-certificates.adoc#cert-types-control-plane-certificates_cert-types-control-plane-certificates[Control plane certificates]
 * xref:../../../security/certificate_types_descriptions/ingress-certificates.adoc#cert-types-ingress-certificates_cert-types-ingress-certificates[Ingress certificates]
 
-include::modules/telco-troubleshooting-certs-auto-etcd.adoc[leveloffset=+2]
+include::modules/troubleshooting-certs-auto-etcd.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../security/certificate_types_descriptions/etcd-certificates.adoc#cert-types-etcd-certificates_cert-types-etcd-certificates[etcd certificates]
 
-include::modules/telco-troubleshooting-certs-auto-node.adoc[leveloffset=+2]
+include::modules/troubleshooting-certs-auto-node.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../security/certificate_types_descriptions/node-certificates.adoc#cert-types-node-certificates_cert-types-node-certificates[Node certificates]
 
-include::modules/telco-troubleshooting-certs-auto-service-ca.adoc[leveloffset=+2]
+include::modules/troubleshooting-certs-auto-service-ca.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-bmn-maintenance.adoc renamed to edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-bmn-maintenance.adoc

@@ -0,0 +1,21 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="troubleshooting-cluster-maintenance"]
+= Cluster maintenance
+include::_attributes/common-attributes.adoc[]
+:context: troubleshooting-cluster-maintenance
+
+toc::[]
+
+When deploying {product-title} on bare-metal infrastructure, you must pay more attention to certain configurations which can have a significant impact on cluster stability.
+You can troubleshoot more effectively by completing these tasks:
+
+* Monitor for failed or failing hardware components
+* Periodically check the status of the cluster Operators
+
+[NOTE]
+====
+For hardware monitoring, contact your hardware vendor to find the appropriate logging tool for your specific hardware.
+====
+
+include::modules/troubleshooting-clusters-check-cluster-operators.adoc[leveloffset=+1]
+include::modules/troubleshooting-clusters-check-for-failed-pods.adoc[leveloffset=+1]

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-cert-maintenance.adoc renamed to edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-cert-maintenance.adoc

@@ -1,28 +1,28 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-general-troubleshooting"]
+[id="troubleshooting-general-troubleshooting"]
 = General troubleshooting
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-general-troubleshooting
+:context: troubleshooting-general-troubleshooting
 
 toc::[]
 
 When you encounter a problem, the first step is to find the specific area where the issue is happening.
-To narrow down the potential problematic areas, complete one or more tasks:
+To narrow down the potential problematic areas, complete one or more of the following tasks:
 
 * Query your cluster
 * Check your pod logs
 * Debug a pod
 * Review events
 
-include::modules/telco-troubleshooting-general-query-cluster.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-query-cluster.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../cli_reference/openshift_cli/developer-cli-commands.adoc#oc-get[oc get]
 * xref:../../../support/troubleshooting/investigating-pod-issues.adoc#reviewing-pod-status_investigating-pod-issues[Reviewing pod status]
 
-include::modules/telco-troubleshooting-general-check-logs.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-check-logs.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
@@ -32,37 +32,37 @@ include::modules/telco-troubleshooting-general-check-logs.adoc[leveloffset=+1]
 * xref:../../../support/troubleshooting/investigating-pod-issues.adoc#inspecting-pod-and-container-logs_investigating-pod-issues[Inspecting pod and container logs]
 
 
-include::modules/telco-troubleshooting-general-describe-pod.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-describe-pod.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../cli_reference/openshift_cli/developer-cli-commands.adoc#oc-describe[oc describe]
 
-include::modules/telco-troubleshooting-general-review-events.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-review-events.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../security/container_security/security-monitoring.adoc#security-monitoring-events_security-monitoring[Watching cluster events]
 
-include::modules/telco-troubleshooting-general-connect-to-pod.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-connect-to-pod.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../cli_reference/openshift_cli/developer-cli-commands.adoc#oc-rsh[oc rsh]
 * xref:../../../support/troubleshooting/investigating-pod-issues.adoc#accessing-running-pods_investigating-pod-issues[Accessing running pods]
 
-include::modules/telco-troubleshooting-general-debug-pod.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-debug-pod.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../cli_reference/openshift_cli/developer-cli-commands.adoc#oc-debug[oc debug]
 * xref:../../../support/troubleshooting/investigating-pod-issues.adoc#starting-debug-pods-with-root-access_investigating-pod-issues[Starting debug pods with root access]
 
-include::modules/telco-troubleshooting-general-run-command-on-pod.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-run-command-on-pod.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources

edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-cluster-maintenance.adoc

@@ -1,24 +1,23 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-intro"]
-= Troubleshooting and maintaining telco core CNF clusters
+[id="troubleshooting-intro"]
+= Troubleshooting and maintaining {product-title} clusters
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-intro
+:context: troubleshooting-intro
 
 toc::[]
 
 Troubleshooting and maintenance are weekly tasks that can be a challenge if you do not have the tools to reach your goal, whether you want to update a component or investigate an issue.
 Part of the challenge is knowing where and how to search for tools and answers.
 
-To maintain and troubleshoot a bare-metal environment where high-bandwidth network throughput is required, see the following procedures.
+To maintain and troubleshoot a bare-metal environment with high performance requirements, see the following procedures.
 
 [IMPORTANT]
 ====
-This troubleshooting information is not a reference for configuring {product-title} or developing Cloud-native Network Function (CNF) applications.
+This troubleshooting information is not a reference for configuring {product-title} or developing cloud-native applications.
 
-For information about developing CNF applications for telco, see link:https://redhat-best-practices-for-k8s.github.io/guide/[Red Hat Best Practices for Kubernetes].
+For information about developing cloud-native applications on {product-title}, see link:https://redhat-best-practices-for-k8s.github.io/guide/[Red Hat Best Practices for Kubernetes].
 ====
 
-include::modules/telco-troubleshooting-cnfs.adoc[leveloffset=+1]
 include::modules/support-getting-support.adoc[leveloffset=+1]
 include::modules/support-knowledgebase-about.adoc[leveloffset=+2]
 include::modules/support-knowledgebase-search.adoc[leveloffset=+2]

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-general-troubleshooting.adoc renamed to edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-general-troubleshooting.adoc

@@ -0,0 +1,18 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="troubleshooting-mco"]
+= Machine Config Operator
+include::_attributes/common-attributes.adoc[]
+:context: troubleshooting-mco
+
+toc::[]
+
+The Machine Config Operator provides useful information to cluster administrators and controls what is running directly on the bare-metal host.
+
+The Machine Config Operator differentiates between groups of nodes in the cluster, allowing control plane nodes and worker nodes to run with different configurations.
+These groups of nodes run worker or application pods, which are called `MachineConfigPool` (`mcp`) groups.
+The same machine config is applied to all nodes or only to one MCP in the cluster.
+
+For more information about the Machine Config Operator, see xref:../../../operators/operator-reference.adoc#machine-config-operator_cluster-operators-ref[Machine Config Operator].
+
+include::modules/troubleshooting-mco-purpose.adoc[leveloffset=+1]
+include::modules/troubleshooting-mco-apply-several-mcs.adoc[leveloffset=+1]