Test NSO 4.x to NSO 5.x migration - automatically compact CDB on NSO 5 startup?
Can we with the base image herein provided upgrade from NSO 4 to NSO 5?
NSO 5 wants to compact the database when it notices it was written from a NSO 4 node. In the past (when NSO 5 was still beta), this was a manual step. Is it still? Add a test!
If it needs to be done "manually", i.e. ncs doesn't do it by itself, we can add it to the run-nso.sh script so the docker container still automatically runs it. What happens when we run compact on an already compacted database? Do we risk delaying startup? AFAIK compaction happens naturally when NSO is running, so starting NSO in most cases works just fine and then NSO can compact it while running. That's preferable since we don't want to delay the startup for most cases.
Can we somehow query CDB to know whether it needs to be compacted before start?