OSDOCS-17051-3: CQA POST-3: Multi-Architecture Compute Node Creation

modules/multi-architecture-enabling-64k-pages.adoc

@@ -4,9 +4,9 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="multi-architecture-enabling-64k-pages_{context}"]
-
 = Enabling 64k pages on the {op-system-first} kernel
 
+[role="_abstract"]
 You can enable the 64k memory page in the {op-system-first} kernel on the 64-bit ARM compute machines in your cluster. The 64k page size kernel specification can be used for large GPU or high memory workloads. This is done using the Machine Config Operator (MCO) which uses a machine config pool to update the kernel. To enable 64k page sizes, you must dedicate a machine config pool for ARM64 to enable on the kernel.
 
 [IMPORTANT]
@@ -15,12 +15,14 @@ Using 64k pages is exclusive to 64-bit ARM architecture compute nodes or cluster
 ====
 
 .Prerequisites
-* You installed the OpenShift CLI (`oc`).
+
+* You installed the {oc-first}.
 * You created a cluster with compute nodes of different architecture on one of the supported platforms.
 
 .Procedure
 
 . Label the nodes where you want to run the 64k page size kernel:
++
 [source,terminal]
 +
 ----
@@ -69,18 +71,23 @@ apiVersion: machineconfiguration.openshift.io/v1
 kind: MachineConfig
 metadata:
   labels:
-    machineconfiguration.openshift.io/role: "worker-64k-pages" <1>
+    machineconfiguration.openshift.io/role: "worker-64k-pages"
   name: 99-worker-64kpages
 spec:
-  kernelType: 64k-pages <2>
+  kernelType: 64k-pages
 ----
-<1> Specify the value of the `machineconfiguration.openshift.io/role` label in the custom machine config pool. The example MachineConfig uses the `worker-64k-pages` label to enable 64k pages in the `worker-64k-pages` pool.
-<2> Specify your desired kernel type. Valid values are `64k-pages` and `default`
++
+where:
++
+--
+`metadata.labels.machineconfiguration.openshift.io/role`:: Specifies the value of the `machineconfiguration.openshift.io/role` label in the custom machine config pool. The example MachineConfig uses the `worker-64k-pages` label to enable 64k pages in the `worker-64k-pages` pool.
+`spec.kernalType`:: Specifies your desired kernel type. Valid values are `64k-pages` and `default`
 +
 [NOTE]
 ====
 The `64k-pages` type is supported on only 64-bit ARM architecture based compute nodes. The `realtime` type is supported on only 64-bit x86 architecture based compute nodes.
 ====
+--
 
 .Verification
 

modules/multi-architecture-import-imagestreams.adoc

@@ -4,18 +4,18 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="multi-architecture-import-imagestreams_{context}"]
-
 = Importing manifest lists in image streams on your multi-architecture compute machines
 
+[role="_abstract"]
 On an {product-title} {product-version} cluster with multi-architecture compute machines, the image streams in the cluster do not import manifest lists automatically. You must manually change the default `importMode` option to the `PreserveOriginal` option in order to import the manifest list.
 
 .Prerequisites
 
-* You installed the {product-title} CLI (`oc`).
+* You installed the {oc-first}.
 
 .Procedure
 
-* The following example command shows how to patch the `ImageStream` cli-artifacts so that the `cli-artifacts:latest` image stream tag is imported as a manifest list.
+* Enter a command similar to the following example command to patch the `ImageStream` cli-artifacts so that the `cli-artifacts:latest` image stream tag is imported as a manifest list:
 +
 [source,terminal]
 ----
@@ -30,10 +30,8 @@ $ oc patch is/cli-artifacts -n openshift -p '{"spec":{"tags":[{"name":"latest","
 ----
 $ oc get istag cli-artifacts:latest -n openshift -oyaml
 ----
-
 +
-If the `dockerImageManifests` object is present, then the manifest list import was successful.
-
+If the `dockerImageManifests` object is present, the manifest list imported successfully.
 +
 .Example output of the `dockerImageManifests` object
 [source, yaml]

modules/multi-architecture-scheduling-examples.adoc

@@ -2,10 +2,11 @@
 //
 //post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-compute-managing.adoc
 
-:_mod-docs-content-type: CONCEPT
+:_mod-docs-content-type: REFERENCE
 [id="multi-architecture-scheduling-examples_{context}"]
 = Sample multi-architecture node workload deployments
 
+[role="_abstract"]
 Scheduling a workload to an appropriate node based on architecture works in the same way as scheduling based on any other node characteristic.
 ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 Consider the following options when determining how to schedule your workloads.

modules/multi-architecture-scheduling.adoc

@@ -1,11 +1,16 @@
+// Module included in the following assemblies:
+//
+// * post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-compute-managing.adoc
+
 :_mod-docs-content-type: CONCEPT
 [id="multi-architecture-scheduling_{context}"]
 = Scheduling workloads on clusters with multi-architecture compute machines
 
-When you deploy workloads on a cluster with compute nodes that use different architectures, you must align pod architecture with the architecture of the underlying node. Your workload may also require additional configuration to particular resources depending on the underlying node architecture.
+[role="_abstract"]
+When you deploy workloads on a cluster with compute nodes that use different architectures, you must align pod architecture with the architecture of the underlying node. Your workload might also require additional configuration to particular resources depending on the underlying node architecture.
 
 You can use the Multiarch Tuning Operator to enable architecture-aware scheduling of workloads on clusters with multi-architecture compute machines. The Multiarch Tuning Operator implements additional scheduler predicates in the pods specifications based on the architectures that the pods can support at creation time.
 
 ifndef::openshift-enterprise[]
-For information about the Multiarch Tuning Operator, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/postinstallation_configuration/configuring-multi-architecture-compute-machines-on-an-openshift-cluster#multiarch-tuning-operator[Managing workloads on multi-architecture clusters by using the Multiarch Tuning Operator].
+For information about the Multiarch Tuning Operator, see "Managing workloads on multi-architecture clusters by using the Multiarch Tuning Operator".
 endif::openshift-enterprise[]

post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-compute-managing.adoc

@@ -6,17 +6,25 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 Managing a cluster that has nodes with multiple architectures requires you to consider node architecture as you monitor the cluster and manage your workloads. This requires you to take additional considerations into account when you 
 ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
-configure cluster resource requirements and behavior, or
+configure cluster resource requirements and behaviors, or
 endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 schedule workloads in a multi-architecture cluster.
 
 include::modules/multi-architecture-scheduling.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+
+* link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/postinstallation_configuration/configuring-multi-architecture-compute-machines-on-an-openshift-cluster#multiarch-tuning-operator[Managing workloads on multi-architecture clusters by using the Multiarch Tuning Operator]
+
 include::modules/multi-architecture-scheduling-examples.adoc[leveloffset=+2]
 
+[role="_additional-resources"]
 .Additional resources
+
 * xref:../../post_installation_configuration/configuring-multi-arch-compute-machines/multiarch-tuning-operator.adoc#multiarch-tuning-operator[Managing workloads on multi-architecture clusters by using the Multiarch Tuning Operator]
 * xref:../../nodes/scheduling/nodes-scheduler-taints-tolerations.adoc#nodes-scheduler-taints-tolerations[Controlling pod placement using node taints]
 * xref:../../nodes/scheduling/nodes-scheduler-node-affinity.adoc#nodes-scheduler-node-affinity[Controlling pod placement on nodes using node affinity]

snippets/multi-arch-schedule-nodeaffinity.adoc

@@ -21,10 +21,11 @@ spec:
             - matchExpressions:
               - key: kubernetes.io/arch
                 operator: In
-                values: <1>
+                values:
                 - amd64
                 - arm64
+# ...
 ----
-<1> Specify the supported architectures. Valid values include `amd64`,`arm64`, or both values.
-[source,yaml]
---
++
+** The `values` parameter specifies the supported architectures. Valid values include `amd64`,`arm64`, or both values.
+