Release notes for version 20.10

Highlights#

Tower 20.10.x introduces support for:

• Add Workflow sharing feature
• Add support for Slurm batch cluster
• Add support for IBM LSF batch cluster
• Add customizable navbar menu
• Add built-in support for MariaDB
• Add built-in support for Google SSO
• Add auth allow-list emails
• Update Java mail 1.6.2
• System security improvements

Updating Tower deployment from version 20.08.x to 20.10.x#

Compute environments#

It is now required to define the Compute environments that are to be available to users in the Tower configuration.

The following ids options are available:

• awsbatch-platform: AWS Batch cloud compute service
• gls-platform: Google LifeSciences cloud compute service
• lsf-platform: IBM LSF batch scheduler
• slurm-platform: Slurm batch scheduler

Choose one or more of these platform ids and append to your current MICRONAUT_ENVIRONMENTS variable, separating them via a comma.

Database schema#

This Tower version requires a database schema update. Follow these steps to update your DB instance and the Tower installation.

Kubernetes based deployment#

1. Update the Tower container images in the Kubernetes manifest yaml files to:

1
2

195996028523.dkr.ecr.eu-west-1.amazonaws.com/nf-tower-enterprise/backend:v20.10.2 195996028523.dkr.ecr.eu-west-1.amazonaws.com/nf-tower-enterprise/frontend:v20.10.2

Refer to the manifests included in the Kubernetes section for details.

2. Update the Tower cron service using the following:

1

kubectl apply -f tower-cron.yml

3. Update the Tower backend and frontend services using the following command:

1

kubectl apply -f tower-svc.yml

Custom deployment script#

1. Pull or update the Tower container images references in your deployment script(s) to:

1
2

195996028523.dkr.ecr.eu-west-1.amazonaws.com/nf-tower-enterprise/backend:v20.10.2 195996028523.dkr.ecr.eu-west-1.amazonaws.com/nf-tower-enterprise/frontend:v20.10.2

2. Update the Tower database schema by running the /migrate-db.sh provided in the backend container.

3. Once the schema update completes, deploy Tower according to the usual procedure.