AWS parallelcluster documentation change
Summary
Minor grammatical correction (changed 'nodes' to 'node' and added comma) in login node documentation
Security assessment
Change only fixes grammar and punctuation without introducing or modifying security-related content
Diff
diff --git a/parallelcluster/latest/ug/login-nodes-v3.md b/parallelcluster/latest/ug/login-nodes-v3.md index 9985ca240..5c9ad57dd 100644 --- a//parallelcluster/latest/ug/login-nodes-v3.md +++ b//parallelcluster/latest/ug/login-nodes-v3.md @@ -7 +7 @@ -Starting from version 3.7.0, AWS ParallelCluster cluster administrators can provision login nodes that can be used to provide access to users to run jobs vs directly accessing the cluster head node. Cluster users with appropriate permissions can use Active Directory or their ssh credential to login, submit and manage their jobs. As a result, cluster management can be improved and the chances of depleting the resources of the head node required by Slurm to manage the cluster can be minimized. Logged in users will also have access to all shared storage of the cluster mounted on login nodes. If a login nodes needs to be stopped logged in users will be notified in advance through the active shell session they are using. +Starting from version 3.7.0, AWS ParallelCluster cluster administrators can provision login nodes that can be used to provide access to users to run jobs vs directly accessing the cluster head node. Cluster users with appropriate permissions can use Active Directory or their ssh credential to login, submit and manage their jobs. As a result, cluster management can be improved and the chances of depleting the resources of the head node required by Slurm to manage the cluster can be minimized. Logged in users will also have access to all shared storage of the cluster mounted on login nodes. If a login node needs to be stopped, users that are logged in will be notified in advance through the active shell session they are using.