Merge pull request #11 from Sydney-Informatics-Hub/tomm-workshop_updates

Tomm workshop updates

Author: jx-fan

notebooks/CLI.md

@@ -39,17 +39,17 @@ you will be prompted for your password and Okta credentials in a browser window
 runai project set <my_project>
 ```
 
-3. To run an `sydneyinformaticshub/dgx-interactive-gpu` container with an interactive terminal session including mounting your projects existing PVC in /scratch inside the container you can use the following command (be sure to replace everything in brackets `<...>` with values specific to your requirements):
+3. To run an `sydneyinformaticshub/dgx-interactive-terminal` container with an interactive terminal session including mounting your projects existing PVC in /scratch inside the container you can use the following command (be sure to replace everything in brackets `<...>` with values specific to your requirements):
 
 ```bash
-runai workspace submit <workspace-name> --image sydneyinformaticshub/dgx-interactive-gpu --gpu-devices-request 1 --cpu-core-request 1.0 --run-as-user --existing-pvc claimname=<pvc-name>,path=/scratch --attach
+runai workspace submit <workspace-name> --image sydneyinformaticshub/dgx-interactive-terminal --gpu-devices-request 1 --cpu-core-request 1.0 --run-as-user --existing-pvc claimname=<pvc-name>,path=/scratch --attach
 ```
 
 Here is a brief rundown of the arguments of the command above:
 
 - `runai workspace submit <workspace-name>` will run a new workspace and give it the name specified in `<workspace-name>`
 
-- `--image sydneyinformaticshub/dgx-interactive-gpu` will run the base Docker image located at `sydneyinformaticshub/dgx-interactive-gpu`, you can replace this image with your own, perhaps built yourself with extra package installs and using this image as a base
+- `--image sydneyinformaticshub/dgx-interactive-terminal` will run the base Docker image located at `sydneyinformaticshub/dgx-interactive-terminal`, you can replace this image with your own, perhaps built yourself with extra package installs and using this image as a base
 
 - `--gpu-devices-request 1 --cpu-core-request 1.0` requests 1 GPU and 1 CPU for the workflow. There are multiple options for selecting GPU and CPU RAM and devices, see [here](https://run-ai-docs.nvidia.com/self-hosted/2.22/reference/cli/runai/runai_workspace_submit) or use `runai wrkspace submit --help` for a full list of options
 
@@ -66,7 +66,7 @@ Using the CLI it is also possible to set up a workflow that persists in the back
 To set this up follow the steps 1 and 2 above, then change the command in step 3 to:
 
 ```bash
-runai workspace submit <workspace-name> --image sydneyinformaticshub/dgx-interactive-gpu --gpu-devices-request 1 --cpu-core-request 1.0 --run-as-user --existing-pvc claimname=<pvc-name>,path=/scratch --command -- bash -c 'trap : TERM INT; sleep infinity & wait'
+runai workspace submit <workspace-name> --image sydneyinformaticshub/dgx-interactive-terminal --gpu-devices-request 1 --cpu-core-request 1.0 --run-as-user --existing-pvc claimname=<pvc-name>,path=/scratch --command -- bash -c 'trap : TERM INT; sleep infinity & wait'
 ```
 
 This will run the workload and keep it persisting in the background. You can then connect to this container whenever you like using:

notebooks/data_transfer.md

@@ -6,19 +6,19 @@ Here we assume you already have set up a [project](projects.md) and have some Pe
 
 ## Interactive data transfer to/from RDS from a web-browser
 
-You can easily transfer data between your Persistent Volume Claim (PVC) and RDS from inside the Run:ai web browser interface. We have set up an [environment](environments.md) called `interactive_dt` for you to do this.
+You can easily transfer data between your Persistent Volume Claim (PVC) and RDS from inside the Run:ai web browser interface. We have set up an [environment](environments.md) called `data-transfer` for you to do this.
 
-To run the `interactive_dt` environment from a template:
+To run the `data-transfer` environment from a template:
 
 1. Log into the Run:ai dashboard at [gpu.sydney.edu.au](https://gpu.sydney.edu.au) and use Okta to login with your credentials via the "CONTINUE WITH SSO" sign in option.
 
 2. Click 'workloads' in the left panel and then the blue 'new workload' icon in the top left of the workloads screen and select 'workspace'.
 
 ![New Workload](../fig/workload_new.png)
 
-3. Select your project from the projects available and select the `interactive-data-transfer` template and give your workspace a name before clicking with your mouse cursor on CONTINUE.
+3. Select your project from the projects available and select the `data-transfer` template and give your workspace a name before clicking with your mouse cursor on CONTINUE.
 
-4. If you have selected the `interactive-data-transfer` template, you should now have pre-populated the required `interactive-dt` environment and the `data-transfer` compute resource fields on the following page. You can double check this now.
+4. If you have selected the `data-transfer` template, you should now have pre-populated the required `data-transfer` environment and the `data-transfer` compute resource fields on the following page. You can double check this now.
 
 5. Expand the `Data sources` box and select the PVC associated with your project from the list.
 
@@ -65,27 +65,6 @@ rsync -rlctP <pvc_mount_point>/<path_to_pvc_data> <your_unikey>@research-data-in
 The above rsync will also perform integrity checking using a *checksum*, comparing the original and copied files to make sure they are identical.
 
 During file transfer, for larger files, you can close the browser and leave things running in the background. You can then reconnect to check its status by logging back into the web UI at [gpu.sydney.edu.au](https://gpu.sydney.edu.au).
-    
-::: {.callout-warning}
-
-# For early adopters
-
-Until we have correct user IDs and group IDs for your unikey and project set up in the PVC and the running workflow, you will need to update the permissions of the mounted PVC as root to be able to read/write files from there. To do this:
-
-1. Change to root
-
-```bash
-sudo su
-```
-
-2. Use chmod to set read and write for all on your mounted PVC space
-
-```bash
-chmod -R 666 <PVC_mount_point>
-```
-
-You must do these steps BEFORE running the `rsync` command above.
-:::