Upgrade from v1.3 to v1.4
This documentation consider that Prelude is installed on two hosts in the /opt/prelude folder. It can be easily adapted for a single host installation.
Backup
Start by a backup of OneBoard database:
docker compose exec -it db-oneboard pg_dump --dbname=prelude --username=prelude > oneboard.backup.sql
Then, Stop both Prelude OneBoard and Prelude Foundation components.
Upgrade: Prelude OneBoard
Then, set the OneBoard container tag to v1.4 in docker-compose.yml.
Pull the new images :
Migrate the database and start the containers:
docker compose run --entrypoint="/app/prelude-oneboard migrate" oneboard
docker compose up -d --remove-orphans
Check that all containers are up and running (the name could be slightly different depending on the setup):
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
prelude-oneboard-db-1 postgres:16.1-alpine "docker-entrypoint.s…" db-oneboard 6 minutes ago Up 6 minutes 5432/tcp
prelude-nats-1 nats:2.10-linux "/nats-server -c /et…" nats 6 minutes ago Up 6 minutes 6222/tcp, 0.0.0.0:4222->4222/tcp, [::]:4222->4222/tcp, 8222/tcp
prelude-oneboard-1 registry.arolo-solutions.com/demo/prelude-oneboard:1.4 "/app/prelude-oneboa…" prelude 6 minutes ago Up 6 minutes 0.0.0.0:443->443/tcp, [::]:443->443/tcp, 0.0.0.0:4010->4010/tcp, [::]:4010->4010/tcp
OneBoard upgrade is done.
Upgrade: Prelude Foundation
Start by setting Gateway container tag to v1.4 in docker-compose.yml.
Then pull the new images and start the containers:
Migrate the Gateway database:
Check that all containers are up and running (the name could be slightly different depending on the setup):
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
prelude-gateway-db-1 postgres:16.1-alpine "docker-entrypoint.s…" db-gateway 6 minutes ago Up 6 minutes 5432/tcp
prelude-gateway-1 registry.arolo-solutions.com/prelude/prelude-gateway:1.4 "/app/prelude-gatewa…" gateway 6 minutes ago Up 6 minutes 0.0.0.0:67->67/udp, [::]:67->67/udp, 0.0.0.0:4020-4021->4020-4021/tcp, [::]:4020-4021->4020-4021/tcp
prelude-nso-1 cisco-nso-prod:6.1.12 "/run-nso.sh" nso 6 minutes ago Up 6 minutes (healthy) 0.0.0.0:2022->2022/tcp, [::]:2022->2022/tcp
NSO packages upgrade
On the OneBoard host, get the NSO packages:
Copy all the packages from the OneBoard host to the foundation host:
Remove previous version packages:
Then, move the new files to the NSO packages folder:Finally, reload NSO packages
Foundation upgrade is done.