...
First make sure you connected to the Centre with teleport using your token id. On the MAC i had to use latest teleport version. (5.0.0)
Code Block title MAC brew install teleport # *OR* > brew upgrade teleport
Next setup port forwarding. Using 'user1' login name as an example, please replace with your own username used at ECMWF. Here I wish to connect to workstation hostname machine1 where I have a ecflow server running on port 4141, also wish to connect to host machine2 where I have a ecflow server running on port 3142
Code Block title Connect to workstation ecflow server and metabuilder ci server ssh -J user1@shell.ecmwf.int user1@machine1 -C -N -L 4141:machine1:4141 -L 3142:machine2:3142
Warning This command as shown will run in the foreground and will hang your terminal, but can be useful to see if the connection breaks for any reason
To access cca/ccb HPC job output via the log server , you need to create a tunnel access for this as well. Here we use 'logserver' as an example, replace this with your actual logserver
add '127.0.0.1 logserver' alias in /etc/hosts so that connections to 'logserver' actually go to localhost, then use
Code Block ssh -J user1@shell.ecmwf.int user1@machine1 -C -N -L 4141:machine1:4141 -L 3142:machine2:3142 -L 9316:logserver:9316
The next steps vary dependent on whether your username at ECMWF matches your local username on your MAC/PC and if ecflow server has a whitelist file.
Remote ecflow Server with NO whitelist file:
Where there is NO whitelist file you are connecting using your local username on the MAC. This can be seen by viewing the log output file
Remote ecflow Server with whitelist file:
There are 3 options:
1/ Create a login name on your local machine which matches your user name at ECMWF.
2/ Ask your ecflow server administrator to add your local username to the ecflow server whitelist file
3/ Ask your ecflow server administrator to setup a CUSTOM user, See: Security(custom user) this requires both client/server setup password based access. When this is done invoke ecflow_ui and use:
- Finally ensure you use "localhost" tunnel entrance for all remote ecflow server hostnames.
...