We do not want a local storage server to start by default (but this should be modifiable via a config option of some sort) if the version of its backend database does not match the "current" version.
(The problem is we do not have this "current" version easily available from python)
Q: should this only prevent a storage RPC server from starting, or should it prevent a local storage object from being instantiated?
| rDSTO Storage manager | |||
| D3834 | rDSTO4532a4dc64e7 Add a --check-config option for cli commands | ||
| D3832 | rDSTOcc33dd359692 Add support for a new "check_config" config option in get_storage() | ||
| D3814 | rDSTOc16ff506ad52 Add a check_dbversion() method to the Db class | ||
| D3814 | rDSTO629d2d10ee97 Fix pytest_plugin's database janitor: do not truncate the dbversion table | ||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T2524 Storage database migration tooling | ||
| Migrated | gitlab-migration | T2525 Prevent the storage server from starting in case of db version mismatch |
Just to make is clear, my main objective here is to have a seatbelt for the mirror scenario: prevent a mirror with updated code but not-yet-updated database from even running until the DB migration script has been executed.