Here is user experience feed-back of our upgrade from knora api v6 to v8.
I don’t know how much effort should be dedicated to this because we are the only one of such users (aren’t we?), and specifically, nobody else will ever make this exercise of upgrading a production set-up from v6. I was even sceptical about the usefulness of writing this, but there might be some of the issues that will hit back at any upgrade.
Not knowing how long it takes and what will be necessary to fix problems, I don’t only back-up the data, but execute the upgrades on a clone. It is the only reasonable way, imho. So we might write it in the documentation.
auto-update starts from v7
The page Release Notes/Migration Notes should be deleted; it is outdated and having found such a page is misleading because one will not look for more as the actual information that is on Deploying Knora/Updating Repositories When Upgrading Knora.
The two pages should be merged.
Also, it would be nice to have the doc for v8.1.0 (knora.org is on v8.0.0), alright, there was no v8.1.0 official tag, anyway, v9.0.0 is out.
Some passwords were lost during the run of the upgrade scripts.
Strict consistency checker
Consistency checker is made more strict and existing data might not comply anymore, this kind of problem won’t be fixed by a script (which is not there to invent data) but a checker would be helpful.
One might object that the test is there: when we import and when we start knora.
Importing a big trig file is long, when it fails for a couple of lines it is frustrating to start over.
When knora fails on a graph, it stops, so on problematic project can stop the whole set-up and all of the projects.
The script ran fine until uploading the final trig file to graphdb, it failed on a
Uploading the file directly worked though.
code and architecture upgrade
v8 saw some other changes either in the behaviour of the process or in the way they interact (sipi needs a
test.html, knora checks on sipi, there is a redis cache that is not optional).
Nothing bad but discovered on the way as a trial and error process.
To avoid people (just me for now) feeling miserable, we should add a section to the documentation Deploying Knora describing a recommended way to set-up the knora ecosystem and how to upgrade from one version to the next one.
Again, it doesn’t make sense to catch back the history as nobody else than us (Basel and Lausanne) installed it so far. And it might not make sense if we end-up all on the same infrastructure on switch.
But having a section “Updating Repositories When Upgrading Knora” without another one saying “How to upgrade a Knora set-up” lacks some legitimacy.