Skip to content

Latest commit

 

History

History
208 lines (154 loc) · 18.7 KB

UPGRADING.md

File metadata and controls

208 lines (154 loc) · 18.7 KB
Raw

Upgrading

This document summarizes the environmental changes that need to be made when upgrading IRIDA that cannot be automated.

20.05 to 20.09

20.01 to 20.05

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file.
  • This version changes the endpoint for creating sequencing runs to allow any type of sequencer. The legacy sequencingRun/miseq endpoint is maintained, but deprecated. See https://irida.corefacility.ca/documentation/developer/rest/#creating-sequencing-runs for more info.
  • Assemblies can now be uploaded to IRIDA rather than just created through an analysis pipeline. This requires a new filesystem directory configured for files to be stored. You must add assembly.file.base.directory to your /etc/irida/irida.conf file and create a new diretory for these files to be stored.

19.09 to 20.01

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file.
  • This upgrade changes the Java version to Java 11. To upgrade, follow the install instructions for your system in https://irida.corefacility.ca/documentation/administrator/web/#prerequisite-install-instructions.
  • Tomcat 8 (or another Servlet 3.1 compatible servlet container) is required for this IRIDA version. Systems using Tomcat 7 must be upgraded before deploying this update.
  • This upgrade adds a required field to OAuth2 clients using the authorization_code grant (that is external applications connecting to IRIDA via the web application). This includes other IRIDA installations synchronizing data via the Remote API system, and Galaxy importer clients. In order for these systems to continue working properly, administrators must register a redirect URI for all authorization_code clients. For more on this process, see https://irida.corefacility.ca/documentation/administrator/upgrades/#2001.
  • The configuration key hibernate.dialect=org.hibernate.dialect.MySQL55Dialect should be set in your /etc/irida/irida.conf file for this release. Note the change from MySQL5Dialect to MySQL55Dialect.

19.05 to 19.09

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file.

19.01 to 19.05

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file.
  • This upgrade will remove FastQC resuts from the database and move them to the file system. It is strongly recommended to make a backup of your database before this upgrade. Before upgrading you should read more at https://irida.corefacility.ca/documentation/administrator/upgrades/#1905.

19.01 to 19.01.2

  • A new configuration value is available to control the number of threads used for communication with Galaxy when running pipelines. The default value is 4. To change, please set irida.workflow.analysis.threads in the /etc/irida/irida.conf file. This can help when running lots of pipelines in IRIDA.

0.22.0 to 19.01

0.21.0 to 0.22.0

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file.

  • This upgrade changes the way the file processors handle uploaded files. File processing now takes place as a scheduled task rather than immediately after files are uploaded. For deployments with multiple IRIDA servers running against the same database, prossing may not be performed by the IRIDA server the files were uploaded to and will instead be balanced among all the available servers. If you want to disable file processing on an IRIDA server, set the following property in /etc/irida/irida.conf : file.processing.process=false.

  • A new pipeline, bio_hansel, has been included. You will have to make sure to install the necessary Galaxy tools listed in the documentation.

  • The MentaLiST pipeline has been ugpraded. Please make sure to install the necessary tools in Galaxy.

  • The SISTR pipeline has been upgraded to make use of shovill for assembly. Please make sure to install the shovill Galaxy tool. Also, please make sure to follow the additional instructions in https://irida.corefacility.ca/documentation/administrator/galaxy/pipelines/sistr/#address-shovill-related-issues, which involves some modifications of the conda environment for shovill. In particular, you must:

    1. Install the proper ncurses and bzip2 packages from the conda-forge channel.

      # activate the Galaxy shovill conda env
source galaxy/deps/_conda/bin/activate galaxy/deps/_conda/envs/[email protected]
# install ncurses and bzip2 from conda-forge channel
conda install -c conda-forge ncurses bzip2

    2. Set the SHOVILL_RAM environment variable in the conda environment:

      cd galaxy/deps/_conda/envs/[email protected]
mkdir -p etc/conda/activate.d
mkdir -p etc/conda/deactivate.d

echo -e "export _OLD_SHOVILL_RAM=\$SHOVILL_RAM\nexport SHOVILL_RAM=8" >> etc/conda/activate.d/shovill-ram.sh
echo -e "export SHOVILL_RAM=\$_OLD_SHOVILL_RAM" >> etc/conda/deactivate.d/shovill-ram.sh

      Please change 8GB to what works for you for shovill (or setup based on the $GALAXY_MEMORY_MB environment variable, see the linked instructions for more details).

0.20.0 to 0.21.0

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file.
  • Two new pipelines, refseq_masher and MentaLiST, are included with this release. Additional Galaxy tools will need to be installed. Please see the linked installation details for each pipeline for more information.

0.19.0 to 0.20.0

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file.
  • This upgrade removes Dandelion framework from IRIDA. -Ddandelion.profile.active=prod" should be removed from Tomcat settings. Please see https://irida.corefacility.ca/documentation/administrator/web/#servlet-container-configuration.
  • You may configure the number of days a password is valid for before it needs reset. Add the security.password.expiry key to /etc/irida/irida.conf to configure. To disable password expiry, set to -1 (default). For example to set to 90 days, add the following:
security.password.expiry=90

0.18.0 to 0.19.0

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file.
  • Any custom pipelines developed should follow the new Analysis scheme. An Analysis subclass is no longer required (but may be used) for custom pipelines, but an AnalysisType entry is required. See developer docs for more information.

0.17.0 to 0.18.0

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file.

0.16.0 to 0.17.0

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file. Note this upgrade removes a number of deprecated database tables such as remote_related_proejct and remote_sequence_file. While these tables were likely empty it is strongly recommended you back up your database before this upgrade.
  • Remove snapshot.file.base.directory entry from /etc/irida/irida.conf. This directory is no longer used. If the directory pointed to by this config entry is empty it may be safely removed.
  • The SISTR pipeline has been upgraded to use sistr_cmd 1.0.2. This new version must be installed in Galaxy. Please see http://irida.corefacility.ca/documentation/administrator/galaxy/pipelines/sistr/.

0.15.0 to 0.16.0

0.14.0 to 0.15.0

0.13.0 to 0.14.0

  • This upgrade makes schema changes to the databases and cannot be parallel deployed. Servlet container must be stopped before deploying the new war file.

0.12.0 to 0.13.0

  • You may now configure the number of threads to be used for file processing on the web server. These threads perform tasks such as unzipping files and running FastQC. The following configuration keys can be set in /etc/irida/irida.conf (default values displayed):

      file.processing.core.size=4
  file.processing.max.size=8
  file.processing.queue.capacity=512

  • Deploy the new war file.

0.11.0 to 0.12.0

1.0.0 to 0.11.0

  • No special upgrade steps required, just deploy the new war file.

1.0.0-alpha10 to 1.0.0

  • You may now configure the link and text that gets rendered on web pages under the 'Help' menu for accessing an external help forum. You can configure the link and text by adding some keys to /etc/irida/web.conf:

      help.page.title=Your Help Page Title
  help.page.url=http://www.example.org/help

    These are optional settings. If they are not configured, no link will appear in the 'Help' menu.

  • You may now configure the e-mail address that gets rendered on web pages under the 'Help' menu. You can configure the e-mail address by adding a key to /etc/irida/web.conf:

      [email protected]

    This is an optional setting. If it is not configured, no 'Contact Us' e-mail address will appear in the 'Help' menu.

  • Deploy the new war file.

1.0.0-alpha9 to 1.0.0-alpha10

  • No special upgrade steps required, just deploy the new war file.

1.0.0-alpha8 to 1.0.0-alpha9

  • No special upgrade steps required, just deploy the new war file.

1.0.0-alpha8 to 1.0.0-alpha8.2

  • Add irida.scheduled.threads key to /etc/irida/irida.conf file with the size of your desired thread pool. Suggested size is 2.

1.0.0-alpha7 to 1.0.0-alpha8

1.0.0-alpha6 to 1.0.0-alpha7

1.0.0-alpha5 to 1.0.0-alpha6

  • No special upgrade steps required, just deploy the new war file.

1.0.0-alpha4 to 1.0.0-alpha5

  • A new version of SNVPhyl should be installed in Galaxy, you must install a new tool repository suite_snvphyl with revision 99463e5aef1b from the IRIDA Main Toolshed. Please see https://irida.corefacility.ca/documentation/administrator/galaxy/pipelines/phylogenomics/#irida-whole-genome-phylogenomics for more information.

  • You can configure the location of the announcements file by adding a key to /etc/irida/irida.conf with the name updates.file with a value of the location of the Markdown formatted file that will be displayed. The user running your serlvet container must be able to read this file. Example:

      updates.file=/etc/irida/announcments.md

  • Administrator notifications for filesystem errors during file uploads in the web interface can be configured by adding a key to /etc/irida/irida.conf with the name irida.administrative.notifications.email with a value of the e-mail address to which notifications can be sent. Notifications are sent when the IRIDA-managed filesystem is in an inconsistent state (trying to write over files that already exist), when there is no disk space left on the volume to which the files are written, or when some other, unknown filesystem-related exception takes place. Example:

      [email protected]

  • The schedule for sending out project digest e-mails is defaulted to be once per day at midnight. You can customize the frequency for the digest notifications by adding a key to /etc/irida/irida.conf with the name irida.scheduled.subscription.cron with a value of a cron-like expression. Please see http://docs.spring.io/spring/docs/4.0.6.RELEASE/javadoc-api/org/springframework/scheduling/annotation/Scheduled.html#cron-- for the format of the expression. Example:

      # send e-mails weekly (on Sunday at midnight) instead of daily
  irida.scheduled.subscription.cron=0 0 0 * * 0

1.0.0-alpha3 to 1.0.0-alpha4

  • No special upgrade steps required, just deploy the new war file.