Upgrade (updating)

Updated:2022-11-09

This section contains information about upgrading MAIA Software to a newer release.

Remember setting the path to MAIA web app installation directory : export PATH=/opt/data/t2maia/bin:$PATH

Steps

  1. Notify users about the upgrade.

  2. Disable the start of all pipelines transferring data to the MAIA web app, and wait for running pipelines to finish.

  3. Open a terminal window on the host where the MAIA web app is installed.

  4. backup of database???

  5. In the terminal window, go down to the file ~/Downloads and download the bsx-file from the path .

    cd ~/Downloads/bsx
    rm -rf *
    wget <path to bsx>/maia.iso.bsx
  6. Run the installation script for MAIA Software.

    sh maia.iso.bsx --loglevel DEBUG
  7. The upgrade process output is printed to the terminal window and to a log file.

TBD TBD TBD

  1. BLT_IPV_ROOT=/opt/blt_ipv /opt/blt_ipv/bin/install_gems /tmp/'selfextract.xxxxxx'/maia.iso

NOTE! The correct 'selfextract.xxxxxx' file name can be found at the beginning of the installation log output.

  1. Update MAIA agent on the host grit.

    ssh autobuild@grit.hq.t2data.com
    export PATH=/opt/t2data.com/maia_build_tools/bin:$PATH
    cd /opt/t2data.com/blt_ipv/setup
    git pull
    rm -rf .bundle Gemfile.lock
    bundle config --local path .bundle
    bundle install --full-index
  2. Follow the installation instructions in the installation log. Go back to normal operation mode by removing the maintenance.txt file. The exact path can be found in the instructions from the installation log output.

    rm /opt/data/t2maia/htdocs/maia/config/maintenance.txt
  3. Restart maia_core.

    MP
    ipv maia_core restart
  4. Go to Jenkins and re-enable all build pipelines.

  5. Send a slack message to maia_dev with information that the upgrade is complete. Send the following information: "maiadev has been upgraded to build_revision See delivery report delivery_report_label"

Install MAIA software on maiat2 and robot-maia
Prerequisites

Delivery reports have been created, go to section Create delivery reports for details.

Steps

Note! The steps below are to be repeated for each server installation, i.e once for maiat2.hq.t2data.com and once for robot-maia.hq.t2data.com

  1. Send a slack message to maia_dev with information about each MAIA software upgrade. Include information about how the maintenance mode will affect the users and an estimated timed of completion.

  2. Open a terminal window on your local host.

  3. Log in to the host where the MAIA software shall be installed.

  4. For maiat2:

    ssh maia@maiat2.hq.t2data.com
  5. For robot-maia:

    ssh maia@192.168.1.150
  6. Sync the tools

    pushd /opt/blt_ipv
    git pull
    popd
  7. In MAIA application, on the Main menu, go to Delivery reports, and click on the build label of the build you have delivered.

  8. In the Deliverables table, write down the path to artifact Bsx

  9. In the terminal window, go down to the file ~/Downloads and download the bsx-file from the path .

    cd ~/Downloads/bsx
    rm -rf *
    wget <path to bsx>/maia.iso.bsx
  10. Run the installation script for MAIA Software.

    sh maia.iso.bsx --loglevel DEBUG -t 0
  11. Follow the installation instructions in the installation log. Go back to normal operation mode by removing the maintenance.txt file. The exact path can be found in the instructions from the installation log output.

  12. Restart maia_core.

    MP
    ipv maia_core restart
  13. Send a slack message to maia_dev with information that the upgrade is complete.

  14. Send the following information: "maiat2/robot-maia has been upgraded to build_revision See delivery report delivery_report_label"

Step a build revision

  1. Open a terminal window on your local host.

  2. Go to the setup folder in the package blt_ipv.

    cd /opt/blt_ipv/setup
  3. Run the source_me.sh file

    source source_me.sh
  4. Go to the packages folder

    cd /opt/packages
  5. Identify the component_name that you want to step the build revision for.

  6. If the component is not present in the folder, check out the component with the MAIA agent command checkout.

    maia checkout -c component_name
  7. Note: If a getaddrinfo error occurrs, change the domain name of the maiadev host, maiadev.hq.t2data.com, to the ip-adress of the maiadev host, 192.168.1.129, in the maia_base.prod file

  8. Step into the component_name folder

    cd component_name
  9. Update the files in the folder

    git pull
  10. Go the the local_repository folder

    cd local_repository
  11. Open Makefile and step the revision

  12. Commit Makefile to Git

    git add Makefile
    git commit -m "commit_message"
    git push origin HEAD:refs/for/master
  13. Go to Gerrit.

  14. Verify that the commit passes the autobuild tests, and then ask a coworker to review your commit.

  15. When the commit is verified, submit the commit and wait for the commit to be scanned by MAIA application.