Release Notes - Yoda v1.10

Version: 1.10

Released: 11 October 2024

What’s new

Major changes

Support for Ubuntu 20.04 LTS
Support for multiple deposit groups
Support for landing page themes
Added an administration page so that functional administration tasks can be performed via the portal
Added a data transfer page, with ready-to-use configurations for data transfer tools
Removed RADIUS fallback option
Removed Secured status from research space
Improved reliability of the data package archiving process (“copy to vault”)
Improved support for vault archiving workflow
Improved performance of the portal
Upgrade python-irodsclient to v2.1.0

Known issues

Collections with single apex “’” in the name do not work irods/irods#5727
Deadlock in msiDataObjRepl & msiDataObjCopy when called from Python irods_rule_engine_plugin_python#54

Upgrading from previous release

The playbook requires Ansible 2.11.x or higher. Ansible 2.17.0 and higher is not yet supported.

Version constraints:

Requires Yoda external user service to be on version 1.9.x or higher.
Requires Yoda public server to be on version 1.9.x or higher.

Configuration changes:

Yoda 1.10 blocks remote access to the anonymous account via the iRODS protocol by default. If you run DavRODS on a different server from the provider, you need to add its network address to the irods_anonymous_account_permit_addresses configuration parameter.

Backup/copy custom configurations made to Yoda version 1.9. To view what files were changed from the defaults, run git diff.
After making sure the configurations are stored safely in another folder, reset the Yoda folder using git stash or when you want to delete all changes made: git reset --hard.
Check out tag v1.10.0 of the Yoda Git repository.
```
git checkout v1.10.0
```
Set the Yoda version to v1.10.0 in the configuration.
```
yoda_version: v1.10.0
```

Install all Ansible collections needed to deploy Yoda:

ansible-galaxy collection install -r requirements.yml

Run the Ansible playbook in check mode.

ansible-playbook -i <path-to-your-environment> playbook.yml --check
### EXAMPLE ###
ansible-playbook -i /environments/development/allinone playbook.yml --check

If the playbook has finished successfully in check mode, run the Ansible playbook normally.

ansible-playbook -i <path-to-your-environment> playbook.yml
### EXAMPLE ###
ansible-playbook -i /environments/development/allinone playbook.yml

Update publication endpoints if there are published packages (DataCite, landingpages and OAI-PMH):

irule -r irods_rule_engine_plugin-irods_rule_language-instance -F /etc/irods/yoda-ruleset/tools/update-publications.r