Skip to content

Release notes for version 21.10.1#

Nextflow Tower 21.10.x brings the following changes:

  • Add Container registry creds for Azure
  • Add Datasets feature
  • Add Support custom CE environment variables
  • New Workflows Runs list page
  • Add support for custom landing page
  • Add Display job info on workflow general panel (#2142) (#2151)
  • Make hidden params a part of pipeline input form even if not shown + small fix (#2134)
  • Parallelize Az metadata retrieval
  • Fix Make hidden params a part of pipeline input form even if not shown + small fix (#2134)
  • Fix Validate final values of config properties on startup (#2100)
  • Fix redisson default connection pool size (#2229)
  • Fix Return a bad request when workspaceId is not parsable (#2220) (#2205)
  • Fix race condition on repo pull (#2110)
  • Fix grid platform default launch dir (#2037)
  • Fix Redirect to the Runs page after launch (#2057)
  • Fix Discard deleted entities from name validation queries and rename them (#2052)
  • Improve landing page config (#1996) (#748)
  • Fix Download hangs when streaming a S3 file (#2005)
  • Hide ebsBlockSize field from aws manual config (#2004)
  • Refactor Google LifeScience head job execution (#1981)
  • Make sure to authenticate the Google storage (#1984)
  • Use amazoncorretto:11.0.13 as base image
  • Minor schema fetching improvement (#2183)
  • Make sure the workflows list query returns the workflows in a workspace even if they have been starred by other users (#2174)
  • Bump nf-launcher 21.10.4

Updating Tower deployment from version 21.06.x to 21.10.x#

If you are upgrading from a version prior to 21.06.x, update your installation to tower 21.04.0, before installing this release.

License key#

As of version 21.02.x, a license key must be provided to enable the Tower deployment feature. The license key should be specified using the configuration variable TOWER_LICENSE. If you don't have a license key, contact sales@seqera.io.

Compute environments#

The Tower compute environments to be made available to users must be specified in the Tower configuration.

The following options are available:

  • awsbatch-platform: AWS Batch cloud compute service
  • gls-platform: Google LifeSciences cloud compute service
  • azbatch-platform: Azure Batch cloud compute service
  • lsf-platform: IBM LSF batch scheduler
  • slurm-platform: Slurm batch scheduler
  • altair-platform: Altair PBS Pro batch scheduler
  • univa-platform: (Univa/Sun) GridEngine
  • k8s-platform: Kubernetes compute platform
  • eks-platform: AWS EKS compute platform
  • gke-platform: Google GKE compute platform

Database schema#

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

Docker compose deployment#

1. Make a backup of the Tower database.

2. Update the docker-compose.yml file with the following container images:

1
2
195996028523.dkr.ecr.eu-west-1.amazonaws.com/nf-tower-enterprise/backend:v21.10.3
195996028523.dkr.ecr.eu-west-1.amazonaws.com/nf-tower-enterprise/frontend:v21.10.3

If you are using AWS Batch with a custom launcher job definition you need to update it to use the following container images (please refer the configuration section for details):

1
public.ecr.aws/seqera-labs/tower/nf-launcher:21.10.5

3. Restart the service using the command docker-compose restart.

Kubernetes based deployment#

1. Make a backup of the Tower database.

2. 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:v21.10.3
195996028523.dkr.ecr.eu-west-1.amazonaws.com/nf-tower-enterprise/frontend:v21.10.3

If you are using AWS Batch with a custom launcher job definition you need to update it to use the following container image (please refer the configuration section for details):

1
public.ecr.aws/seqera-labs/tower/nf-launcher:21.10.5

Refer to the manifests included in the K8s instalation section for details.

3. Update the Tower cron service using the following:

1
kubectl apply -f tower-cron.yml

Note

This task will automatically run the Tower database schema update tool.

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

1
kubectl apply -f tower-svc.yml

Custom deployment script#

1. Make a backup of the Tower database.

2. 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:v21.10.3
195996028523.dkr.ecr.eu-west-1.amazonaws.com/nf-tower-enterprise/frontend:v21.10.3

If you are using AWS Batch with a custom launcher job definition you need to update it to use the following container image (please refer the configuration section for details):

1
public.ecr.aws/seqera-labs/tower/nf-launcher:21.10.5

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

Note

Make sure to include the identical environment as used in the normal backend execution.

4. Once the schema update completes, deploy Tower following your usual procedure.

Back to top