v2.2.1 Upgrade Notes

Configuration Changes

Container Image Versions

Replace docker-compose.yml with new version from release folder.

Update container versions in .env to v2.2.1.

Move PostgreSQL Database to Separate Service

From version 2.2.1, MOPS 4.0 will no longer use the container-based PostgreSQL database. Instead, it will run using a separately installed database server. Follow the instruction in note MD-1960 below to perform the migration.

Directory Database

You should run the update script for the directory database. This will add the changes from MD-1290 and ensure that inherited permissions gets applied correctly.

See Upgrade Directory Database - Step 3.

Upgrade Notes

[MD-1960] Adjust MOPS 4.0 Setup to run PostgreSQL as Windows Service

Following versions of MOPS 4.0 will no longer use the container based PostgreSQL database.

  1. Start the migration process by first performing a backup of the current database. The backup will later be imported to the service-based database.

  2. Follow the installation instructions for installing PostgreSQL. Remember the assigned port and the password for the “postgres” user. After a new separate database has been created, we can migrate from the container database to the service based database.

  3. Import the exported database on the newly created database server.

  4. Shut down the system and change the configuration files that contain connection details to the previous database with new and correct information.

  5. Update affected configuration files. Services and their config files affected by database connection details are:

    • mops-dir: mops-dir.config
    • keycloak: keycloak.conf
    • mops-cms-alertmgr: db-config.json
    • mops-cms-conditionmonitor: db-config.json

    Update database connection details in the above mentioned configuration files to point to the new database server. This includes hostname, port, database name, username and password.

  6. Start the system and verify that all services are running as expected. Check the logs for any errors related to database connection issues.

[MD-2009] Infoscreen Caches the index file

In addition to replacing docker-compose.yml during upgrade, a new middleware needs to be added to “middlewares” section of rules.yml (Ingress configuration file). Example can be found in <installation-package>/templates/conf/ingress/rules.yml