openBIS Server Upgrade

Documentation
1

Hi,
would it be possible to place the “Installtion Upgrade” at a more pronounced or even stand-alone place in the documentation?

E.g. if one searches for “upgrade” https://openbis.readthedocs.io, the actual task how to upgrade the openbis server is not coming up.

Thank you in anticipation

Best regards

Kristian

2

Dear @KristianUllrich,
we did not really think about writing specifically the upgrade downgrade procedure as technically it is matter of organization of your setup.
The upgrade is running desired version configured with production database and data store.
Standalone installation is described here
https://openbis.readthedocs.io/en/latest/system-documentation/standalone/index.html

Our standalone setup is organized with folders per release wher all of them are identically configured.

drwxrwxr-x  4 openbis openbis 4096 Jun 25 12:14 openbis-20.10.6
drwxrwxr-x  4 openbis openbis 4096 Jul  1 13:17 openbis-20.10.7
drwxrwxr-x  4 openbis openbis 4096 Jul  5 12:11 openbis-20.10.8
drwxrwxr-x  4 openbis openbis 4096 Jul 24 12:26 openbis-20.10.9

And we run release of choise by decion which is started.

I believe it is clearer in the case of Docker based setup.
We describe it here
https://openbis.readthedocs.io/en/latest/system-documentation/docker/usage.html

The upgrade is to change the “openbis/openbis-app:20.10.7;” to “openbis/openbis-app:20.10.8;” and restart the container and downgrade is to change the “openbis/openbis-app:20.10.8;” to “openbis/openbis-app:20.10.7;”.

https://openbis.readthedocs.io/en/latest/system-documentation/docker/index.html

3

Dear @artur.pedziwilk,
since a lot of users have setup and upgraded openbis before the docker version had the status to be used as “production”. In older openbis versions, the docker solution was specifically assigned as only testing and to use a system install as “production”.

I am just asking for a single bullet point in the documentation, which is not availabe here: Standalone — Python documentation

e.g.: Upgrade standalone openbis:

  1. download latest openbis here (Production Releases - openbis - Confluence)
  2. move into openbis/servers directory (mv openBIS-installation-standard-technologies-20.10.XXX.tar.gz /openbis/servers)
  3. Stop running instance (openbis/bin/alldown.sh)
  4. Upgrade (openbis/bin/upgrade.sh)
  5. Start instance (openbis/bin/allup.sh)

Thank you in anticipation

Best regards

Kristian

4

Hi Kristian, Hi Artur,

I would like to make a contribution here so that other people can learn from my experiences.
The original upgrade procedure via upgrade.sh has not gone so smoothly for me at least twice in the past and needed to be improved. In a production system with growing user numbers, I became more cautious and we stayed at 20.10.8 for a long time.
I would have liked to have seen the advice mentioned by Artur to do the installations side by side in the home directory earlier, but it has now motivated us to upgrade to 20.10.11.1 by installing them in parallel in /home/openbis/openbis-20.10.11.1, which worked perfectly.
We saved the list of files from the neighboring thread (How to upgrade a running installation?) and copied them into the new installation.
Unfortunately, it was only a few days later that we noticed that the inline images in the MULTILINE_VARCHAR fields were no longer being loaded.
Other than the data in the DataStore those are stored in the application folder /home/openbis/openbis-20.10.11.1/data/file-server and therefore have to be moved alongside the afromentioned files.

If there is a better way to handle the storage of inline images, I would be glad to have that mentioned elsewhere.

Greetings,
Volker