Release Notes

2.9.0

Whats new

  • Iris enablement of spaces

  • Iris Single Sign On (SSO)

  • External service support for Postgres, RabbitMQ and Redis

  • Ngenea Core 1.32 support

What you need to know

  • The configuration value LDAP_MIRROR_GROUPS is no longer json loaded, please consult the LDAP documentation for more details.

  • The configuration value “celery_broker” will be automatically replaced with BROKER_PROVIDER and RESULTS_PROVIDER on first hub startup.

  • Any configuration file older than version 2.9.0 will be backed up with this upgrade

  • SSO and LDAP cannot be enabled simultaneously, please consult the LDAP and Single Sign-On documentation for more details.

  • SSO is not enabled by default and must be configured and enabled, details for this process are in the Single Sign-On documentation.

What’s Fixed

  • Consult the changelog for individual fixes

2.8.1

What you need to know

  • Ngenea targets are no longer renamed on update, the new format is only applied to new targets

  • Ngenea Core 1.32 support has been added to targets

What’s Fixed

  • Consult the Changelog for individual fixes

2.8.0

What’s new

  • Iris beta (feature flagged)

  • Initial release of Programming Guide, with improved, user-friendly REST API documentation

What you need to know

  • API only workflows can now be selected when editing the Space Schedules and Schedule settings

  • Hub containers now auto-restart when encountering an issue which causes container shutdown

What’s Fixed

  • Consult the Changelog for individual fixes

2.7.0

What’s new

  • Spaces can now be viewed in table layout

  • Schedules are now specified relative to the site timezones rather than UTC+0

  • Site workflow batch size options to control workflow task processing performance

  • Policies support more file systems than mmfs1

  • Global settings now provides Timeout controls for Hub behaviours

  • API performance can be scaled with the new GUNICORN_THREADS setting

What you need to know

  • Where NAS user(s) and group(s) exist prior to additional sites being joined, automatic creation of existing NAS users and groups as part of setup on the new Site may fail if the Site is still undergoing joining. Should this occur, re-submit the failed ‘Creating NAS group’ and/or ‘Creating NAS user’ job after a few minutes.

What’s Fixed

  • Consult the Changelog for individual fixes