...
| No Format |
|---|
module load ecflow ecflow_ui |
Through
...
a dynamic proxy
You may alternatively use the native ecflow_ui client in your Linux or Mac End User Device, but an additional step tool called proxychains is required to ensure connectivity between both ends. You will need .
On Mac, it can be installed using Homebrew with:
| No Format |
|---|
brew install proxychains-ng |
On Linux it should be available through your package manager.
| No Format |
|---|
# For Debian / Ubuntu
sudo apt install proxychains4
# For RHEL / Rocky
sudo dnf install proxychains-ng |
Then, follow these steps:
- Authenticate via Teleport on your End User device.
- Make sure you have the latest recommended ssh configuration as described in the documentation.
- Create the SOCKS dynamic proxy:
No Format ssh -N -D 9050 hpc-login - Start ecflow_ui on your End User device with the
-pc4option:No Format ecflow_ui -pc4
See the official ecFlow Documentation for more details.
| Info |
|---|
This method will allow you to connect to any ecflow and log servers as if the ecflowUI was running on the HPC itself. |
Through an SSH tunnel
An alternative method is to create an SSH tunnel, forwarding the port where the ecflow server is running. . Note that, unlike the dynamic proxy method above, it will only allow you to connect to one server, with no access to any other ecflow or log servers.
- Authenticate via Teleport on your End User device.
- Make sure you have the latest recommended ssh configuration
Create the SSH tunnel with:
No Format ssh -N -L3141:localhost:3141 -J jump.ecmwf.int,hpc-login <ecflow_host>where the first '3141' is the local port. For example, if the server is started on the host ecfg-user-1:
No Format ssh -N -L3141:localhost:3141 -J jump.ecmwf.int,hpc-login ecfg-user-1- Open
ecflow_uion your End User Device and configure the new server, using "localhost" as the host and the ecFlow (local) port used above.
...