If ecIf you wish to use ecFlow to run your workloads, ECMWF will provide you with ready-to-go ecFlow server running on an independent Virtual Machine outside the HPCF. Those servers would take care of the orchestration of your workflow, while all tasks in your suites would actually be submitted and run on HPCF. With each machine being dedicated to one ecFlow server, there are no restrictions of cpu time and no possibility of interference with other users.
...
Code Block | ||||
---|---|---|---|---|
| ||||
edit QUEUE nf edit SCHOST aahpc edit ECF_JOB_CMD troika submit -o %ECF_JOBOUT% %SCHOST% %ECF_JOB% edit ECF_KILL_CMD troika kill %SCHOST% %ECF_JOB% edit ECF_STATUS_CMD troika monitor %SCHOST% %ECF_JOB% |
...
Code Block | ||||
---|---|---|---|---|
| ||||
edit QUEUE nf edit SCHOST aahpc edit TROIKA /path/to/bin/troika edit TROIKA_CONFIG /path/to/troika.yml edit ECF_JOB_CMD %TROIKA% -c %TROIKA_CONFIG% submit -o %ECF_JOBOUT% %SCHOST% %ECF_JOB% edit ECF_KILL_CMD %TROIKA% -c %TROIKA_CONFIG% kill %SCHOST% %ECF_JOB% edit ECF_STATUS_CMD %TROIKA% -c %TROIKA_CONFIG% monitor %SCHOST% %ECF_JOB% |
...
- Authenticate via Teleport on your End User device
Create the SSH tunnel with:
No Format ssh -N -L3141:localhost:3141 -J jump.ecmwf.int,aahpc-login <ecflow_host>
where the first '3141' is the local port. For example, if the server is started on the host ecflow-gen-user-001:
No Format ssh -N -L3141:localhost:3141 -J jump.ecmwf.int,aahpc-login ecflow-gen-user-001
- Open
ecflow_ui
on your End User Device and configure the new server, using "localhost
" as the host and the ecFlow (local) port used above.
...
You may also run ecflow_ui remotely on the Atos HPCF, and use X11 forwarding to display on your screen:
No Format |
---|
ssh -X aahpc-login module load ecflow ecflow_ui |
...