torch is now open to all

Author: s-sajid-ali

docs/cloud/03_hpc_bursting_to_cloud/01_intro.md

@@ -16,7 +16,7 @@ To request access to the HPC Bursting capabilities, [please complete this form][
 This is not public, only per request of eligible classes or researchers
 :::
 ```sh
-ssh <NetID>@torch.hpc.nyu.edu
+ssh <NetID>@login.torch.hpc.nyu.edu
 ```
 ssh to the class on GCP (burst login node) - anyone can login but you can only submit jobs if you have approval
 ```sh

docs/cloud/03_hpc_bursting_to_cloud/02_visualization.md

@@ -10,7 +10,7 @@ Add the following to your SSH config file (~/.ssh/config) on your local workstat
 Host burst
   HostName burst.hpc.nyu.edu
   User <NetID>
-  ProxyJump <NetID>@torch.hpc.nyu.edu
+  ProxyJump <NetID>@login.torch.hpc.nyu.edu
   ProxyJump <NetID>@burst.hpc.nyu.edu
   StrictHostKeyChecking no
   UserKnownHostsFile /dev/null

docs/hpc/02_connecting_to_hpc/01_connecting_to_hpc.md

@@ -16,7 +16,7 @@ The following sections will outline basic ways to connect to the Greene cluster.
 
 To connect to HPC systems, you have to configure the SSH client on your machine. We recommend the following configuration:
 ```sh
-Host torch.hpc.nyu.edu dtn.hpc.nyu.edu
+Host dtn.hpc.nyu.edu
   User <NetID>
   StrictHostKeyChecking no
   ServerAliveInterval 60
@@ -60,7 +60,7 @@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
 Someone could be eavesdropping on you right now (man-in-the-middle attack)!
 It is also possible that a host key has just been changed.
 ```
-Do not be alarmed - this is an issue that occurs because the Greene and Torch clusters have multiple login nodes. For instance, `torch.hpc.nyu.edu` resolves to one of three possible login nodes (`log-1`, `log-2`, and `log-3`). The configuration directive `StrictHostKeyChecking no` referenced in the recommended config above will prevent this error. Ensure that you have not missed adding it.
+Do not be alarmed - this is an issue that occurs because the Greene and Torch clusters have multiple login nodes. For instance, `login.torch.hpc.nyu.edu` resolves to one of three possible login nodes (`log-1`, `log-2`, and `log-3`). The configuration directive `StrictHostKeyChecking no` referenced in the recommended config above will prevent this error. Ensure that you have not missed adding it.
 :::
 
 :::info SSH Timeout errors
@@ -81,7 +81,7 @@ To access the HPC systems, you must either be on the NYU secure network (such as
 Once you're on the VPN or the main NYU network on campus you can SSH directly to torch like so:
 
 ```sh
-ssh <Your NetID>@torch.hpc.nyu.edu
+ssh <Your NetID>@login.torch.hpc.nyu.edu
 ```
 
 ### Windows

docs/hpc/02_connecting_to_hpc/02_x11_forwarding.md

@@ -5,7 +5,7 @@
 In rare cases when you need to interact with GUI applications on HPC clusters, you need to enable X11 forwarding for your SSH connection. Mac and Linux users will need to run the ssh commands described above with an additional flag:
 
 ```sh
-ssh -Y <NYU_NetID>@torch.hpc.nyu.edu
+ssh -Y <NYU_NetID>@login.torch.hpc.nyu.edu
 ```
 
 However, Mac users need to install [XQuartz][xquartz], since X-server is no longer shipped with the macOS.

docs/hpc/12_tutorial_intro_shell_hpc/02_connecting_to_hpc.mdx

@@ -38,7 +38,7 @@ From within the NYU network, that is, from an on-campus location, or after you V
 
 To log in to the HPC cluster (Greene), simply use:
 ```bash
-ssh <NetID>@torch.hpc.nyu.edu
+ssh <NetID>@login.torch.hpc.nyu.edu
 ```
 
 ### From Windows
@@ -58,7 +58,7 @@ There are many different versions (aka “flavours”) of Linux and how to open
 Open a terminal application and enter the following to connect to one of the HPC clusters:
 ```bash
 # this will connect you to Greene HPC cluster
-ssh <NetID>@torch.hpc.nyu.edu
+ssh <NetID>@login.torch.hpc.nyu.edu
 ```
 
 ### Mac
@@ -67,7 +67,7 @@ Macs have had a terminal built in since the first version of OS X, since it is b
 Open a terminal application and enter the following to connect to Greene:
 ```bash
 # this will connect you to Greene HPC cluster
-ssh <NetID>@torch.hpc.nyu.edu
+ssh <NetID>@login.torch.hpc.nyu.edu
 ```
 
 ### Windows
@@ -227,7 +227,7 @@ If you are using PuTTY on Windows, download and use `pageant` as the SSH agent.
 ## Modifying your .ssh/config file
 Please add the following lines to your `~/.ssh/config` file:
 ```
-Host torch.hpc.nyu.edu dtn.hpc.nyu.edu
+Host login.torch.hpc.nyu.edu dtn.hpc.nyu.edu
   StrictHostKeyChecking no
   ServerAliveInterval 60
   ForwardAgent yes
@@ -257,14 +257,14 @@ Let’s attempt to connect to the HPC system now:
 
 If you'd like to connect without typing your password you'll need to copy your public key file to torch first:
 ```bash
-scp ~/.ssh/id_Greene_rsa.pub <NetID>@torch.hpc.nyu.edu:/home/<NetID>
+scp ~/.ssh/id_Greene_rsa.pub <NetID>@login.torch.hpc.nyu.edu:/home/<NetID>
 ```
 
 You'll need to log in with your password at least once even if you plan to use SSH keys in the future because we'll need to set up your keys.
 
 Once you are on the NYU WiFi or VPN you can connect with:
 ```bash
-ssh <NetID>@torch.hpc.nyu.edu
+ssh <NetID>@login.torch.hpc.nyu.edu
 ```
 
 When you are logged in you will see information about your last login, the host you've connected to, and your storage quota.  It should look something like this:

docs/hpc/13_tutorial_intro_hpc/03_exploring_remote_resources.mdx

@@ -16,7 +16,7 @@ Objectives
 ## Look Around the Remote System
 If you have not already connected to Greene, please do so now:
 ```bash
-[user@laptop ~]$  ssh NetID@torch.hpc.nyu.edu
+[user@laptop ~]$  ssh NetID@login.torch.hpc.nyu.edu
 ```
 Take a look at your home directory on the remote system:
 ```bash
@@ -196,7 +196,7 @@ Now compare the resources of your computer with those of the login node. <br />
 </summary>
 :::tip[Solution]
 ```bash
-[user@laptop ~]$ ssh NetID@torch.hpc.nyu.edu
+[user@laptop ~]$ ssh NetID@login.torch.hpc.nyu.edu
 [NetID@log-1 ~]$ nproc --all
 [NetID@log-1 ~]$ free -m
 ```

docs/hpc/13_tutorial_intro_hpc/07_transferring_files_remote.mdx

@@ -151,19 +151,19 @@ To copy a single file to or from the cluster, we can use `scp` (“secure copy
 
 To *upload* to another computer, the template command is
 ```bash
-[user@laptop ~]$ scp local_file NetID@torch.hpc.nyu.edu:remote_destination
+[user@laptop ~]$ scp local_file NetID@login.torch.hpc.nyu.edu:remote_destination
 ```
 in which `@` and `:` are field separators and `remote_destination` is a path relative to your remote home directory, or a new filename if you wish to change it, or both a relative path *and* a new filename. If you don’t have a specific folder in mind you can omit the `remote_destination` and the file will be copied to your home directory on the remote computer (with its original name). If you include a `remote_destination`, note that `scp` interprets this the same way `cp` does when making local copies: if it exists and is a folder, the file is copied inside the folder; if it exists and is a file, the file is overwritten with the contents of `local_file`; if it does not exist, it is assumed to be a destination filename for `local_file`.
 
 Upload the lesson material to your remote home directory like so:
 ```bash
-[user@laptop ~]$ scp amdahl.tar.gz NetID@torch.hpc.nyu.edu:
+[user@laptop ~]$ scp amdahl.tar.gz NetID@login.torch.hpc.nyu.edu:
 ```
 
 ## Transferring a Directory
 To transfer an entire directory, we add the `-r` flag for “recursive”: copy the item specified, and every item below it, and every item below those… until it reaches the bottom of the directory tree rooted at the folder name you provided.
 ```bash
-[user@laptop ~]$ scp -r amdahl NetID@torch.hpc.nyu.edu:
+[user@laptop ~]$ scp -r amdahl NetID@login.torch.hpc.nyu.edu:
 ```
 :::warning[Caution]
 For a large directory – either in size or number of files – copying with `-r` can take a long time to complete.
@@ -182,7 +182,7 @@ As you gain experience with transferring files, you may find the `scp` command l
 
 The syntax is similar to `scp`. To transfer to another computer with commonly used options:
 ```bash
-[user@laptop ~]$ rsync -avP amdahl.tar.gz NetID@torch.hpc.nyu.edu:
+[user@laptop ~]$ rsync -avP amdahl.tar.gz NetID@login.torch.hpc.nyu.edu:
 ```
 The options are:
 -   `-a` (archive) to preserve file timestamps, permissions, and folders, among other things; implies recursion
@@ -191,13 +191,13 @@ The options are:
 
 To recursively copy a directory, we can use the same options:
 ```bash
-[user@laptop ~]$ rsync -avP amdahl NetID@torch.hpc.nyu.edu:~/
+[user@laptop ~]$ rsync -avP amdahl NetID@login.torch.hpc.nyu.edu:~/
 ```
 As written, this will place the local directory and its contents under your home directory on the remote system. If a trailing slash is added to the source, a new directory corresponding to the transferred directory will not be created, and the contents of the source directory will be copied directly into the destination directory.
 
 To download a file, we simply change the source and destination:
 ```bash
-[user@laptop ~]$ rsync -avP NetID@torch.hpc.nyu.edu:amdahl ./
+[user@laptop ~]$ rsync -avP NetID@login.torch.hpc.nyu.edu:amdahl ./
 ```
 :::
 
@@ -208,7 +208,7 @@ File transfers using both `scp` and `rsync` use SSH to encrypt data sent through
 :::info[Change the Rsync Port]
 Say we have to connect `rsync` through port 768 instead of 22. How would we modify this command?
 ```bash
-[user@laptop ~]$ rsync amdahl.tar.gz NetID@torch.hpc.nyu.edu:
+[user@laptop ~]$ rsync amdahl.tar.gz NetID@login.torch.hpc.nyu.edu:
 ```
 Hint: check the `man` page or “help” for `rsync`. <br />
 **[Click for Solution]**
@@ -220,7 +220,7 @@ Hint: check the `man` page or “help” for `rsync`. <br />
 [user@laptop ~]$ rsync --help | grep port
      --port=PORT             specify double-colon alternate port number
 See http://rsync.samba.org/ for updates, bug reports, and answers
-[user@laptop ~]$ rsync --port=768 amdahl.tar.gz NetID@torch.hpc.nyu.edu:
+[user@laptop ~]$ rsync --port=768 amdahl.tar.gz NetID@login.torch.hpc.nyu.edu:
 ```
 :::note
 This command will fail, as the correct port in this case is the default: 22.
@@ -235,7 +235,7 @@ Download and install the FileZilla client from [https://filezilla-project.org](h
 
 To connect to the cluster, we’ll just need to enter our credentials at the top of the screen:
 
--   Host: `sftp://torch.hpc.nyu.edu`
+-   Host: `sftp://login.torch.hpc.nyu.edu`
 -   User: Your NetID
 -   Password: Your NetID password
 -   Port: (leave blank to use the default port)
@@ -275,25 +275,25 @@ If you are transferring large amounts of data you will need to think about what
 
 Say you have a “data” folder containing 10,000 or so files, a healthy mix of small and large ASCII and binary data. Which of the following would be the best way to transfer them to Greene?
 ```bash
-[user@laptop ~]$ scp -r data NYUNetID@torch.hpc.nyu.edu:~/
+[user@laptop ~]$ scp -r data NYUNetID@login.torch.hpc.nyu.edu:~/
 ```
 ```bash
-[user@laptop ~]$ rsync -ra data NYUNetID@torch.hpc.nyu.edu:~/
+[user@laptop ~]$ rsync -ra data NYUNetID@login.torch.hpc.nyu.edu:~/
 ```
 ```bash
-[user@laptop ~]$ rsync -raz data NYUNetID@torch.hpc.nyu.edu:~/
+[user@laptop ~]$ rsync -raz data NYUNetID@login.torch.hpc.nyu.edu:~/
 ```
 ```bash
 [user@laptop ~]$ tar -cvf data.tar data
 ```
 ```bash
-[user@laptop ~]$ rsync -raz data.tar NYUNetID@torch.hpc.nyu.edu:~/
+[user@laptop ~]$ rsync -raz data.tar NYUNetID@login.torch.hpc.nyu.edu:~/
 ```
 ```bash
 [user@laptop ~]$ tar -cvzf data.tar.gz data
 ```
 ```bash
-[user@laptop ~]$ rsync -ra data.tar.gz NYUNetID@torch.hpc.nyu.edu:~/
+[user@laptop ~]$ rsync -ra data.tar.gz NYUNetID@login.torch.hpc.nyu.edu:~/
 ```
 **[Click for Solution]**
 :::

docs/hpc/13_tutorial_intro_hpc/08_running_parallel_job.mdx

@@ -17,7 +17,7 @@ We now have the tools we need to run a multi-processor job. This is a very impor
 
 If you disconnected, log back in to the cluster.
 ```bash
-[user@laptop ~]$ ssh NetID@torch.hpc.nyu.edu
+[user@laptop ~]$ ssh NetID@login.torch.hpc.nyu.edu
 ```
 
 ## Install the Amdahl Program