From 894472e7c1b9d4f7a18c8b700e1563036de9f593 Mon Sep 17 00:00:00 2001 From: Manjila Singh Date: Fri, 23 Aug 2024 20:38:35 +0100 Subject: [PATCH 1/2] Update Infrastructure access page --- docs/services/access.md | 26 ++++++++++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/docs/services/access.md b/docs/services/access.md index 2d40037..ba0bf72 100644 --- a/docs/services/access.md +++ b/docs/services/access.md @@ -18,10 +18,32 @@ CIROH has partnered with AWS, 2i2c and Google Cloud to provide CIROH also operates an on-premises infrastructure that includes high-performance computing (HPC) resources and specialized software. To request access to the on-premises infrastructure, please submit a GitHub template request detailing your project requirements and specifications. Our team will review your request and assist you in obtaining the necessary access. On-premises Infrastructure Request Form -_____ - +
+
:::note - This form must be submitted by Principal Investigator (PI) of the project. - Your request will be handled by DevOps staff at CIROH and if permitted will be given access to the research cloud or on-premise infrastructure. ::: + +### How to get access to Pantarhei? + +**Step 1**: Submit the On-Premise Infrastructure Request Form below to get access to Pantarhei: + +We encourage PI of the project to start here: (select On-Premises Infrastructure Request Form and fill out details) + + Infrastructure Request Form + +--- + +**Step 2**: Submit the On-premise Access Request form for individual user accounts on Pantarhei: + + On-Premise Access Request Form + +--- + +:::note +For UA users, please submit On-Premises Access Request Form. For outside UA users, please start with VPN Access Request Form followed by On-Premises Access Request Form +::: + + From 5b8a823d048ba31417ea375c154f968922e57fc9 Mon Sep 17 00:00:00 2001 From: Manjila Singh Date: Fri, 23 Aug 2024 21:10:04 +0100 Subject: [PATCH 2/2] Update documentation --- .../cloudservices/aws/documentation/aws-s3-sync/index.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/services/cloudservices/aws/documentation/aws-s3-sync/index.md b/docs/services/cloudservices/aws/documentation/aws-s3-sync/index.md index dd3101b..1175ea7 100644 --- a/docs/services/cloudservices/aws/documentation/aws-s3-sync/index.md +++ b/docs/services/cloudservices/aws/documentation/aws-s3-sync/index.md @@ -78,5 +78,4 @@ aws s3 sync s3://my-source-bucket s3://my-destination-bucket \ - The --profile (or --dest-profile in some AWS CLI versions) is used for writing to the destination bucket. - Ensure both profiles have the necessary permissions on their respective buckets. - Be cautious with the --delete flag as it removes files in the destination that don't exist in the source. -- Always test with --dryrun first to ensure the operation will do what you expect. -- Basically, you have to create two access key profile, and attach those appropriate \ No newline at end of file +- Always test with --dryrun first to ensure the operation will do what you expect. \ No newline at end of file