Remote Access to INL-HPC
The following instructions are designed to users with access to INL HPC computing resources and operating from a machine outside of INL.
SSH Config
Edit the ~/.ssh/config file on your local machine to include the commands for proxy calls to internal INL sites.
ServerAliveInterval 240
Host *
ControlMaster auto
ControlPath ~/.ssh/master-%r@%h:%p
## HPC Entry Point
Host hpclogin hpclogin.inl.gov
Hostname hpclogin.inl.gov
DynamicForward 5555
## Forwarding
Host sawtooth1 sawtooth2 falcon1 falcon2 lemhi1 lemhi2 rod moosebuild.hpc.inl.gov hpcgitlab.hpc.inl.gov hpcsc.hpc.inl.gov
ProxyJump hpcloginIf your remote username is different from your local username you will need to add User directives in the appropriate places. See the instructions here.
ProxyJump directive fails?If your SSH client version is from before 2017. The ProxyJump command will not be recognized. Please upgrade your client, if possible. Otherwise, replace the ProxyJump directive with the following line:
ProxyCommand ssh -q -x hpclogin.inl.gov -W %h:%pSSH Tunnel
Create a tunnel into the HPC environment and leave it running while you require access to HPC resources (GitLab, MOOSE Build, etc). If you close this window, you will loose your connection to these resources.
ssh <your hpc user id>@hpcloginConnecting in this method requires an RSA PIN + Token. You should not need a fully-qualified domain name in your command above because of the "Host" setting in your SSH config file.
SOCKS Proxy
To access common HPC resources (hpcgitlab.hpc.inl.gov, hpcweb.inl.gov, etc) within a web browser, traffic must be routed through a SOCKS proxy. This can be achieved by using a PAC (Proxy-Auto Configuration) file:
// INL HPC PAC (Proxy-Auto Configuration)
//
// Used within the MOOSE HPC connectivity instructions
// (mooseframework.org/help/inl/hpc_remote.html)
// to tunnel traffic to common HPC resources
// using a SOCKS proxy to hpclogin.inl.gov.
// See the link for more information.
function FindProxyForURL(url, host) {
// For *.hpc.inl.gov, first attempt to use the SOCKS proxy.
// If no success, attempt a direct connection (useful when on the INL VPN)
if (dnsDomainIs(host, ".hpc.inl.gov"))
return "SOCKS5 localhost:5555; DIRECT";
// For all other domains, use direct access (no proxy)
return "DIRECT";
}Add the proxy configuration to your browser via the following url:
https://raw.githubusercontent.com/idaholab/moose/master/scripts/hpc_proxy.pacDocumentation is available for using Firefox. Add the URL above within the "Automatic proxy configuration URL" box. We do not recommend utilizing Google Chrome with this functionality because it requires setting a system-wide proxy configuration.
Log in to HPC Gitlab
Go to the following link: https://hpcgitlab.hpc.inl.gov Log in using your HPC id and password, not your RSA token or PIN.
SSH Keys
Create your SSH public/private key and install it on GitLab. Instructions for doing so can be found on GitLab itself at: https://hpcgitlab.hpc.inl.gov/help/ssh/README
Request Access
With now being able to connect to https://hpcgitlab.hpc.inl.gov, and having generated an SSH public/private key pair, please inform a project owner that you require access to their project.
Once you receive an email stating you have been added as a member of said project, you should then be able to create a Fork of that repository (using the https://hpcgitlab.hpc.inl.gov web site)
To clone the repository you just forked:
git clone git@hpcgitlab.hpc.inl.gov:<your user id>/<project>.gitView build status on MOOSEBuild
Using the same browser you modified your socks proxy settings, you should be able to navigate to https://moosebuild.hpc.inl.gov.