Repeat steps #3, #4, and #5 for each remaining application (e.g. Repeat step #4 for the remaining machines associated with the ceph-mon application (machines 1 and 2 in this example). Juju ssh 0 sudo do-release-upgrade # reboot when prompted Set the default series for the application so any future application units (scaleout) will use the new series: juju set-series ceph-mon focalĪssuming that the ceph-mon units are on machines 0, 1, and 2 begin with machine 0: juju upgrade-series 0 prepare focal The below example commands will feature the ceph-mon application.

In terms of the upgrade order, begin with the machines hosting the ceph-mon application, after which the remaining applications/machines can be upgraded in any order. On any ceph-mon unit set the ‘noout’ option for the cluster: juju run-action -wait ceph-mon/1 set-noout Prevent data rebalancing from occurring when OSDs start disappearing from the network.

On any ceph-mon unit run a status check: juju ssh ceph-mon/1 sudo ceph status Set the default series for the current model: juju model-config default-series=focalĮnsure that the cluster is in a healthy state. The below example will cover the case of a bionic-to-focal series upgrade. The command used to manage series upgrades on a per-machine basis is the upgrade-series command. Depending on the current state of the cluster and the goal state of the upgrade, a series upgrade may occur before or after a Ceph upgrade. the ‘Ubuntu 18.04 LTS’ release corresponds to the ‘bionic’ series). The operating system running on a Juju machine is known as a Juju “series” and corresponds to an Ubuntu release (e.g.

Ubuntu update node