...
Read about the new version - Review the release notes for the version of Clowder. If you skip a few versions, we strongly recommend 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 that will affect you.
Check for compatibility:
Confirm that your operating system, database, and other software installed still comply with the requirements for Clowder.
If you have installed Clowder extractors, verify that they will be compatible 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 satisfied that your test environment upgrade has been successful.
If you have any problems with your test environment upgrade which you cannot resolve, create an issue at JIRA so that we can assist you.
...
If you leverage of the geostreams capabilities in Clowder you will be using a PostgreSQL database. Again this assumes you will be using the default database (geostream) on localhost. This will dump the database in a directory. Each of the tables will be a separate file that is compressed.
| Code Block | ||||
|---|---|---|---|---|
| ||||
pg_dump -F d -Z 9 -d bety -f geostream |
2.4 Restoring PostgreSQL
To restore the database geostream database you can use the following command.
| Code Block | ||||
|---|---|---|---|---|
| ||||
pg_restore -d geostream |
geostream |
3. Performing the upgrade
The actual update consists of a few steps. After these steps are completed you will have an updated version of clowder.
- Make sure you have backed up your database.
- Download the version you want to install, some common versions are:
- Latest stable version - This version is more tested, but is not as up to date as the development version.
- Latest development version - This version contains the latest code and has been lightly tested.
- Stop the current version of clowder you have running
- Move the folder of the current version
- Unzip the downloaded version of clowder
- Move the custom folder of the original clowder to the custom folder of the new clowder
- Start clowder. Make sure your startup script uses the flag -DMONGOUPDATE=1 and -DPOSTGRESUPDATE=1 to update the databases. If the database is not updated the application might not run correctly and/or you might not be able to login.
To make this process easier we have a script "update-clowder.sh" that will perform all these tasks for you (except for the backup, your are still responsible for the backup). The script does assume you have in the startup script that will have the UPDATE flags enabled.
- To upgrade to the latest development version, as root, do:
Code Block CLOWDER_BRANCH=CATS-CORE0 ./update-clowder.sh - To upgrade to the latest stable version, as root, do:
Code Block ./update-clowder.shFor both, if this does not update it, add
"--force"after "update-clowder.sh".
4. Post upgrade checks and tasks
Once you have confirmed the availability of compatible versions of the extractors, you should upgrade your extractors after successfully upgrading Clowder.
...