You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reana-client info command returns various useful information about various "minor" REANA features and configurations of the given connected deployment:
$ reana-client infoList of supported compute backends: kubernetesDefault timeout for Kubernetes jobs: 604800Default memory limit for Kubernetes jobs: 4GiDefault workspace: /var/reanaMaximum allowed memory limit for Kubernetes jobs: NoneMaximum inactivity period in days before automatic closure of interactive sessions: NoneMaximum timeout for Kubernetes jobs: 1209600Maximum retention period in days for workspace files: NoneList of available workspaces: /var/reana
However, we don't print out explicitly the version of CWL, Snakemake, Yadage workflows that the server supports.
This was not fully required up to now because CWL/Snakemake/Yadage functionality was "embedded" in the (thick) client, so that workflow validation was run on the client-side, and if the workflow created by the user was not compatible with the supported version, the users were informed locally even before the client reached out to the REANA server for processing.
Expected behaviour
With the forthcoming move of the workflow creation and validation functionality to the server side, the REANA client will remain "thin" and won't contain "inner knowledge" about the supported workflow versions anymore.
Hence it would be useful to enrich the reana-client info command output to return prominently the information about supported worfklow languages and their versions.
Beware of additional packages that would be useful to let users know, for example for CWL we may want to specify that we are using cwltool implementation, for Snakemake we may want to specify which plugins are supported on the server (such as XRootD 0.1.4), for Yadage we may want to specify what are the Adage (0.11.0) and Packtivity (0.16.2) versions. So it may be necessary to print out more "rows" for each given workflow language that the server supports.
The text was updated successfully, but these errors were encountered:
Alputer
added a commit
to Alputer/reana-server
that referenced
this issue
Nov 5, 2024
Current behaviour
The
reana-client info
command returns various useful information about various "minor" REANA features and configurations of the given connected deployment:However, we don't print out explicitly the version of CWL, Snakemake, Yadage workflows that the server supports.
This was not fully required up to now because CWL/Snakemake/Yadage functionality was "embedded" in the (thick) client, so that workflow validation was run on the client-side, and if the workflow created by the user was not compatible with the supported version, the users were informed locally even before the client reached out to the REANA server for processing.
Expected behaviour
With the forthcoming move of the workflow creation and validation functionality to the server side, the REANA client will remain "thin" and won't contain "inner knowledge" about the supported workflow versions anymore.
Hence it would be useful to enrich the
reana-client info
command output to return prominently the information about supported worfklow languages and their versions.For example:
Notes
Beware of additional packages that would be useful to let users know, for example for CWL we may want to specify that we are using
cwltool
implementation, for Snakemake we may want to specify which plugins are supported on the server (such as XRootD 0.1.4), for Yadage we may want to specify what are the Adage (0.11.0) and Packtivity (0.16.2) versions. So it may be necessary to print out more "rows" for each given workflow language that the server supports.The text was updated successfully, but these errors were encountered: