7526de2410
I have tested this upgrade on a held node going straight from 10.4 to 10.11 in one go. The resulting logs can be found in this paste [0]. The resulting backups of system tables are small enough that it seems reasonable to keep those enabled (though they can be disabled). Also, we can either land this change and let docker-compose do the upgrade for us, or we can put the host in the emergency file, do the upgrade by hand, then merge this change to reflect the new state of the world. One advantage to doing this by hand is that we can manually run a db backup with the service turned off to avoid any lost data between the time the upgrade occurs and the time of our last backup should anything go wrong. In either case we should probably double check that db backups look good in borg before proceeding. Comments on approach are very much welcome. [0] https://paste.opendev.org/show/bWhZZH97IMLv44eeiWlB/ Change-Id: I1bfcaeb9b90838a80d002732215f45a14a158fed |
||
|---|---|---|
| .. | ||
| defaults | ||
| files | ||
| handlers | ||
| tasks | ||
| templates | ||
| README.rst | ||
lodgeit
Paste service. Runs a mariadb container and lodgeit container.
** Role Variables **