Learn about database upgrade testing and other things
Discussion items
Time
Item
Who
Notes
5
Welcome
Ingolf
Find a note taker
Question about the lack of documentation for running FOLIO while not using containers.
The Docker files actually show how to build each module. Not really. They are all abstracted away making assumptions about Jenkins and others. The actual files exist in Git for each module. Jo has Jenkins running and trying to feed configurations into it. Jason stated docker allows one to ignore all this.
Core team responsible for this documentation. Ingolf will discuss with Jakub.
Jo is worried about a Docker installation failing and the entire system goes down.
Database upgrade testing
TAMU team: TAMU in-place upgrade, round #2
Round 1 during Q4 upgrade (in place migration) failed. The code was not tested. Jason figured out where and logged defects.
Round 2 for licenses and agreements scripts work. But other modules don't.
Jason will add tickets and John Melconian are getting back to the dev teams responsible for the upgrade scripts. The scripts don't leave the system in a good and stable state. Not recoverable. No log of what went wrong. No exception handling. What completed and what didn't is unknown.
There is no way to roll back. It fails badly. Not acceptable.
Rollback is a requirement
One can clone and test before placing in production, but we still need a graceful exist. Not sure a full rollback is reasonable at this time during the project.
System / database backup strategies
Ingolf
Outstanding charges of the SIG
Ingolf
Create an architectural diagram
Missing documentation of the container images on hub.docker.com/u/folioci
Ingolf
Old software versions in the installation documentation; causing potential security vulnerabilities