response to Hera ticket #376
Conversation
elisabethpatterson
requested review from
josh-eisinger and
chanwilson
as code owners
|
|
||
| In the steps below, replace First.Last with your own HPC username, and | ||
| XXXXX with the unique Local Port Number assigned to you when you log | ||
| in to your specified HPC system (Hera/Jet). Use the word "localhost" |
There was a problem hiding this comment.
Should we only be listing Hera & Jet when this is part of the main site FAQ?
There was a problem hiding this comment.
This was one of the concerns but leaving it too generic also can be problematic. I am ok with leaving it out. Alternatively we can do something like:
"... specified HPC system (Hera/Jet/etc)?
| Before you perform the first step, close all current sessions on the | ||
| HPC where system you are trying to connect. Once the first session has | ||
| been opened with port forwarding, any further connections (login via | ||
| ssh, copy via scp) will work as expected. You are running these |
There was a problem hiding this comment.
I'd recommend putting ssh and scp in double tick-marks so they appear as commands
| **1. Find your local port number** | ||
|
|
||
| To find your unique local port number, log onto your specified HPC | ||
| system (Hera/Jet). Make a note of this number - once you've recorded |
There was a problem hiding this comment.
Again, this is the primary site FAQ -- I don't think we should explicitly be referencing only Hera/Jet.
|
|
||
| .. code-block:: shell | ||
|
|
||
| ssh -m [email protected] -L1234e:localhost:12345 [email protected] |
There was a problem hiding this comment.
Should we be putting an explicit hera reference here? Or can we follow similar logic to the https://docs.rdhpcs.noaa.gov/connecting/index.html page (and possibly link to the https://docs.rdhpcs.noaa.gov/connecting/index.html#bastion-hostnames table?)
|
|
||
| .. code-block:: shell | ||
|
|
||
| ssh -L12345:localhost:12345 [email protected] |
There was a problem hiding this comment.
Again, explicit hera reference.
|
|
||
| .. code-block:: shell | ||
|
|
||
| ssh -X -L12345:localhost:12345 [email protected] |
| Note that objects emphasized in this figure should be unique to your | ||
| configuration: | ||
|
|
||
| .. image:: /images/linux_xfer2.png |
There was a problem hiding this comment.
This image has a "real" user name (Nikki.Ivie) -- should probably be First.Last (and maybe just do a code snippet rather than an image?)
| **Local Client Window #2** | ||
|
|
||
| Once the session is open, you can use this forwarded port | ||
| for data transfers, as long as this ssh window is kept open. After the |
There was a problem hiding this comment.
That 2nd sentence is also a repeat from earlier. Do we need it again here?
| **Configuration** | ||
|
|
||
| Enter host information to configure an SSH Terminal Session. The | ||
| example below defines a session to Jet via the Boulder Bastion: |
There was a problem hiding this comment.
The image doesn't actually show a Jet connection -- it has a blank host name.
|
|
||
| * Find and record your Local Host number. | ||
|
|
||
| .. image:: /images/linux_xfer1.png |
There was a problem hiding this comment.
This is duplicated from above. Can we restructure this so we don't have repeated info?
|
Superceeded by #386 and #LFS-1 |
This is the first step in a fix to the Port Tunnelling instructions. This PR adds a small item. Second step will be to move a block of text from here to the Connections section.