Skip to content

Commit b529916

Browse files
cherrazcherraz
committed
BZ2040707: Style fixes on ZTP assembly
1 parent e1218d6 commit b529916

File tree

46 files changed

+202
-156
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

46 files changed

+202
-156
lines changed

‎modules/ztp-about-ztp-and-distributed-units-on-single-node-openshift-clusters.adoc‎

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
// Module included in the following assemblies:
22
//
3-
// *scalability_and_performance/ztp-zero-touch-provisioning.adoc
3+
// *scalability_and_performance/ztp-deploying-disconnected.adoc
44

5+
:_content-type: CONCEPT
56
[id="about-ztp-and-distributed-units-on-single-node-clusters_{context}"]
67
= About ZTP and distributed units on single nodes
78

@@ -15,10 +16,10 @@ With ZTP and AI, you can provision {product-title} single nodes to run your DUs
1516

1617
* A hub cluster running ACM manages a disconnected internal registry that mirrors the {product-title} release images. The internal registry is used to provision the spoke single nodes.
1718
18-
* You manage the bare metal host machines for your DUs in an inventory file that uses YAML for formatting. You store the inventory file in a Git repository.
19+
* You manage the bare-metal host machines for your DUs in an inventory file that uses YAML for formatting. You store the inventory file in a Git repository.
1920
2021
21-
* You install the DU bare metal host machines on site, and make the hosts ready for provisioning. To be ready for provisioning, the following is required for each bare metal host:
22+
* You install the DU bare-metal host machines on site, and make the hosts ready for provisioning. To be ready for provisioning, the following is required for each bare-metal host:
2223
2324
** Network connectivity - including DNS for your network. Hosts should be reachable through the hub and managed spoke clusters. Ensure there is layer 3 connectivity between the hub and the host where you want to install your hub cluster.
2425

@@ -56,7 +57,7 @@ CRs are as follows:
5657
This is the final step of the manifest creation phase.
5758

5859
|BareMetalHost
59-
|Describes the details of the bare metal host, including BMC and credentials details.
60+
|Describes the details of the bare-metal host, including BMC and credentials details.
6061
|===
6162

6263
* When a change is detected in the host inventory repository, a host management event is triggered to provision the new or updated host.

‎modules/ztp-acm-adding-images-to-mirror-registry.adoc‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
// Module included in the following assemblies:
33
//
44
// scalability_and_performance/ztp-deploying-disconnected.adoc
5+
:_content-type: PROCEDURE
56
[id="ztp-acm-adding-images-to-mirror-registry_{context}"]
67
= Adding {op-system} ISO and RootFS images to a disconnected mirror host
78

‎modules/ztp-acm-installing-disconnected-rhacm.adoc‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@
33
// scalability_and_performance/ztp-deploying-disconnected.adoc
44

55
[id="installing-disconnected-rhacm_{context}"]
6+
:_content-type: PROCEDURE
67
= Installing Red Hat Advanced Cluster Management in a disconnected environment
78

89
You use {rh-rhacm-first} on a hub cluster in the disconnected environment to manage the deployment of distributed unit (DU) profiles on multiple managed spoke clusters.

‎modules/ztp-acm-preparing-to-install-disconnected-acm.adoc‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
// Module included in the following assemblies:
33
//
44
// scalability_and_performance/ztp-deploying-disconnected.adoc
5+
:_content-type: CONCEPT
56
[id="ztp-acm-preparing-to-install-disconnected-acm_{context}"]
67
= Preparing the disconnected environment
78

‎modules/ztp-ai-install-ocp-clusters-on-bare-metal.adoc‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
//
33
// scalability_and_performance/ztp-deploying-disconnected.adoc
44

5+
:_content-type: PROCEDURE
56
[id="enabling-assisted-installer-service-on-bare-metal_{context}"]
67
= Enabling assisted installer service on bare metal
78

‎modules/ztp-applying-source-custom-resource-policies.adoc‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
//
33
// scalability_and_performance/ztp-deploying-disconnected.adoc
44

5+
:_content-type: PROCEDURE
56
[id="ztp-applying-source-custom-resource-policies_{context}"]
67
= Applying source custom resource policies
78

‎modules/ztp-applying-the-ran-policies-for-monitoring-cluster-activity.adoc‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
//
33
// scalability_and_performance/ztp-deploying-disconnected.adoc
44

5+
:_content-type: CONCEPT
56
[id="ztp-applying-the-ran-policies-for-monitoring-cluster-activity_{context}"]
67
= Applying the RAN policies for monitoring cluster activity
78

‎modules/ztp-checking-the-installation-status.adoc‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
// Module included in the following assemblies:
22
//
3-
// *scalability_and_performance/ztp-zero-touch-provisioning.adoc
3+
// *scalability_and_performance/ztp-deploying-disconnected.adoc
44

5+
:_content-type: PROCEDURE
56
[id="ztp-checking-the-installation-status_{context}"]
67
= Checking the installation status
78

@@ -13,7 +14,7 @@ The ArgoCD pipeline detects the `SiteConfig` and `PolicyGenTemplate` custom reso
1314
+
1415
[source,terminal]
1516
----
16-
$ export CLUSTER=<clusterName>
17+
$ export CLUSTER=<cluster_name>
1718
----
1819
+
1920
[source,terminal]

‎modules/ztp-checking-the-managed-cluster-status.adoc‎

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
// Module included in the following assemblies:
22
//
3-
// *scalability_and_performance/ztp-zero-touch-provisioning.adoc
3+
// *scalability_and_performance/ztp-deploying-disconnected.adoc
44

5+
:_content-type: PROCEDURE
56
[id="ztp-checking-the-managed-cluster-status_{context}"]
67
= Checking the managed cluster status
78

@@ -27,40 +28,40 @@ $ oc get managedcluster
2728
+
2829
[source,terminal]
2930
----
30-
$ oc get agent -n <cluster-name>
31+
$ oc get agent -n <cluster_name>
3132
----
3233

3334
. Use the `describe` command to provide an in-depth description of the agent’s condition. Statuses to be aware of include `BackendError`, `InputError`, `ValidationsFailing`, `InstallationFailed`, and `AgentIsConnected`. These statuses are relevant to the `Agent` and `AgentClusterInstall` custom resources.
3435
+
3536
[source,terminal]
3637
----
37-
$ oc describe agent -n <cluster-name>
38+
$ oc describe agent -n <cluster_name>
3839
----
3940

4041
. Check the cluster provisioning status:
4142
+
4243
[source,terminal]
4344
----
44-
$ oc get agentclusterinstall -n <cluster-name>
45+
$ oc get agentclusterinstall -n <cluster_name>
4546
----
4647

4748
. Use the `describe` command to provide an in-depth description of the cluster provisioning status:
4849
+
4950
[source,terminal]
5051
----
51-
$ oc describe agentclusterinstall -n <cluster-name>
52+
$ oc describe agentclusterinstall -n <cluster_name>
5253
----
5354

5455
. Check the status of the managed cluster’s add-on services:
5556
+
5657
[source,terminal]
5758
----
58-
$ oc get managedclusteraddon -n <cluster-name>
59+
$ oc get managedclusteraddon -n <cluster_name>
5960
----
6061

6162
. Retrieve the authentication information of the `kubeconfig` file for the managed cluster:
6263
+
6364
[source,terminal]
6465
----
65-
$ oc get secret -n <cluster-name> <cluster-name>-admin-kubeconfig -o jsonpath={.data.kubeconfig} | base64 -d > <directory>/<cluster-name>-kubeconfig
66+
$ oc get secret -n <cluster_name> <cluster_name>-admin-kubeconfig -o jsonpath={.data.kubeconfig} | base64 -d > <directory>/<cluster_name>-kubeconfig
6667
----

‎modules/ztp-cluster-provisioning.adoc‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
//
33
// scalability_and_performance/ztp-deploying-disconnected.adoc
44

5+
:_content-type: CONCEPT
56
[id="ztp-cluster-provisioning_{context}"]
67
= Cluster provisioning
78

0 commit comments

Comments
 (0)