No software is perfect and few are ever complete. Updates are, or should be, part of the day to day operations. This document describes the steps you can follow to upgrade Replicante without service interruption.
This document does NOT describe how to update replicante’s dependencies.
You should take care to keep them up to date as well.
The upgrade path relies on Replicante high availability features to avoid loss of service. Nodes are updated one at a time, upgrading them between compatible versions. Once all nodes are up to date and restarted the upgrade is complete.
repliadm validate update-compatibility).
Once the upgrade is complete you should review the configuration to enable new options and disable any deprecated features. Refer to the change log to know what was added and what was deprecated.
Any software that persist data needs to deal with changes to the schema as the software evolves. Replicante tries to avoid the need for migrations by gradually rolling out changes to the schema.
When the data schema needs to change:
Upgrading to major releases
Always run the latest minor release before upgrades to the next major release.
The approach above works because Replicante expires historical data and refreshes monitoring data. You may need to run the latest minor release until all data items are expired or refreshed. The
repliadm validate update-compatibilitycommand can scan your dataset to ensure all items are compatible with the new format.