Deploy new Atomio version

Prior to deploying a new version of Atomio, the filesystem mount it is using should be backed up / restorable to a recent point prior to deployment of the new updated version. It is recommended that a backup be taken immediately prior to deploying the update.

Installing a new update

Installing a new updated version requires

1. pulling a new Atomio Docker image from a repository, or installing a image tarball (depending upon how software versions are deployed in your Docker setup)
2. recreating the Atomio container

Step 2 above requires a short outage to stop the old container and create a new container which uses the new image. The boot time of Atomio is very fast (typically 5-10 seconds) and the longest part of this process is pulling the new Docker image, so this should be done before the Atomio container is stopped and the new one started to minimise the outage.

Database schema migration

Any database schema changes required by the new version of Atomio will be made by the new instance of Atomio when it is booted from the new Docker image. There are no manual steps required.

Rollback

Unlike automated forward database migration in new Atomio versions, no automated downgrade capability is built into Atomio.

Rollback is performed by

1. Shutting down the Atomio container
2. Restoring the container’s filesystem mount to a recent backup prior to the upgrade
3. Recreate the Atomio container using the previous Docker image