Multi host upgrades

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

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

Update the EventQ installation yum repository

  1. Configure your TeamForge installation repository.
    • TeamForge installation repository configuration for sites with internet access
    1. Contact the CollabNet Support and download the TeamForge 17.11.xx installation repository package to /tmp.
    2. Install the repository package.
      • yum install -y /tmp/collabnet-teamforge-repo-17.11.xx-1.noarch.rpm
    3. Refresh your repository cache.
      • yum clean all
    • TeamForge installation repository configuration for sites without internet access
    1. Contact the CollabNet Support to get the auxiliary installer package for TeamForge 17.11.xx disconnected installation and save it in /tmp.
      • Red Hat Enterprise Linux/CentOS 7.4 64 bit RPM package: CTF-Disconnected-media-17.11.501-841.rhel7.x86_64.rpm
        Note: In addition to the above CentOS 7.4 64 bit RPM package, you must get the following CentOS 7.4 compatibility RPM, which is required for TeamForge 17.11.xx disconnected media installation on CentOS 7.4 profile: compat-ctf-dc-media-1.0-1.el7.centos.noarch.rpm.
    2. Unpack the disconnected installation package.
      • rpm -Uvh <package-name>
    3. Unpack the compat-ctf-dc-media-1.0-1.el7.centos.noarch.rpm package if you are installing TeamForge 17.11.xx on CentOS 7.4.
      • rpm -ivh compat-ctf-dc-media-1.0-1.el7.centos.noarch.rpm
    4. Note: If the Red Hat Enterprise Linux/CentOS installation DVD is mounted already, skip the following instructions. If not, mount the DVD.
      Mount the Red Hat Enterprise Linux/CentOS installation DVD. The DVD contains the necessary software and utilities required for installing TeamForge without internet access.

      In the following commands, replace "cdrom" with the identifier for your server's CD/DVD drive, if necessary.

      • cd /media/
      • mkdir cdrom
      • mount /dev/cdrom ./cdrom/

      If there are any spaces in the automount, unmount it first and mount it as a filepath, with no spaces.

    5. Create a yum configuration file that points to the Red Hat Enterprise Linux/CentOS installation DVD.
      • vi /etc/yum.repos.d/cdrom.repo
      Here's a sample yum configuration file.
      [RHEL-CDROM] 
name=RHEL CDRom 			
baseurl=file:///media/cdrom/Server/
gpgfile=file:///media/cdrom/RPM-GPG-KEY-redhat-release 
enabled=1
gpgcheck=0
    6. Verify your yum configuration files.
      • yum list httpd
      • yum list apr
  2. Once the yum repository is configured, update the EventQ RPM.
    • yum update CN-eventq
  3. Copy the /opt/collabnet/eventq/bin/upgrade-eventq-17.11.xx.sh file to the /tmp directory on the MongoDB and RabbitMQ servers.
    • scp /opt/collabnet/eventq/bin/upgrade-eventq-17.11.xx.sh username@newbox:/tmp
    Tip: scp is just an example. You can choose any file transfer method you prefer.

Back up the TeamForge EventQ system

  1. Before upgrading, backup TeamForge EventQ system and data, see Back up and restore EventQ data
    Important: It is imperative that MongoDB and RabbitMQ be upgraded before the EventQ 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 EventQ application (App server) with a privileged account.
  2. Shutdown the "eventq" service, see EventQ System Administration.

    sudo service eventq stop

    Attention:
    • Assuming that the App server is not upgraded yet, you may have to use the sudo service orchestrate stop command if you are upgrading from TeamForge 16.3 or earlier versions to TeamForge 16.7 and later.
    • The TeamForge EventQ 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-eventq-17.11.sh, passing the mongodb flag.

    /tmp/upgrade-eventq-17.11.sh mongodb

    Upon success, MongoDB will be automatically restarted.

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

    sudo service eventq start

    Attention: Assuming that the App server is not upgraded yet, you may have to use the sudo service orchestrate start command if you are upgrading from TeamForge 16.3 or earlier versions to TeamForge 16.7 and later.

Upgrade RabbitMQ

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

    /tmp/upgrade-eventq-17.11.sh rabbitmq

    Upon success, RabbitMQ will be automatically restarted.

Upgrade TeamForge EventQ

  1. Log into the host running the TeamForge EventQ application (App server) with a privileged account.
  2. Perform upgrade by running upgrade-eventq-17.11.sh, passing the eventq flag.

    /opt/collabnet/eventq/bin/upgrade-eventq-17.11.sh eventq

    Upon success, EventQ services will be restarted automatically.

  3. Verify that all services are running after upgrade-eventq-17.11.sh terminates.

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