...
- Review the release notes https://spaces.at.internet2.edu/display/Grouper/v2.6+Release+Notes and understand the upgrade process https://spaces.at.internet2.edu/display/Grouper/v2.6+Upgrade+Instructions+from+v2.6
- Check the current DDL version
- SSH into the container
- Connect to the backend DB via the container; if need be install postgresql
- Check the DDL version via this query: select * from grouper_ddl where object_name = 'Grouper';
- Ensure the DB version matches the container version via DDL in Grouper v2.5+
- Start GSH (we want to make sure there are no errors before we upgrade)
- Backup all of the configuration and post to Azure DevOps file repo
- Check that all daemons are green before upgrading
- Test all external systems
Do
This phase of the upgrade process actually upgrades the container image.
...
- Watch the Grouper Daemon Container image log stream to ensure it is pulling the updated container
- Perform any upgrade specific instructions as documented
- SSH into the container and run GSH to ensure there are no upgrades post error
- Check the DDL version as described above in the Plan phase to ensure the DB was indeed upgraded
- Assuming no errors, proceed with restarting the UI container
- Ensure that within the UI, under Configure the correct version of Grouper is shown
- Check daemon jobs to ensure they are all green (note it might take a while for them to turn green)
- Run a simple loader
- Run a simple provisioner
- Test all external systems
- Test anything specific to the release
- Backup all of the configuration files to Azure DevOps
...