Date: Thu, 28 Mar 2024 06:55:05 -0500 (CDT) Message-ID: <700008506.122.1711626905282@os-confluence.ncsa.illinois.edu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_121_1361144907.1711626905281" ------=_Part_121_1361144907.1711626905281 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page describes how to upgrade the Clowder software. The ste= ps described will do an in-place upgrade of clowder. The biggest advantage = of this upgrade is that it is fast and requires the least amount of changes= to the current system.
Read about the new version - Review the release not= es for the version of Clowder. If you skip a few versions, we strongly reco= mmend that you read the release notes of the versions you have skipped.
=Check for known issues - Use the JIRA to search for any issues in the new version t= hat will affect you.
Check for compatibility:
Confirm that your operating system, database, and other software ins= talled still comply with the requiremen= ts for Clowder.
If you have installed Clowder extractors, verify that they will be c= ompatible with the version of Clowder you are upgrading to. If not you will= need to update the extractors as well.
Prestaging and testing your new version of Clowder:=
We strongly recommend performing your upgrade in a test environment = first. Do not upgrade your production Clowder server until you are satisfie= d that your test environment upgrade has been successful.
If you have any problems with your test environment upgrade which yo= u cannot resolve, create an issue at JIRA= so that we can assist you.
Before you begin the upgrade process, make you have upgraded your databa= se. During the upgrade process your database will be updated to match withe= the new version of the software. If you ever want to rollback to a previou= s version of the software you will have to rollback the database as well. F= ollowing are command to backup your database, as well as the commands neede= d to restore the specific database
This will describe how to backup the mongo database. If you have the fil= es stored in the mongo database (default) this can take a long time and tak= e up a significant amount of space since it will also dump the actual files= . This assumes you are using the default database name (clowder) on th= e local host. If your database is stored somewhere else or has a different = name you will need to modify the commands below. To backup the mongo databa= se use:
mongodu= mp --db clowder --out clowder-upgrade
This will describe how to backup the mongo database. If you have the fil= es stored in the mongo database (default) this can take a long time and tak= e up a significant amount of space since it will also restore the actual fi= les. There are two ways to restore the mongo database, the first one will d= rop the database first, and thus will also remove any additional collection= s you added. The second way will only drop those collections that are impor= ted, this can leave some additional collections that could create trouble i= n future updates.
echo "d= b.dropDatabase();" | mongo --db clowder mongorestore --db clowder clowder-upgrade/clowder
mongore= store --drop --db clowder clowder-upgrade/clowder
If you leverage of the geostreams capabilities in Clowder you will be us= ing a PostgreSQL database. Again this assumes you will be using the default= database (geostream) on localhost. This will dump the database in a direct= ory. Each of the tables will be a separate file that is compressed.
pg_dump= -F d -Z 9 -d bety -f geostream
To restore the database geostream database you can use the following com= mand.
pg_rest= ore -d geostream geostream
The actual update consists of a few steps. After these steps are complet= ed you will have an updated version of clowder.
To make this process easier we have a script "upda= te-clowder.sh" that will perform all these tasks for you (except for the ba= ckup, your are still responsible for the backup). The script does assume yo= u have in the startup script that will have the UPDATE flags enabled.
CLOWDER= _BRANCH=3DCATS-CORE0 ./update-clowder.sh
./updat= e-clowder.sh
For both, if this does not update it, add "--force" after "update-clowder.sh".
Once you have confirmed the availability of compatible versions of the e= xtractors, you should upgrade your extractors after successfully upgrading = Clowder.
Congratulations! You have completed your Clowder upgrade.