Changes to operator mesh setup (RedHatInsights#1211)

ianf77 · web-flow · commit a4cc3adbdb36 · 2024-04-19T09:42:27.000+01:00
* Changes to operator mesh setup Amend Peers from Control nodes Adding a Remote Execution Node to AAP https://issues.redhat.com/browse/AAP-22358 * Changes to operator mesh setup Moved removing instances section Adding a Remote Execution Node to AAP https://issues.redhat.com/browse/AAP-22358 * Changes to operator mesh setip Added reference to RHEL subscriptions Adding a Remote Execution Node to AAP https://issues.redhat.com/browse/AAP-22358 * Changes to operator mesh setup Correction Adding a Remote Execution Node to AAP https://issues.redhat.com/browse/AAP-22358 * Changes to operator mesh set up Correction Adding a Remote Execution Node to AAP https://issues.redhat.com/browse/AAP-22358 * Changes to operator mesh setup Changed reference to Simple Content Access Adding a Remote Execution Node to AAP https://issues.redhat.com/browse/AAP-22358
diff --git a/downstream/assemblies/platform/assembly-automation-mesh-operator-aap.adoc b/downstream/assemblies/platform/assembly-automation-mesh-operator-aap.adoc
@@ -17,12 +17,12 @@ For more information, see link:{BaseURL}/red_hat_ansible_automation_platform/{Pl
 include::platform/ref-operator-mesh-prerequisites.adoc[leveloffset=+1]
 include::platform/proc-set-up-virtual-machines.adoc[leveloffset=+1]
 include::platform/proc-define-mesh-node-types.adoc[leveloffset=+1]
-include::platform/ref-removing-instances.adoc[leveloffset=+2]
 include::platform/proc-controller-create-instance-group.adoc[leveloffset=+1]
 include::platform/proc-controller-associate-instances-to-instance-group.adoc[leveloffset=+1]
 include::platform/proc-run-jobs-on-execution-nodes.adoc[leveloffset=+1]
 //include::platform/proc-connecting-nodes-through-mesh-ingress.adoc[leveloffset=+1]
 include::platform/proc-pulling-the-secret.adoc[leveloffset=+1]
+include::platform/ref-removing-instances.adoc[leveloffset=+1]
 
 
 
diff --git a/downstream/modules/platform/proc-define-mesh-node-types.adoc b/downstream/modules/platform/proc-define-mesh-node-types.adoc
@@ -48,8 +48,13 @@ Options:
 
 ** *Enable Instance*: Check this box to make it available for jobs to run on an execution node.
 ** Check the *Managed by Policy* box to enable policy to dictate how the instance is assigned.
-** Check the *Peers from control nodes* box to enable control nodes to peer to this instance automatically. For hop nodes, check the *Peers from Control* nodes box to create a direct communication link between the hop node and {ControllerName}. 
-For execution nodes that communicate with hop nodes, do not check this box.
+** Check the *Peers from control nodes* box to enable control nodes to peer to this instance automatically. 
+For nodes connected to {ControllerName}, check the *Peers from Control* nodes box to create a direct communication link between that node and {ControllerName}. 
+For all other nodes:
+
+*** If you are not adding a hop node, make sure *Peers from Control* is checked. 
+*** If you are adding a hop node, make sure *Peers from Control* is not checked.
+*** For execution nodes that communicate with hop nodes, do not check this box.
 ** To peer an execution node with a hop node, click the image:search.png[Search,15,15] icon next to the *Peers* field.
 +
 The Select Peers window is displayed.
@@ -159,6 +164,8 @@ After this playbook runs, your automation mesh is configured.
 +
 image::instances_list_view2.png[Instances list view]
 
+To remove an instance from the mesh, see xref:ref-removing-instances[Removing instances].
+
 
 
 
diff --git a/downstream/modules/platform/proc-set-up-virtual-machines.adoc b/downstream/modules/platform/proc-set-up-virtual-machines.adoc
@@ -37,7 +37,7 @@ If Simple Content Access is enabled for your account, use:
 sudo subscription-manager register
 ----
 +
-For more information about Simple Content Access, see link:https://access.redhat.com/articles/simple-content-access[Simple Content Access].
+For more information about Simple Content Access, see link:{BaseURL}/subscription_central/1-latest/html/getting_started_with_simple_content_access/index[Getting started with simple content access].
 
 . Enable {PlatformNameShort} subscriptions and the proper {PlatformName} channel:
 +
diff --git a/downstream/modules/platform/ref-operator-mesh-prerequisites.adoc b/downstream/modules/platform/ref-operator-mesh-prerequisites.adoc
@@ -4,6 +4,9 @@
 
 The automation mesh is dependent on hop and execution nodes running on {RHEL} (RHEL). 
 Your {PlatformName} subscription grants you ten {RHEL} licenses that can be used for running components of {PlatformNameShort}. 
+
+For additional information about {RHEL} subscriptions, see link:{BaseURL}/red_hat_enterprise_linux/9/html/configuring_basic_system_settings/assembly_registering-the-system-and-managing-subscriptions_configuring-basic-system-settings[Registering the system and managing subscriptions] in the {RHEL} documentation.
+
 The following steps prepare the RHEL instances for deployment of the automation mesh.
 
 . You require a {RHEL} operating system. 

Original file line number	Diff line number	Diff line change
`@@ -37,7 +37,7 @@ If Simple Content Access is enabled for your account, use:`
`37`	`37`	`sudo subscription-manager register`
`38`	`38`	`----`
`39`	`39`	`+`
`40`		`-For more information about Simple Content Access, see link:https://access.redhat.com/articles/simple-content-access[Simple Content Access].`
	`40`	`+For more information about Simple Content Access, see link:{BaseURL}/subscription_central/1-latest/html/getting_started_with_simple_content_access/index[Getting started with simple content access].`
`41`	`41`
`42`	`42`	`. Enable {PlatformNameShort} subscriptions and the proper {PlatformName} channel:`
`43`	`43`	`+`