Documentation changes related to CentOS 7 and PBS Pro within the cluster-toolkit repository. (GoogleCloudPlatform#4792)

Co-authored-by: Sudheer <markapurams@google.com>

Author: siddhartha-quad

docs/gpu-support.md

@@ -12,8 +12,7 @@
 ## Accelerator definition automation
 
 The schedmd-slurm-gcp-v6 modules ([nodeset], [controller] and [login]),
-the [vm-instance] module and any module relying on [vm-instance] (HTCondor and
-PBS Pro) support
+the [vm-instance] module and any module relying on [vm-instance] (HTCondor) support
 automation for defining the `guest_accelerator` config. If the user supplies any
 value for this setting, the automation will be bypassed.
 

docs/network_storage.md

@@ -99,18 +99,18 @@ The following is an example setting up a filestore using startup script:
 The following matrix shows the best method by which each type of network storage
 device should be mounted to each mount capable module.
 
-  | Slurm V6 | Batch | vm-instance | Packer (client install) | HTCondor\* | PBS Pro\*
--- | -- | -- | -- | -- | -- | --
-filestore | via USE | via USE | via USE | via STARTUP | via USE | via USE
-nfs-server | via USE | via USE | via USE | via STARTUP | via USE | via USE
-cloud-storage-bucket (GCS)| via USE | via USE | via USE | via STARTUP | via USE | via USE
-Managed Lustre | via USE | Needs Testing | via USE | Needs Testing | Needs Testing |  Needs Testing
-netapp-volume | Needs Testing | Needs Testing | via USE | Needs Testing | Needs Testing | Needs Testing
-  |  |   |   |   |   |  
-filestore (pre-existing) | via USE | via USE | via USE | via STARTUP | via USE | via USE
-nfs-server (pre-existing) | via USE | via USE | via USE | via STARTUP | via USE | via USE
-Managed Lustre (pre-existing) | via USE| Needs Testing | via USE | Needs Testing | Needs Testing |  Needs Testing
-GCS FUSE (pre-existing) | via USE | via USE | via USE | via STARTUP | via USE | Needs Testing
+  | Slurm V6 | Batch | vm-instance | Packer (client install) | HTCondor\*
+-- | -- | -- | -- | -- | --
+filestore | via USE | via USE | via USE | via STARTUP | via USE
+nfs-server | via USE | via USE | via USE | via STARTUP | via USE
+cloud-storage-bucket (GCS)| via USE | via USE | via USE | via STARTUP | via USE
+Managed Lustre | via USE | Needs Testing | via USE | Needs Testing | Needs Testing
+netapp-volume | Needs Testing | Needs Testing | via USE | Needs Testing | Needs Testing
+  |  |   |   |   |    
+filestore (pre-existing) | via USE | via USE | via USE | via STARTUP | via USE
+nfs-server (pre-existing) | via USE | via USE | via USE | via STARTUP | via USE
+Managed Lustre (pre-existing) | via USE| Needs Testing | via USE | Needs Testing | Needs Testing
+GCS FUSE (pre-existing) | via USE | via USE | via USE | via STARTUP | via USE
 
 - **via USE:** Client installation and mounting occur automatically when
   connected with the use field. See
@@ -121,7 +121,7 @@ GCS FUSE (pre-existing) | via USE | via USE | via USE | via STARTUP | via USE |
 - **Needs Testing:** May currently work but has not yet been fully tested.
 - **Not Supported:** This feature is not supported right now.
 
-\* only supported on CentOS 7\
+\* only supported on CentOS 7
 
 [filestore]: ../modules/file-system/filestore/README.md
 [pre-existing-network-storage]: ../modules/file-system/pre-existing-network-storage/README.md

docs/vm-images.md

@@ -36,9 +36,9 @@ either the specific module definition or the global variables. The
 
 ```yaml
 instance_image:
-  project: centos-cloud
-  family: centos-v7        # If family is defined, omit name
-  name: centos-7-v20230809 # If name is defined, omit family
+ family: hpc-rocky-linux-8
+ project: cloud-hpc-image-public    # If family is defined, omit name
+ name: hpc-rocky-linux-8-v20251117  # If name is defined, omit family
 ```
 
 The `project` setting defines the space where the image will be found. Either

examples/README.md

@@ -265,7 +265,7 @@ File systems:
   2.5 TiB of capacity
 * The projectsfs is mounted at `/projects` and is a high scale SSD filestore
   instance with 10TiB of capacity.
-* The managed_lustre is mounted at /lustre and is designed for the highly parallel and random I/O performance. It has a minimum capacity of ~18TiB.
+* The lustre-gcp is mounted at /lustre and is designed for the highly parallel and random I/O performance. It has a minimum capacity of ~18TiB. [GCP Managed Lustre module](../modules/file-system/managed-lustre/README.md)
 
 #### Quota Requirements for hpc-enterprise-slurm.yaml