diff --git a/docs/hpc/01_getting_started/03_walkthrough_request_hpc_account.mdx b/docs/hpc/01_getting_started/03_walkthrough_request_hpc_account.mdx index 75e1405639..8957964a34 100644 --- a/docs/hpc/01_getting_started/03_walkthrough_request_hpc_account.mdx +++ b/docs/hpc/01_getting_started/03_walkthrough_request_hpc_account.mdx @@ -4,7 +4,7 @@ import TabItem from '@theme/TabItem'; # How to request an HPC account :::tip -Make sure you don't already have an HPC account. You can check this by attempting to log in to the cluster, according to the instructions at [Connecting to the HPC Cluster](../02_connecting_to_hpc/01_connecting_to_hpc.md). +Make sure you don't already have an HPC account. You can check this by attempting to log in to the cluster, according to the instructions at [Connecting to the HPC Cluster](../02_connecting_to_hpc/01_connecting_to_hpc.mdx). ::: Login to the URL given below, using your NetID/password, to create or manage HPC Account Requests: diff --git a/docs/hpc/01_getting_started/06_hpc_accounts_external_collaborators.md b/docs/hpc/01_getting_started/06_hpc_accounts_external_collaborators.md index 6ca3ef058b..c9aad3d114 100644 --- a/docs/hpc/01_getting_started/06_hpc_accounts_external_collaborators.md +++ b/docs/hpc/01_getting_started/06_hpc_accounts_external_collaborators.md @@ -13,7 +13,7 @@ External (non-NYU) collaborators can access, with proper sponsorship, the NYU HP :::note Once the sponsoring faculty approves the account request, the HPC account is created within one hour. ::: -- Once the HPC account is created, the external collaborator can access HPC resources as described in our documentation page [Connecting to the HPC Cluster](../02_connecting_to_hpc/01_connecting_to_hpc.md). +- Once the HPC account is created, the external collaborator can access HPC resources as described in our documentation page [Connecting to the HPC Cluster](../02_connecting_to_hpc/01_connecting_to_hpc.mdx). :::note As with all sponsored accounts, HPC accounts for external collaborators are valid for a period of 12 months, at which point a renewal process is required to continue access to the NYU HPC environment. You can find information about renewing your account on our documentation page [Getting and Renewing an HPC Account](./02_getting_and_renewing_an_account.mdx). diff --git a/docs/hpc/02_connecting_to_hpc/01_connecting_to_hpc.md b/docs/hpc/02_connecting_to_hpc/01_connecting_to_hpc.mdx similarity index 90% rename from docs/hpc/02_connecting_to_hpc/01_connecting_to_hpc.md rename to docs/hpc/02_connecting_to_hpc/01_connecting_to_hpc.mdx index 14aa38a497..cd79a13d26 100644 --- a/docs/hpc/02_connecting_to_hpc/01_connecting_to_hpc.md +++ b/docs/hpc/02_connecting_to_hpc/01_connecting_to_hpc.mdx @@ -33,6 +33,12 @@ Host torch login.torch.hpc.nyu.edu UserKnownHostsFile /dev/null LogLevel ERROR ``` + +:::warning[No SSH Keys on Torch] +SSH keys are not supported on Torch due to increased security resrtictions. +::: + + ### MacOS/Linux MacOS/Linux machines have SSH clients pre-installed. Using the editor of your choice, open the `~/.ssh/config` file on your machine and add the contents listed above. @@ -119,19 +125,6 @@ There is an extra layer of security when accessing Torch which is described belo - Return to terminal and hit Enter ![torch-ssh-2fa-9](static/torch-ssh-2fa-9.png) -## SSH Keys for Torch -:::warning -SSH keys are not supported on Torch! -::: - -Instead of typing your password every time you need to log in, you can also specify an ssh key. - -- Only do that on the computer you trust -- Generate ssh key pair (terminal in Linux/Mac or cmd/WSL in Windows) [using ssh keygen](https://www.ssh.com/ssh/keygen/) -- Note the path to ssh key files. Don't share key files with anybody - anybody with this key file can login to your account -- Log into cluster using regular login/password and then add the content of generated public key file (the one with .pub) to `$HOME/.ssh/authorized_keys` on cluster -- Next time you will log into cluster no password will be required - [nyu vpn link]: https://www.nyu.edu/life/information-technology/infrastructure/network-services/vpn.html diff --git a/docs/hpc/03_storage/07_transferring_cloud_storage_data_with_rclone.md b/docs/hpc/03_storage/07_transferring_cloud_storage_data_with_rclone.md index 1040b38b59..79a6713d9a 100644 --- a/docs/hpc/03_storage/07_transferring_cloud_storage_data_with_rclone.md +++ b/docs/hpc/03_storage/07_transferring_cloud_storage_data_with_rclone.md @@ -33,7 +33,7 @@ There are specific instruction on the [rclone web site](https://rclone.org/drive ### Step 1: Login to Torch: -Follow [instructions](../02_connecting_to_hpc/01_connecting_to_hpc.md) to log into the Torch HPC cluster. +Follow [instructions](../02_connecting_to_hpc/01_connecting_to_hpc.mdx) to log into the Torch HPC cluster. ### Step 2: Load the rclone module ```sh diff --git a/docs/hpc/08_ml_ai_hpc/05_run_hf_model.md b/docs/hpc/08_ml_ai_hpc/05_run_hf_model.md index 5a58fb7ef1..f134469aa3 100644 --- a/docs/hpc/08_ml_ai_hpc/05_run_hf_model.md +++ b/docs/hpc/08_ml_ai_hpc/05_run_hf_model.md @@ -5,7 +5,7 @@ Here we provide an example of how one can run a Hugging Face Large-language mode ## Prepare environment ### Create project directory -After [logging on to a Torch login node](../02_connecting_to_hpc/01_connecting_to_hpc.md), make a directory for this project: +After [logging on to a Torch login node](../02_connecting_to_hpc/01_connecting_to_hpc.mdx), make a directory for this project: ```bash [NetID@log-1 ~]$ mkdir -p /scratch/NetID/llm_example [NetID@log-1 ~]$ cd /scratch/NetID/llm_example diff --git a/docs/hpc/09_ood/01_ood_intro.md b/docs/hpc/09_ood/01_ood_intro.md index 78dde8e737..0050b42083 100644 --- a/docs/hpc/09_ood/01_ood_intro.md +++ b/docs/hpc/09_ood/01_ood_intro.md @@ -63,4 +63,4 @@ Just click on the `Session ID` link and a tab will open with the contents of the #### From terminal -If your session is no longer visible from within OOD you may still be able to find your logs via the terminal. Simply [log into Torch](../02_connecting_to_hpc/01_connecting_to_hpc.md) and `cd` to `/home/$USER/ondemand/data/sys/dashboard/batch_connect/sys/` and then `cd` into the directory for the app that you're interested in. You should find the file `output.log` there. +If your session is no longer visible from within OOD you may still be able to find your logs via the terminal. Simply [log into Torch](../02_connecting_to_hpc/01_connecting_to_hpc.mdx) and `cd` to `/home/$USER/ondemand/data/sys/dashboard/batch_connect/sys/` and then `cd` into the directory for the app that you're interested in. You should find the file `output.log` there. diff --git a/docs/hpc/09_ood/07_jupyter_with_conda_singularity.mdx b/docs/hpc/09_ood/07_jupyter_with_conda_singularity.mdx index 195a66d0e7..972b98502a 100644 --- a/docs/hpc/09_ood/07_jupyter_with_conda_singularity.mdx +++ b/docs/hpc/09_ood/07_jupyter_with_conda_singularity.mdx @@ -4,7 +4,7 @@ This page describes how to use your Singularity with conda environment in OOD GUI at Torch. ### Log Into Torch via the Terminal -The following commands must be run from the terminal. Information on accessing via the terminal can be found at [Connecting to the HPC](../02_connecting_to_hpc/01_connecting_to_hpc.md) or you can log into OOD and select the `Clusters` tab at the top of the page and select `Torch Shell Access`. +The following commands must be run from the terminal. Information on accessing via the terminal can be found at [Connecting to the HPC](../02_connecting_to_hpc/01_connecting_to_hpc.mdx) or you can log into OOD and select the `Clusters` tab at the top of the page and select `Torch Shell Access`. ### Preinstallation Warning :::warning