REANA-Client¶
REANA-Client is a component of the REANA reusable and reproducible research data analysis platform. It provides a command-line tool that allows researchers to submit, run, and manage their computational workflows.
- seed workspace with input code and data
- run computational workflows on remote compute clouds
- list submitted workflows and enquire about their statuses
- download results of finished workflows
Installation¶
$ # create new virtual environment
$ virtualenv ~/.virtualenvs/reana
$ source ~/.virtualenvs/reana/bin/activate
$ # install reana-client
$ pip install reana-client
Usage¶
The detailed information on how to install and use REANA can be found in docs.reana.io.
CLI API¶
Usage: reana-client [OPTIONS] COMMAND [ARGS]...
REANA client for interacting with REANA server.
Options:
-l, --loglevel [DEBUG|INFO|WARNING]
Sets log level
--help Show this message and exit.
Quota commands:
quota-show Show user quota.
Configuration commands:
ping Check connection to REANA server.
version Show version.
Workflow management commands:
create Create a new workflow.
delete Delete a workflow.
diff Show diff between two workflows.
list List all workflows and sessions.
Workflow execution commands:
logs Get workflow logs.
restart Restart previously run workflow.
run Shortcut to create, upload, start a new workflow.
start Start previously created workflow.
status Get status of a workflow.
stop Stop a running workflow.
validate Validate workflow specification file.
Workspace interactive commands:
close Close an interactive session.
open Open an interactive session inside the workspace.
Workspace file management commands:
download Download workspace files.
du Get workspace disk usage.
ls List workspace files.
mv Move files within workspace.
rm Delete files from workspace.
upload Upload files and directories to workspace.
Secret management commands:
secrets-add Add secrets from literal string or from file.
secrets-delete Delete user secrets by name.
secrets-list List user secrets.
reana-client¶
REANA client for interacting with REANA server.
reana-client [OPTIONS] COMMAND [ARGS]...
Options
-
-l
,
--loglevel
<loglevel>
¶ Sets log level
Options: DEBUG|INFO|WARNING
close¶
Close an interactive session.
The close command allows to shut down any interactive sessions that you may have running. You would typically use this command after you finished exploring data in the Jupyter notebook and after you have transferred any code created in your interactive session.
Examples:
$ reana-client close -w myanalysis.42
reana-client close [OPTIONS]
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
create¶
Create a new workflow.
The create command allows to create a new workflow from reana.yaml specifications file. The file is expected to be located in the current working directory, or supplied via command-line -f option, see examples below.
Examples:
$ reana-client create
$ reana-client create -w myanalysis
$ reana-client create -w myanalysis -f myreana.yaml
reana-client create [OPTIONS]
Options
-
-f
,
--file
<file>
¶ REANA specification file describing the workflow to execute. [default=reana.yaml]
-
-n
,
-w
,
--name
,
--workflow
<name>
¶ Optional name of the workflow. [default is “workflow”]
-
--skip-validation
¶
If set, specifications file is not validated before submitting it’s contents to REANA server.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
delete¶
Delete a workflow.
The delete command allows to remove workflow runs from the database and the workspace. By default, the command removes the workflow and all its cached information and hides the workflow from the workflow list. Note that workflow workspace will still be accessible until you use –include-workspace flag. Note also that you can remove all past runs of a workflow by specifying –include-all-runs flag.
Example:
$ reana-client delete -w myanalysis.42
$ reana-client delete -w myanalysis.42 –include-all-runs
$ reana-client delete -w myanalysis.42 –include-workspace
reana-client delete [OPTIONS]
Options
-
--include-all-runs
¶
Delete all runs of a given workflow.
-
--include-workspace
¶
Delete workspace from REANA.
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
diff¶
Show diff between two workflows.
The diff command allows to compare two workflows, the workflow_a and workflow_b, which must be provided as arguments. The output will show the difference in workflow run parameters, the generated files, the logs, etc.
Examples:
$ reana-client diff myanalysis.42 myotheranalysis.43
$ reana-client diff myanalysis.42 myotheranalysis.43 –brief
reana-client diff [OPTIONS] WORKFLOW_A WORKFLOW_B
Options
-
-q
,
--brief
¶
If not set, differences in the contents of the files in the two workspaces are shown.
-
-u
,
-U
,
--unified
<context_lines>
¶ Sets number of context lines for workspace diff output.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
Arguments
-
WORKFLOW_A
¶
Required argument
-
WORKFLOW_B
¶
Required argument
download¶
Download workspace files.
The download command allows to download workspace files. By default, the files specified in the workflow specification as outputs are downloaded. You can also specify the individual files you would like to download, see examples below. Note that downloading directories is not yet supported.
Examples:
$ reana-client download # download all output files
$ reana-client download mydata.tmp outputs/myplot.png
reana-client download [OPTIONS] FILES
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-o
,
--output-directory
<output_directory>
¶ Path to the directory where files will be downloaded.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
Arguments
-
FILES
¶
Optional argument(s)
du¶
Get workspace disk usage.
The du command allows to chech the disk usage of given workspace.
Examples:
$ reana-client du -w myanalysis.42 -s
$ reana-client du -w myanalysis.42 -s –human-readable
reana-client du [OPTIONS]
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
-
-s
,
--summarize
¶
Display total.
-
-h
,
--human-readable
¶
Show disk size in human readable format.
list¶
List all workflows and sessions.
The list command lists workflows and sessions. By default, the list of workflows is returned. If you would like to see the list of your open interactive sessions, you need to pass the –sessions command-line option.
Example:
$ reana-client list –all
$ reana-client list –sessions
$ reana-client list –verbose –bytes
reana-client list [OPTIONS]
Options
-
-s
,
--sessions
¶
List all open interactive sessions.
-
--format
<_format>
¶ Format output according to column titles or column values. Use <columm_name>=<column_value> format. E.g. display workflow with failed status and named test_workflow –format status=failed,name=test_workflow.
-
--json
¶
Get output in JSON format.
-
--all
¶
Show all workflows including deleted ones.
-
-v
,
--verbose
¶
Print out extra information: workflow id, user id, disk usage.
-
-h
,
--human-readable
¶
Show disk size in human readable format.
-
--sort
<sort_columm_name>
¶ Sort the output by specified column
-
--filter
<filters>
¶ Filter workflow that contains certain filtering criteria. Use –filter <columm_name>=<column_value> pairs. Available filters are name and status.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
-
--page
<page>
¶ Results page number (to be used with –size).
-
--size
<size>
¶ Size of results per page (to be used with –page).
logs¶
Get workflow logs.
The logs command allows to retrieve logs of running workflow. Note that only finished steps of the workflow are returned, the logs of the currently processed step is not returned until it is finished.
Examples:
$ reana-client logs -w myanalysis.42 $ reana-client logs -w myanalysis.42 -s 1st_step
reana-client logs [OPTIONS]
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
--json
¶
Get output in JSON format.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
-
--filter
<filters>
¶ Filter job logs to include only those steps that match certain filtering criteria. Use –filter name=value pairs. Available filters are compute_backend, docker_img, status and step.
-
--page
<page>
¶ Results page number (to be used with –size).
-
--size
<size>
¶ Size of results per page (to be used with –page).
ls¶
List workspace files.
The ls command lists workspace files of a workflow specified by the environment variable REANA_WORKON or provided as a command-line flag –workflow or -w.
Examples:
$ reana-client ls –workflow myanalysis.42
$ reana-client ls –workflow myanalysis.42 –human-readable
reana-client ls [OPTIONS]
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
--format
<_format>
¶ Format output according to column titles or column values. Use <column_name>=<column_value> format. For E.g. display FILES named data.txt –format name=data.txt.
-
--json
¶
Get output in JSON format.
-
--url
¶
Get URLs of output files.
-
-h
,
--human-readable
¶
Show disk size in human readable format.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
-
--page
<page>
¶ Results page number (to be used with –size).
-
--size
<size>
¶ Size of results per page (to be used with –page).
mv¶
Move files within workspace.
The mv command allow to move the files within workspace.
Examples:
$ reana-client mv data/input.txt input/input.txt
reana-client mv [OPTIONS] SOURCE TARGET
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
Arguments
-
SOURCE
¶
Required argument
-
TARGET
¶
Required argument
open¶
Open an interactive session inside the workspace.
The open command allows to open interactive session processes on top of the workflow workspace, such as Jupyter notebooks. This is useful to quickly inspect and analyse the produced files while the workflow is stlil running.
Examples:
$ reana-client open -w myanalysis.42 jupyter
reana-client open [OPTIONS] interactive-session-type
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-i
,
--image
<image>
¶ Docker image which will be used to spawn the interactive session. Overrides the default image for the selected type.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
Arguments
-
interactive-session-type
¶
Optional argument
ping¶
Check connection to REANA server.
The ping command allows to test connection to REANA server.
Examples:
$ reana-client ping
reana-client ping [OPTIONS]
Options
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
quota-show¶
Show user quota.
The quota-show command displays quota usage for the user.
Examples:
$ reana-client quota-show –resource disk –report limit
$ reana-client quota-show –resource disk –report usage
$ reana-client quota-show –resource disk
$ reana-client quota-show –resources
reana-client quota-show [OPTIONS]
Options
-
--resource
<resource>
¶ Specify quota resource. e.g. cpu, disk.
-
--resources
¶
Print available resources
-
--report
<report>
¶ Specify quota report type. e.g. limit, usage.
Options: limit|usage
-
-h
,
--human-readable
¶
Show disk size in human readable format.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
restart¶
Restart previously run workflow.
The restart command allows to restart a previous workflow on the same workspace.
Note that workflow restarting can be used in a combination with operational
options FROM
and TARGET
. You can also pass a modified workflow
specification with -f
or –file` flag.
You can furthermore use modified input prameters using -p or –parameters flag and by setting additional operational options using -o or –options. The input parameters and operational options can be repetitive.
Examples:
$ reana-client restart -w myanalysis.42 -p sleeptime=10 -p myparam=4
$ reana-client restart -w myanalysis.42 -p myparam=myvalue
$ reana-client restart -w myanalysis.42 -o TARGET=gendata
$ reana-client restart -w myanalysis.42 -o FROM=fitdata
reana-client restart [OPTIONS]
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
-
-p
,
--parameter
<parameters>
¶ Additional input parameters to override original ones from reana.yaml. E.g. -p myparam1=myval1 -p myparam2=myval2.
-
-o
,
--option
<options>
¶ Additional operational options for the workflow execution. E.g. CACHE=off. (workflow engine - serial) E.g. –debug (workflow engine - cwl)
-
-f
,
--file
<file>
¶ REANA specification file describing the workflow to execute. [default=reana.yaml]
rm¶
Delete files from workspace.
The rm command allow to delete files and directories from workspace. Note that you can use glob to remove similar files.
Examples:
$ reana-client rm -w myanalysis.42 data/mydata.csv
$ reana-client rm -w myanalysis.42 ‘code/*’
reana-client rm [OPTIONS] SOURCES
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
Arguments
-
SOURCES
¶
Optional argument(s)
run¶
Shortcut to create, upload, start a new workflow.
The run command allows to create a new workflow, upload its input files and start it in one command.
Examples:
$ reana-client run -w myanalysis-test-small -p myparam=mysmallvalue
$ reana-client run -w myanalysis-test-big -p myparam=mybigvalue
reana-client run [OPTIONS]
Options
-
-f
,
--file
<file>
¶ REANA specification file describing the workflow to execute. [default=reana.yaml]
-
-n
,
-w
,
--name
,
--workflow
<name>
¶ Optional name of the workflow. [default is “workflow”]
-
--skip-validation
¶
If set, specifications file is not validated before submitting it’s contents to REANA server.
-
-p
,
--parameter
<parameters>
¶ Additional input parameters to override original ones from reana.yaml. E.g. -p myparam1=myval1 -p myparam2=myval2.
-
-o
,
--option
<options>
¶ Additional operational options for the workflow execution. E.g. CACHE=off.
-
--follow
¶
If set, follows the execution of the workflow until termination.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
secrets-add¶
Add secrets from literal string or from file.
Examples:
$ reana-client secrets-add –env PASSWORD=password
$ reana-client secrets-add –file ~/.keytab
$ reana-client secrets-add –env USER=reanauser
–env PASSWORD=password
—file ~/.keytab
reana-client secrets-add [OPTIONS]
Options
-
--env
<env>
¶ Secrets to be uploaded from literal string.e.g. PASSWORD=password123
-
--file
<file>
¶ Secrets to be uploaded from file.
-
--overwrite
¶
Overwrite the secret if already present
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
secrets-delete¶
Delete user secrets by name.
Examples:
$ reana-client secrets-delete PASSWORD
reana-client secrets-delete [OPTIONS] [SECRETS]...
Options
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
Arguments
-
SECRETS
¶
Optional argument(s)
secrets-list¶
List user secrets.
Examples:
$ reana-client secrets-list
reana-client secrets-list [OPTIONS]
Options
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
start¶
Start previously created workflow.
The start command allows to start previously created workflow. The workflow execution can be further influenced by passing input prameters using -p or –parameters flag and by setting additional operational options using -o or –options. The input parameters and operational options can be repetitive. For example, to disable caching for the Serial workflow engine, you can set -o CACHE=off.
Examples:
$ reana-client start -w myanalysis.42 -p sleeptime=10 -p myparam=4
$ reana-client start -w myanalysis.42 -p myparam1=myvalue1 -o CACHE=off
reana-client start [OPTIONS]
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
-
-p
,
--parameter
<parameters>
¶ Additional input parameters to override original ones from reana.yaml. E.g. -p myparam1=myval1 -p myparam2=myval2.
-
-o
,
--option
<options>
¶ Additional operational options for the workflow execution. E.g. CACHE=off. (workflow engine - serial) E.g. –debug (workflow engine - cwl)
-
--follow
¶
If set, follows the execution of the workflow until termination.
status¶
Get status of a workflow.
The status command allow to retrieve status of a workflow. The status can be created, queued, running, failed, etc. You can increase verbosity or filter retrieved information by passing appropriate command-line options.
Examples:
$ reana-client status -w myanalysis.42
$ reana-client status -w myanalysis.42 -v –json
reana-client status [OPTIONS]
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
--format
<_format>
¶ Format output by displaying only certain columns. E.g. –format name,status.
-
--json
¶
Get output in JSON format.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
-
-v
,
--verbose
¶
Set status information verbosity.
stop¶
Stop a running workflow.
The stop command allows to hard-stop the running workflow process. Note that soft-stopping of the workflow is currently not supported. This command should be therefore used with care, only if you are absolutely sure that there is no point in continuing the running the workflow.
Example:
$ reana-client stop -w myanalysis.42 –force
reana-client stop [OPTIONS]
Options
-
--force
¶
Stop a workflow without waiting for jobs to finish.
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
upload¶
Upload files and directories to workspace.
The upload command allows to upload workflow input files and directories. The SOURCES argument can be repeated and specifies which files and directories are to be uploaded, see examples below. The default behaviour is to upload all input files and directories specified in the reana.yaml file.
Examples:
$ reana-client upload -w myanalysis.42
$ reana-client upload -w myanalysis.42 code/mycode.py
reana-client upload [OPTIONS] SOURCES
Options
-
-w
,
--workflow
<workflow>
¶ Name or UUID of the workflow. Overrides value of REANA_WORKON environment variable.
-
-t
,
--access-token
<access_token>
¶ Access token of the current user.
Arguments
-
SOURCES
¶
Optional argument(s)
validate¶
Validate workflow specification file.
The validate command allows to check syntax and validate the reana.yaml workflow specification file.
Examples:
$ reana-client validate -f reana.yaml
reana-client validate [OPTIONS]
Options
-
-f
,
--file
<file>
¶ REANA specification file describing the workflow to execute. [default=reana.yaml]
version¶
Show version.
The version command shows REANA client version.
Examples:
$ reana-client version
reana-client version [OPTIONS]
API docs¶
REANA REST API client.
-
reana_client.api.client.
create_workflow_from_json
(workflow_json, name, access_token, parameters=None, workflow_engine='yadage', outputs=None)[source]¶ Create a workflow from json specification.
Parameters: - workflow_json – workflow specification in json format.
- name – name or UUID of the workflow to be started.
- access_token – Access token of the current user.
- parameters – workflow input parameters dictionary.
- workflow_engine – one of the workflow engines (yadage, serial, cwl)
- outputs – dictionary with expected workflow outputs.
Example: create_workflow_from_json( workflow_json=workflow_json, name='workflow_name.1', access_token='access_token', parameters={'files': ['file.txt'], 'parameters': {'key': 'value'}}, workflow_engine='serial')
-
reana_client.api.client.
upload_file
(workflow_id, file_, file_name, access_token)[source]¶ Upload file to workflow workspace.
Parameters: - workflow_id – UID which identifies the workflow.
- file – content of a file that will be uploaded.
- file_name – name of a file that will be uploaded.
- access_token – access token of the current user.
-
reana_client.api.client.
start_workflow
(workflow, access_token, parameters)[source]¶ Start a workflow.
Parameters: - workflow – name or id of previously created workflow.
- access_token – access token of the current user.
- parameters – dict of workflow parameters to override the original ones (after workflow creation).
- restart – boolean if workflow should be restarted on the same workspace.
Changes¶
Version 0.8.0 (UNRELEASED)¶
- Adds new command
quota-show
. - Adds possibility to filter by workflow status and search by workflow name to
list
. - Changes
delete
to prevent workflow hard deletion. - Changes
list
to display interactive session status.
Version 0.7.2 (UNRELEASED)¶
- Adds support for Python 3.9.
- Fixes exception handling when uploading files.
- Fixes minor code warnings.
Version 0.7.1 (2020-11-10)¶
- Changes
ping
command output to include REANA client and server version information. - Fixes
upload
command to properly display errors.
Version 0.7.0 (2020-10-20)¶
- Adds option to
logs
command to filter job logs according to compute backend, docker image, status and step name. - Adds new
restart
command to restart previously run or failed workflows. - Adds possibility to specify operational options in the
reana.yaml
of the workflow. - Fixes user experience by preventing dots as part of the workflow name to avoid confusion with restart runs.
- Changes
du
command output format. - Changes file loading to optimise CLI performance.
- Changes
logs
command to enhance formatting using marks and colours. - Changes from Bravado to requests to improve download performance.
- Changes
ping
command to perform user access token validation. - Changes defaults to accept both
reana.yaml
andreana.yml
filenames. - Changes
diff
command to improve output formatting. - Changes code formatting to respect
black
coding style. - Changes documentation to single-page layout.
Version 0.6.1 (2020-06-09)¶
- Fixes installation troubles for REANA 0.6.x release series by pinning several dependencies.
Version 0.6.0 (2019-12-27)¶
- Introduces user secrets management commands
secrets-add
,secrets-list
andsecrets-delete
. - Enhances
run
andcreate
commands to allow specifying workfow via the--workflow
flag. - Introduces new command
version
to report client version. - Fixes
upload
command behaviour for uploading very large files. - Simplifies
run
command by removing free upload parameters. - Upgrades
cwltool
to 1.0.20191022103248. - Disables SSL verification warnings when talking to self-signed server certificates.
Version 0.5.0 (2019-04-24)¶
- Introduces new
resources
field inreana.yaml
specification file allowing to declare computing resources needed for workflow runs, such as the CVMFS repositories viacvmfs
subfield. - Improves
reana-client
embedded command-line documentation (-help
) by grouping commands and providing concrete usage examples for all commands. - Enhances workflow
start
command allowing to override input parameters (--parameter
) and to specify additional operational options (--option
). - Introduces new workflow
run
wrapper command that creates workflow, uploads its input data and code and starts its execution. - Introduces new workflow
stop
command for stopping a running workflow. - Enhances workflow
logs
command output capabilities via new--json
option. - Introduces new workflow
diff
command for comparing two workflow runs. - Introduces new workflow
delete
command for deleting one or more workflow runs. - Introduces new session
open
command allowing to run interactive sessions such as Jupyter notebook upon workflow workspace. - Introduces new session
close
command for closing interactive sessions. - Renames past
workflows
command tolist
allowing to list both workflow runs and interactive sessions. - Introduces new workspace
du
command for checking workspace disk usage. - Introduces new workspace
mv
command for moving files within workspace. - Introduces new workspace
rm
command for removing files within workspace. - Renames past workspace
list
command tols
allowing to list workspace files. Enhances its output capabilities via new--format
option. - Introduces new API function
create_workflow_from_json()
which allows developers and third-party systems to create workflows directly from JSON specification.
Version 0.4.0 (2018-11-07)¶
- Enhances test suite and increases code coverage.
- Changes license to MIT.
Version 0.3.1 (2018-09-25)¶
- Amends upload and download commands that will now upload/download all the
files specified in
reana.yaml
in case no arguments are provided. - Fixes
status
command’s JSON output mode. - Upgrades CWL reference implementation to version
1.0.20180912090223
. - Renames Serial workflow operational parameter from
CACHING``to ``CACHE
. - Adds support for Python 3.7.
Version 0.3.0 (2018-08-10)¶
- Adds support for Serial workflows.
- CLI refactored to a flat design:
inputs
/outputs
/code
removed, everything is a file managed with upload/download/list commands.- Removes
workflow
command, workflows are managed withcreate
/start
/status
.
- Removes
analyes
command, nowvalidate
is first level command. status
now shows the selected workflow progress and current command on verbose mode.- Requires the usage of an access token to talk to REANA Server.
- Fixes bug when uploading binary files.
- Supports addition of workflow engine parameters when using
start
for serial workflows. - Improves error messages.
Version 0.2.0 (2018-04-20)¶
- Adds support for Common Workflow Language workflows.
- Adds support for persistent user-selected workflow names.
- Enables file and directory input uploading using absolute paths.
- Adds new
status
command to display the current status of the client. - Reduces verbosity level for commands and improves error messages.
Version 0.1.0 (2018-01-30)¶
- Initial public release.
Please beware
Please note that REANA is in an early alpha stage of its development. The developer preview releases are meant for early adopters and testers. Please don’t rely on released versions for any production purposes yet.
Contributing¶
Bug reports, issues, feature requests, and other contributions are welcome. If you find a demonstrable problem that is caused by the REANA code, please:
- Search for already reported problems.
- Check if the issue has been fixed or is still reproducible on the latest master branch.
- Create an issue, ideally with a test case.
If you create a pull request fixing a bug or implementing a feature, you can run the tests to ensure that everything is operating correctly:
$ ./run-tests.sh
Each pull request should preserve or increase code coverage.
License¶
MIT License
Copyright (C) 2017-2020 CERN.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
In applying this license, CERN does not waive the privileges and immunities granted to it by virtue of its status as an Intergovernmental Organization or submit itself to any jurisdiction.
Authors¶
The list of contributors in alphabetical order: