AWS pcs documentation change
Summary
Updated Slurm path references to 25.05 and modified section title
Security assessment
Routine version number updates and documentation formatting changes without security impact.
Diff
diff --git a/pcs/latest/userguide/working-with_login-nodes_standalone_test.md b/pcs/latest/userguide/working-with_login-nodes_standalone_test.md index 2f7838d2f..363da4c08 100644 --- a//pcs/latest/userguide/working-with_login-nodes_standalone_test.md +++ b//pcs/latest/userguide/working-with_login-nodes_standalone_test.md @@ -16 +16 @@ Confirm that the `sackd` service is running. Sample output follows. If there are - └─9985 /opt/aws/pcs/scheduler/slurm-24.05/sbin/sackd --systemd --conf-server=10.3.149.220:6817 + └─9985 /opt/aws/pcs/scheduler/slurm-25.05/sbin/sackd --systemd --conf-server=10.3.149.220:6817 @@ -26 +26 @@ Confirm connections to the cluster are working using Slurm client commands such - [root@ip-10-3-27-112 ~]# /opt/aws/pcs/scheduler/slurm-24.11/bin/sinfo + [root@ip-10-3-27-112 ~]# /opt/aws/pcs/scheduler/slurm-25.05/bin/sinfo @@ -33 +33 @@ You should also be able to submit jobs. For example, a command similar to this e - /opt/aws/pcs/scheduler/slurm-24.11/bin/srun --nodes=1 -p all --pty bash -i + /opt/aws/pcs/scheduler/slurm-25.05/bin/srun --nodes=1 -p all --pty bash -i @@ -43 +43 @@ Step 5 – Configure the connection to the AWS PCS cluster -Networking +Connecting a standalone login node to multiple clusters