From 19b7ab5ca2b923a9a76cefd0a1adc9f4ba473638 Mon Sep 17 00:00:00 2001 From: Umair Ayub Date: Thu, 27 Aug 2026 14:36:45 +0100 Subject: [PATCH 1/3] rename and add shs-gpu-cluster to main docs --- .../faq.md | 0 .../index.md | 2 +- .../kueue.md | 0 .../policies.md | 0 .../L1.1_building-and-testing-containers.md | 0 .../training/L1_getting_started.md | 0 .../L2.1_creating-your-first-pod-template.md | 0 .../L2_using-containers-in-the-tre.md | 0 ...ccessing_the_BeeGFS_Inside_the_EPCC_TRE.md | 0 .../L4_requesting_persistent_volumes.md | 0 .../training/L5_running_a_pytorch_task.md | 0 .../training/L6_template_workflow.md | 0 .../resources/example_pytorch_code.py | 0 docs/services/cirrus/index.md | 2 +- mkdocs.yml | 27 +++++++++---------- 15 files changed, 14 insertions(+), 17 deletions(-) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/faq.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/index.md (99%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/kueue.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/policies.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/training/L1.1_building-and-testing-containers.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/training/L1_getting_started.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/training/L2.1_creating-your-first-pod-template.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/training/L2_using-containers-in-the-tre.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/training/L4_requesting_persistent_volumes.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/training/L5_running_a_pytorch_task.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/training/L6_template_workflow.md (100%) rename docs/safe-haven-services/{tre-gpu-service => shs-gpu-cluster}/training/resources/example_pytorch_code.py (100%) diff --git a/docs/safe-haven-services/tre-gpu-service/faq.md b/docs/safe-haven-services/shs-gpu-cluster/faq.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/faq.md rename to docs/safe-haven-services/shs-gpu-cluster/faq.md diff --git a/docs/safe-haven-services/tre-gpu-service/index.md b/docs/safe-haven-services/shs-gpu-cluster/index.md similarity index 99% rename from docs/safe-haven-services/tre-gpu-service/index.md rename to docs/safe-haven-services/shs-gpu-cluster/index.md index 262fe9745..3e64aae5a 100644 --- a/docs/safe-haven-services/tre-gpu-service/index.md +++ b/docs/safe-haven-services/shs-gpu-cluster/index.md @@ -113,7 +113,7 @@ This tutorial teaches users how to submit tasks to the SHS GPU Cluster. It assum | [Using Containers in the SHS](training/L2_using-containers-in-the-tre.md) | a. How to run containers inside the SHS.
b. Security considerations for SHS containers.
c. How to manage container dependencies. | | [Creating Your First Pod Template](training/L2.1_creating-your-first-pod-template.md) | a. What is a Kubernetes pod template.
b. How to define pod resources.
c. How to submit a pod to the GPU cluster. | | [Accessing the BeeGFS Inside the SHS _GPU Cluster_](training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md) | a. How to access BeeGFS from the SHS _GPU Cluster_.
b. How to read/write data efficiently.
c. Best practices for using shared storage. | -| [Requesting Persistent Volumes](training/L4_requesting_persistent_volumes.md) | a. How pods use persistent storage (Persistent Volumes and Persistent Volume Claims).
b. How SHS _GPU Cluster_ users access pre-provisioned storage via Persistent Volume Claims.
c. How to attach Persistent Volume Claims to pods using volumeMounts and proper securityContext. | +| [Requesting Persistent Volumes](training/L4_requesting_persistent_volumes.md) | a. How pods use persistent storage (Persistent Volumes and Persistent Volume Claims).
b. How SHS _GPU Cluster_ users access pre-provisioned storage via Persistent Volume Claims.
c. How to attach Persistent Volume Claims to pods using volumeMounts and proper securityContext. | ## Further Reading and Help diff --git a/docs/safe-haven-services/tre-gpu-service/kueue.md b/docs/safe-haven-services/shs-gpu-cluster/kueue.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/kueue.md rename to docs/safe-haven-services/shs-gpu-cluster/kueue.md diff --git a/docs/safe-haven-services/tre-gpu-service/policies.md b/docs/safe-haven-services/shs-gpu-cluster/policies.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/policies.md rename to docs/safe-haven-services/shs-gpu-cluster/policies.md diff --git a/docs/safe-haven-services/tre-gpu-service/training/L1.1_building-and-testing-containers.md b/docs/safe-haven-services/shs-gpu-cluster/training/L1.1_building-and-testing-containers.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/training/L1.1_building-and-testing-containers.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L1.1_building-and-testing-containers.md diff --git a/docs/safe-haven-services/tre-gpu-service/training/L1_getting_started.md b/docs/safe-haven-services/shs-gpu-cluster/training/L1_getting_started.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/training/L1_getting_started.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L1_getting_started.md diff --git a/docs/safe-haven-services/tre-gpu-service/training/L2.1_creating-your-first-pod-template.md b/docs/safe-haven-services/shs-gpu-cluster/training/L2.1_creating-your-first-pod-template.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/training/L2.1_creating-your-first-pod-template.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L2.1_creating-your-first-pod-template.md diff --git a/docs/safe-haven-services/tre-gpu-service/training/L2_using-containers-in-the-tre.md b/docs/safe-haven-services/shs-gpu-cluster/training/L2_using-containers-in-the-tre.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/training/L2_using-containers-in-the-tre.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L2_using-containers-in-the-tre.md diff --git a/docs/safe-haven-services/tre-gpu-service/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md b/docs/safe-haven-services/shs-gpu-cluster/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md diff --git a/docs/safe-haven-services/tre-gpu-service/training/L4_requesting_persistent_volumes.md b/docs/safe-haven-services/shs-gpu-cluster/training/L4_requesting_persistent_volumes.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/training/L4_requesting_persistent_volumes.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L4_requesting_persistent_volumes.md diff --git a/docs/safe-haven-services/tre-gpu-service/training/L5_running_a_pytorch_task.md b/docs/safe-haven-services/shs-gpu-cluster/training/L5_running_a_pytorch_task.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/training/L5_running_a_pytorch_task.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L5_running_a_pytorch_task.md diff --git a/docs/safe-haven-services/tre-gpu-service/training/L6_template_workflow.md b/docs/safe-haven-services/shs-gpu-cluster/training/L6_template_workflow.md similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/training/L6_template_workflow.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L6_template_workflow.md diff --git a/docs/safe-haven-services/tre-gpu-service/training/resources/example_pytorch_code.py b/docs/safe-haven-services/shs-gpu-cluster/training/resources/example_pytorch_code.py similarity index 100% rename from docs/safe-haven-services/tre-gpu-service/training/resources/example_pytorch_code.py rename to docs/safe-haven-services/shs-gpu-cluster/training/resources/example_pytorch_code.py diff --git a/docs/services/cirrus/index.md b/docs/services/cirrus/index.md index f4a810599..e4557440c 100644 --- a/docs/services/cirrus/index.md +++ b/docs/services/cirrus/index.md @@ -1,6 +1,6 @@ # Overview -The Cirrus service provides access to CPU-based high-performance computing resources. As well as being part of the +The Cirrus service provides access to CPU-based high-performance computing resources. As well as being part of the EIDF, Cirrus is one of the UKRI National Compute Resources (NCRs). Cirrus is a HPE EX4000 supercomputing system which has a total of 256 compute nodes. Each compute node has 288 cores (dual AMD EPYC 9825 144-core 2.2 GHz processors) giving a total of 73,228 cores. 192 are standard memory compute nodes with 768 GB DDR5 RAM and 64 are high memory compute nodes with 1536 GB DDR5 RAM. Compute nodes are connected together by a HPE Slingshot 11 interconnect. diff --git a/mkdocs.yml b/mkdocs.yml index b747694d4..3656f2276 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -127,21 +127,18 @@ nav: - "Development Workflow": safe-haven-services/shs-container-user-guide/development-workflow.md - "Workflow Examples": safe-haven-services/shs-container-user-guide/workflow-examples.md - "Container Examples": safe-haven-services/shs-container-user-guide/container-examples.md - # TRE GPU service docs can be uncommented and added to - # the navigation menu when the TRE GPU service is made - # available to TRE tenants. See Umair Ayub and Kostas for details. - # - "TRE GPU Service": - # - "Overview": safe-haven-services/tre-gpu-service/index.md - # - "Policies": safe-haven-services/tre-gpu-service/policies.md - # - "Kueue": safe-haven-services/tre-gpu-service/kueue.md - # - "Tutorials": - # - "Getting Started": safe-haven-services/tre-gpu-service/training/L1_getting_started.md - # - "Building and Pushing Containers to GHCR": safe-haven-services/tre-gpu-service/training/L1.1_building-and-testing-containers.md - # - "Downloading Containers in the TRE GPU Cluster": safe-haven-services/tre-gpu-service/training/L2_using-containers-in-the-tre.md - # - "Creating your first pod template within a job yaml file": safe-haven-services/tre-gpu-service/training/L2.1_creating-your-first-pod-template.md - # - "Transfer Data Inside the TRE GPU Cluster": safe-haven-services/tre-gpu-service/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md - # - "Persistent Volumes": safe-haven-services/tre-gpu-service/training/L4_requesting_persistent_volumes.md - # - "GPU Service FAQ": safe-haven-services/tre-gpu-service/faq.md + - "SHS GPU Cluster": + - "Overview": safe-haven-services/shs-gpu-cluster/index.md + - "Policies": safe-haven-services/shs-gpu-cluster/policies.md + - "Kueue": safe-haven-services/shs-gpu-cluster/kueue.md + - "Tutorials": + - "Getting Started": safe-haven-services/shs-gpu-cluster/training/L1_getting_started.md + - "Building and Pushing Containers to GHCR": safe-haven-services/shs-gpu-cluster/training/L1.1_building-and-testing-containers.md + - "Downloading Containers in the SHS GPU Cluster": safe-haven-services/shs-gpu-cluster/training/L2_using-containers-in-the-tre.md + - "Creating your first pod template within a job yaml file": safe-haven-services/shs-gpu-cluster/training/L2.1_creating-your-first-pod-template.md + - "Transfer Data Inside the SHS GPU Cluster": safe-haven-services/shs-gpu-cluster/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md + - "Persistent Volumes": safe-haven-services/shs-gpu-cluster/training/L4_requesting_persistent_volumes.md + - "SHS GPU Cluster FAQ": safe-haven-services/shs-gpu-cluster/faq.md # Application Services (Open OnDemand) docs can be uncommented # and added to the navigation menu when the service is made # available to safe haven users. See MikeJ for details. From e90b09077e9f043d3434db656cbe11588b278641 Mon Sep 17 00:00:00 2001 From: Umair Ayub Date: Fri, 28 Aug 2026 14:20:25 +0100 Subject: [PATCH 2/3] update the page links for shs gpu cluster --- docs/safe-haven-services/shs-gpu-cluster/index.md | 10 +++++----- ...ainers.md => L2_building_and_testing_containers.md} | 0 ...in-the-tre.md => L3_using_containers_in_the_shs.md} | 0 ...plate.md => L4_creating_your_first_pod_template.md} | 0 ... => L5_accessing_the_beegfs_inside_the_epcc_shs.md} | 0 ..._volumes.md => L6_requesting_persistent_volumes.md} | 0 ..._a_pytorch_task.md => L7_running_a_pytorch_task.md} | 2 +- ...L6_template_workflow.md => L8_template_workflow.md} | 4 ++-- mkdocs.yml | 10 +++++----- 9 files changed, 13 insertions(+), 13 deletions(-) rename docs/safe-haven-services/shs-gpu-cluster/training/{L1.1_building-and-testing-containers.md => L2_building_and_testing_containers.md} (100%) rename docs/safe-haven-services/shs-gpu-cluster/training/{L2_using-containers-in-the-tre.md => L3_using_containers_in_the_shs.md} (100%) rename docs/safe-haven-services/shs-gpu-cluster/training/{L2.1_creating-your-first-pod-template.md => L4_creating_your_first_pod_template.md} (100%) rename docs/safe-haven-services/shs-gpu-cluster/training/{L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md => L5_accessing_the_beegfs_inside_the_epcc_shs.md} (100%) rename docs/safe-haven-services/shs-gpu-cluster/training/{L4_requesting_persistent_volumes.md => L6_requesting_persistent_volumes.md} (100%) rename docs/safe-haven-services/shs-gpu-cluster/training/{L5_running_a_pytorch_task.md => L7_running_a_pytorch_task.md} (99%) rename docs/safe-haven-services/shs-gpu-cluster/training/{L6_template_workflow.md => L8_template_workflow.md} (99%) diff --git a/docs/safe-haven-services/shs-gpu-cluster/index.md b/docs/safe-haven-services/shs-gpu-cluster/index.md index 3e64aae5a..d442308f2 100644 --- a/docs/safe-haven-services/shs-gpu-cluster/index.md +++ b/docs/safe-haven-services/shs-gpu-cluster/index.md @@ -109,11 +109,11 @@ This tutorial teaches users how to submit tasks to the SHS GPU Cluster. It assum | Lesson | Objective | |-----------------------------------|-------------------------------------| | [Getting started with Kubernetes](training/L1_getting_started.md) | a. What is Kubernetes?
b. How to send a task to a GPU node.
c. How to define the GPU resources needed. | -| [Building and Testing Containers](training/L1.1_building-and-testing-containers.md) | a. How to build container images.
b. How to test containers locally.
c. Best practices for container setup. | -| [Using Containers in the SHS](training/L2_using-containers-in-the-tre.md) | a. How to run containers inside the SHS.
b. Security considerations for SHS containers.
c. How to manage container dependencies. | -| [Creating Your First Pod Template](training/L2.1_creating-your-first-pod-template.md) | a. What is a Kubernetes pod template.
b. How to define pod resources.
c. How to submit a pod to the GPU cluster. | -| [Accessing the BeeGFS Inside the SHS _GPU Cluster_](training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md) | a. How to access BeeGFS from the SHS _GPU Cluster_.
b. How to read/write data efficiently.
c. Best practices for using shared storage. | -| [Requesting Persistent Volumes](training/L4_requesting_persistent_volumes.md) | a. How pods use persistent storage (Persistent Volumes and Persistent Volume Claims).
b. How SHS _GPU Cluster_ users access pre-provisioned storage via Persistent Volume Claims.
c. How to attach Persistent Volume Claims to pods using volumeMounts and proper securityContext. | +| [Building and Testing Containers](training/L2_building_and_testing_containers.md) | a. How to build container images.
b. How to test containers locally.
c. Best practices for container setup. | +| [Using Containers in the SHS](training/L3_using_containers_in_the_shs.md) | a. How to run containers inside the SHS.
b. Security considerations for SHS containers.
c. How to manage container dependencies. | +| [Creating Your First Pod Template](training/L4_creating_your_first_pod_template.md) | a. What is a Kubernetes pod template.
b. How to define pod resources.
c. How to submit a pod to the GPU cluster. | +| [Accessing the BeeGFS Inside the SHS _GPU Cluster_](training/L5_accessing_the_beegfs_inside_the_epcc_shs.md) | a. How to access BeeGFS from the SHS _GPU Cluster_.
b. How to read/write data efficiently.
c. Best practices for using shared storage. | +| [Requesting Persistent Volumes](training/L6_requesting_persistent_volumes.md) | a. How pods use persistent storage (Persistent Volumes and Persistent Volume Claims).
b. How SHS _GPU Cluster_ users access pre-provisioned storage via Persistent Volume Claims.
c. How to attach Persistent Volume Claims to pods using volumeMounts and proper securityContext. | ## Further Reading and Help diff --git a/docs/safe-haven-services/shs-gpu-cluster/training/L1.1_building-and-testing-containers.md b/docs/safe-haven-services/shs-gpu-cluster/training/L2_building_and_testing_containers.md similarity index 100% rename from docs/safe-haven-services/shs-gpu-cluster/training/L1.1_building-and-testing-containers.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L2_building_and_testing_containers.md diff --git a/docs/safe-haven-services/shs-gpu-cluster/training/L2_using-containers-in-the-tre.md b/docs/safe-haven-services/shs-gpu-cluster/training/L3_using_containers_in_the_shs.md similarity index 100% rename from docs/safe-haven-services/shs-gpu-cluster/training/L2_using-containers-in-the-tre.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L3_using_containers_in_the_shs.md diff --git a/docs/safe-haven-services/shs-gpu-cluster/training/L2.1_creating-your-first-pod-template.md b/docs/safe-haven-services/shs-gpu-cluster/training/L4_creating_your_first_pod_template.md similarity index 100% rename from docs/safe-haven-services/shs-gpu-cluster/training/L2.1_creating-your-first-pod-template.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L4_creating_your_first_pod_template.md diff --git a/docs/safe-haven-services/shs-gpu-cluster/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md b/docs/safe-haven-services/shs-gpu-cluster/training/L5_accessing_the_beegfs_inside_the_epcc_shs.md similarity index 100% rename from docs/safe-haven-services/shs-gpu-cluster/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L5_accessing_the_beegfs_inside_the_epcc_shs.md diff --git a/docs/safe-haven-services/shs-gpu-cluster/training/L4_requesting_persistent_volumes.md b/docs/safe-haven-services/shs-gpu-cluster/training/L6_requesting_persistent_volumes.md similarity index 100% rename from docs/safe-haven-services/shs-gpu-cluster/training/L4_requesting_persistent_volumes.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L6_requesting_persistent_volumes.md diff --git a/docs/safe-haven-services/shs-gpu-cluster/training/L5_running_a_pytorch_task.md b/docs/safe-haven-services/shs-gpu-cluster/training/L7_running_a_pytorch_task.md similarity index 99% rename from docs/safe-haven-services/shs-gpu-cluster/training/L5_running_a_pytorch_task.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L7_running_a_pytorch_task.md index 086a0c6b8..5eb1f987a 100644 --- a/docs/safe-haven-services/shs-gpu-cluster/training/L5_running_a_pytorch_task.md +++ b/docs/safe-haven-services/shs-gpu-cluster/training/L7_running_a_pytorch_task.md @@ -2,7 +2,7 @@ ## Requirements -It is recommended that users complete [Getting started with Kubernetes](./L1_getting_started.md) and [Requesting persistent volumes With Kubernetes](./L4_requesting_persistent_volumes.md) before proceeding with this tutorial. +It is recommended that users complete [Getting started with Kubernetes](./L1_getting_started.md) and [Requesting persistent volumes With Kubernetes](./L6_requesting_persistent_volumes.md) before proceeding with this tutorial. ## Overview diff --git a/docs/safe-haven-services/shs-gpu-cluster/training/L6_template_workflow.md b/docs/safe-haven-services/shs-gpu-cluster/training/L8_template_workflow.md similarity index 99% rename from docs/safe-haven-services/shs-gpu-cluster/training/L6_template_workflow.md rename to docs/safe-haven-services/shs-gpu-cluster/training/L8_template_workflow.md index 96b8460db..9833a5770 100644 --- a/docs/safe-haven-services/shs-gpu-cluster/training/L6_template_workflow.md +++ b/docs/safe-haven-services/shs-gpu-cluster/training/L8_template_workflow.md @@ -2,7 +2,7 @@ ## Requirements -It is recommended that users complete [Getting started with Kubernetes](./L1_getting_started.md) and [Requesting persistent volumes With Kubernetes](./L4_requesting_persistent_volumes.md) before proceeding with this tutorial. +It is recommended that users complete [Getting started with Kubernetes](./L1_getting_started.md) and [Requesting persistent volumes With Kubernetes](./L6_requesting_persistent_volumes.md) before proceeding with this tutorial. ## Overview @@ -32,7 +32,7 @@ The SHS GPU Cluster contains GPUs with 40Gb/80Gb of on board memory and it is ex Persistent volume claims need to be of sufficient size to hold the input data, any expected output data and a small amount of additional empty space to facilitate IO. -Read the [requesting persistent volumes with Kubernetes](L4_requesting_persistent_volumes.md) lesson to learn how to request and mount persistent volumes to pods. +Read the [requesting persistent volumes with Kubernetes](L6_requesting_persistent_volumes.md) lesson to learn how to request and mount persistent volumes to pods. It often takes several hours or days to download data sets of 1/2 TB or more to a persistent volume. diff --git a/mkdocs.yml b/mkdocs.yml index 3656f2276..2a99c5997 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -133,11 +133,11 @@ nav: - "Kueue": safe-haven-services/shs-gpu-cluster/kueue.md - "Tutorials": - "Getting Started": safe-haven-services/shs-gpu-cluster/training/L1_getting_started.md - - "Building and Pushing Containers to GHCR": safe-haven-services/shs-gpu-cluster/training/L1.1_building-and-testing-containers.md - - "Downloading Containers in the SHS GPU Cluster": safe-haven-services/shs-gpu-cluster/training/L2_using-containers-in-the-tre.md - - "Creating your first pod template within a job yaml file": safe-haven-services/shs-gpu-cluster/training/L2.1_creating-your-first-pod-template.md - - "Transfer Data Inside the SHS GPU Cluster": safe-haven-services/shs-gpu-cluster/training/L3_Accessing_the_BeeGFS_Inside_the_EPCC_TRE.md - - "Persistent Volumes": safe-haven-services/shs-gpu-cluster/training/L4_requesting_persistent_volumes.md + - "Building and Pushing Containers to GHCR": safe-haven-services/shs-gpu-cluster/training/L2_building_and_testing_containers.md + - "Downloading Containers in the SHS GPU Cluster": safe-haven-services/shs-gpu-cluster/training/L3_using_containers_in_the_shs.md + - "Creating your first pod template within a job yaml file": safe-haven-services/shs-gpu-cluster/training/L4_creating_your_first_pod_template.md + - "Transfer Data Inside the SHS GPU Cluster": safe-haven-services/shs-gpu-cluster/training/L5_accessing_the_beegfs_inside_the_epcc_shs.md + - "Persistent Volumes": safe-haven-services/shs-gpu-cluster/training/L6_requesting_persistent_volumes.md - "SHS GPU Cluster FAQ": safe-haven-services/shs-gpu-cluster/faq.md # Application Services (Open OnDemand) docs can be uncommented # and added to the navigation menu when the service is made From 61b02697b6e600d1920477c5ae1c005503c10696 Mon Sep 17 00:00:00 2001 From: Umair Ayub Date: Fri, 28 Aug 2026 15:51:31 +0100 Subject: [PATCH 3/3] Revert services/cirrus/index.md to previous version --- docs/services/cirrus/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/services/cirrus/index.md b/docs/services/cirrus/index.md index e4557440c..f4a810599 100644 --- a/docs/services/cirrus/index.md +++ b/docs/services/cirrus/index.md @@ -1,6 +1,6 @@ # Overview -The Cirrus service provides access to CPU-based high-performance computing resources. As well as being part of the +The Cirrus service provides access to CPU-based high-performance computing resources. As well as being part of the EIDF, Cirrus is one of the UKRI National Compute Resources (NCRs). Cirrus is a HPE EX4000 supercomputing system which has a total of 256 compute nodes. Each compute node has 288 cores (dual AMD EPYC 9825 144-core 2.2 GHz processors) giving a total of 73,228 cores. 192 are standard memory compute nodes with 768 GB DDR5 RAM and 64 are high memory compute nodes with 1536 GB DDR5 RAM. Compute nodes are connected together by a HPE Slingshot 11 interconnect.