...
- ecflow_ui ↔ ECMWF ecFlow servers
- ecflow_ui ↔ ECMWF logservers (but see the "Limitations" section)
Start your SSH tunnel
Using 'user1' login name as an example, please replace with your own username used at ECMWF. Here I wish to connect to ECMWF 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
...
To access 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). You also need to 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 |
Configure your ecflow_ui
Next, configure the connection settings for the two ecflow servers in your ecflow_ui. Make sure you use "localhost" in "Host" fields, not the actual ECMWF hostnames.
If you need your ecflow_ui to connect to a logserver at ECMWF, you will also need to att "127.0.0.1 logserver" alias in /etc/hosts on your laptop, so that connections from your ecflow_ui to logserver actually go to localhost.
Limitations of Local Port Forwarding
...
In practice we can only connect to a single remote log server. This is because different log servers at the Centre use the same port number (9316).
Method 2: Dynamic Port Forwarding
...