REANA 0.9.0 makes it easy to enable Kerberos authentication for an entire workflow orchestration. This can be useful when the workflow decides on its computational steps depending on the number of input files located on an external restricted file system.

We are happy to announce REANA 0.9.0, a major update that allows users to set custom workflow retention rules to automatically delete workspace files, adds a new way of launching workflows from external sources, and more!

It can be useful to be able to keep some files in your workflow’s workspace only for a limited period of time, for example if your workflow generates huge temporary files that consume your disk quota. It is always possible to remove any unnecessary workspace files manually, but it may be quite a tedious process. Therefore, we are introducing the possibility to define custom workspace file retention rules to allow fully automated deletion of unnecessary files inside workspaces.

The usual way of creating, executing and managing REANA workflows is by means of the reana-client command-line tool. However, installing reana-client can be painful in certain situations, for example when it conflicts with your other Python project dependencies and you don’t want to be switching Python virtual environments all the time. In these cases, using a fully standalone reana-client executable would be desirable.

If you host your analysis workflows on publicly accessible external sources such as source code repositories (GitHub, GitLab), digital repositories (Zenodo), or simply other locations on the web (generic URL), it is now possible to launch your workflows directly on the web using the brand new REANA launcher web page.