CASMCMS-9045 - IMS clarify configuring remote build nodes. (#5334)

* CASMCMS-9045 - IMS clarify configuring remote build nodes.

* Fixes for PR feedback.

* Update operations/image_management/Configure_a_Remote_Build_Node.md

Signed-off-by: Nathan Rockershousen <nathan.rockershousen@hpe.com>

---------

Signed-off-by: Nathan Rockershousen <nathan.rockershousen@hpe.com>
Co-authored-by: Nathan Rockershousen <nathan.rockershousen@hpe.com>

operations/image_management/Configure_a_Remote_Build_Node.md

@@ -61,6 +61,29 @@ There are only two requirements for using a compute node as a remote build node:
 * Have Podman installed and configured
 * Allow IMS access via SSH key
 
+Each system is unique so the node chosen to run remote jobs needs to be manually configured based on the
+requirements and capabilities of the system and that particular node. It is not possible to list all the
+configuration steps to optimize a particular node. The following directions are only intended to make a
+minimally functional remote node. Much better performance may be possible with custom configuration by a
+system administrator who is familiar with the configuration and capabilities of the system.
+
+Some things to consider are:
+
+1. Volume mounts.
+
+    There needs to be adequate space on the node to handle the images that are being created or customized
+    on the remote node. The faster the volume access, the faster the image customization. Ways to improve
+    performance beyond the mounts described below can include:
+
+    * If there are local disk drives on the node, use them.
+    * If there is a lot of RAM available, create volumes from memory.
+    * If lustre is available, use lustre mounts.
+
+1. Network access.
+
+    The package repositories that are needed for image creation and customization are located in Nexus
+    within the Kubernetes system. The remote node must be able to access Nexus in order to function.
+
 ### Use an existing compute node
 
 This will add processes to the node being used as a remote build node. The system administrator

operations/image_management/Troubleshoot_Remote_Build_Node.md

@@ -61,7 +61,7 @@ are times that problems crop up with running these remote jobs.
 1. (`ncn-mw#`) Check the IMS service logs for creation of the job.
 
     ```bash
-    cray -n services logs cray-ims-<id of current pod> | grep -A 15 POST
+    kubectl -n services logs cray-ims-<id of current pod> | grep -A 15 POST
     ```
 
     When the job is created there is information in the log about matching remote build nodes - look