Multi host upgrades

This article provides steps for upgrading multi-host TeamForge Orchestrate installations to the latest release.

The following steps pertain to TeamForge Orchestrate upgrades when all services are located on multiple hosts. Upon successful completion, TeamForge Orchestrate will be upgraded to the latest available release.
Important: The upgrade process stops the TeamForge Orchestrate App server while upgrading. Anticipate up to 20 minutes of end-user downtime from the time services are shutdown.

Download upgrade_collabnet-orchestrate-16.3.sh

  1. To gain access to the TeamForge Orchestrate upgrade script upgrade_collabnet-orchestrate-16.3.sh, contact CollabNet Support at https://www.collab.net/support/secure-customer-login
  2. Once Support has given you access, download upgrade_collabnet-orchestrate-16.3.sh from https://ctf.open.collab.net/sf/sfmain/do/viewProject/projects.sfdl
  3. Copy upgrade_collabnet-orchestrate-16.3.sh to /tmp on each host in question and change directories to that location.

    cp upgrade_collabnet-orchestrate-16.3.sh /tmp cd /tmp chmod 755 upgrade_collabnet-orchestrate-16.3.sh

Back up the TeamForge Orchestrate system

  1. Before upgrading, backup TeamForge Orchestrate system and data, see Backup and Restore

Disconnected media

  1. If you are using "disconnected media" to upgrade, follow the steps in Upgrading without internet access. Otherwise continue with the MongoDB section below.
    Important: It is imperative that MongoDB and RabbitMQ be upgraded before the Orchestrate service to avoid potential data loss due to downed services. Please proceed in the order prescribed below.

Upgrade MongoDB - Before upgrading MongoDB, to prevent unintentional data loss, it is important that you shutdown the services running on the App server.

  1. Log into the host running the TeamForge Orchestrate application (App server) with a privileged account.
  2. Shutdown the "orchestrate" service, see System Administration.

    sudo service orchestrate stop

    Note: The TeamForge Orchestrate web interface will be unavailable to end-users until after the upgrade process. RabbitMQ will remain up though, collecting and queuing data from sources.
  3. Log into the host running MongoDB (DB server) with a privileged account.
  4. Perform upgrade by running upgrade_collabnet-orchestrate-16.3.sh, passing the mongodb flag.

    sudo ./upgrade_collabnet-orchestrate-16.3.sh mongodb

    Upon success, MongoDB will be automatically restarted.

  5. You may restart the Orchestrate services on the App server at this time, or continue to the RabbitMQ section.

    sudo service orchestrate start

Upgrade RabbitMQ

  1. Log into the host running RabbitMQ (MQ server) with a privileged account.
  2. Perform upgrade by running upgrade_collabnet-orchestrate-16.3.sh, passing the rabbitmq flag.

    sudo ./upgrade_collabnet-orchestrate-16.3.sh rabbitmq

    Upon success, RabbitMQ will be automatically restarted.

Upgrade TeamForge Orchestrate

  1. Log into the host running the TeamForge Orchestrate application (App server) with a privileged account.
  2. Perform upgrade by running upgrade_collabnet-orchestrate-16.3.sh, passing the orchestrate flag.

    sudo ./upgrade_collabnet-orchestrate-16.3.sh orchestrate

    Upon success, Orchestrate services will be restarted automatically.

  3. Verify that all services are running after upgrade_collabnet-orchestrate-16.3.sh terminates

    The upgrade script should display a list of all services with [OK] denoting a successful restart.

Parent topic: Upgrading TeamForge Orchestrate