Skip to content

Update Process

Jump to bottom
Tom Mitchell edited this page May 31, 2017 · 8 revisions

Overview

This page covers the update process. There are also pages for testing and for creating a release.

  1. Schedule Update
  2. Update
  3. Notify Others

Schedule Update

  1. Check the GMOC Calendar for conflicts

  2. Email GMOC notifying them that we intend to use our maintenance window

    • Include the GMOC ticket number from the appropriate maintenance event on the GMOC calendar (see above)
    • Include the phrase "please notify GENI-Ops. This outage affects GENI experimenters, so please also notify experimenter-ops@grnoc.iu.edu." in the email so a notification goes to the response team email list

  3. Invoke maintenance mode on the portal to display a message about the upcoming maintenance window

    sudo geni-manage-maintenance --set-alert \
     "The GENI Portal and Clearinghouse will be down for maintenance on Wednesday, September 11, 2016 at 2:00 p.m. UTC"

Update

  1. Set maintenance mode on the portal to prevent users from accessing the portal & clearinghouse during upgrade

    sudo geni-manage-maintenance --set-outage \
     "31-May-2017 2:00 p.m. UTC: The GENI Portal is down for scheduled maintenance."
sudo geni-manage-maintenance --clear-alert

  2. Snapshot the host so that it can be rolled back if problems are encountered

  3. Perform any pre-update steps (e.g. OS & similar updates)

  4. Install the software via RPM

    N.B. The link in the example below may not be the latest RPM. You can find the URL of the latest RPM at https://github.com/GENI-NSF/geni-portal/releases/latest

    sudo yum install -y \
     https://github.com/GENI-NSF/geni-portal/releases/download/v3.24/geni-portal-3.24-1.el7.centos.noarch.rpm

  5. Apply any special changes listed in the CHANGES.md file

  6. Check logs for startup errors

    sudo geni-check-errors

sudo tail /var/log/apache2/portal_error.log

  7. Do basic testing

    • Focus on testing fixes and new features listed in CHANGES.md
    • Log in
    • View each tab
    • Optional: Edit project membership
    • Create a slice
    • Renew a slice
    • Optional: Edit slice membership
    • Add slice resources to a slice with multiple members
    • Get sliver status
      • Hit 'Get Details'
      • Try to log in to the sliver using the SSH command presented
      • Look at the authorized keys file and the users who have accounts, to ensure it matches slice membership as expected
    • Delete sliver
    • Test external tools:
      • Wireless
      • iRODS
      • GENI Desktop (OpenID)
      • Map on home page
      • Map on slice page
    • Test Omni
      • Download an omni bundle
      • Run listmyslices

  8. If issues are encountered, roll back to snapshot

  9. Clear the outage maintenance mode

    sudo geni-manage-maintenance --clear-outage

Notify Others

  1. Email GMOC that maintenance is complete

  2. Notify the ORBIT Lab via problems@orbit-lab.org that the portal host was rebooted and they should remove cached OpenID nonces on by running the following command on their host:

     rm /tmp/mod_auth_openid.db
Clone this wiki locally