Scaling the cluster in

Canonical OpenStack scales in, meaning that you can remove machines from the cluster if you no longer need them.

Scaling the cluster in using the manual bare metal provider

The following section provides instructions on scaling the cluster in with the manual bare metal provider.

These instructions apply to all node types but the primary node. For instruction on the latter, refer to Removing the primary node section of this documentation.

Remove the machine from the cluster

To remove the machine from the cluster, execute the sunbeam cluster remove command on the primary node:

sunbeam cluster remove --name FQDN

FQDN is a fully qualified domain name (FQDN) of the machine being removed.

For example, to remove the cloud-2 machine from the Example physical configuration section, execute the following command:

sunbeam cluster remove --name cloud-2.example.com

Remove components from the machine

Software components now need to be removed from the target node. Perform all the below steps on the target node.

Remove the Juju agent:

sudo /sbin/remove-juju-services

Remove the juju snap:

sudo snap remove --purge juju

Remove Juju configuration:

rm -rf ~/.local/share/juju

Remove the openstack-hypervisor and openstack snaps:

sudo snap remove --purge openstack-hypervisor
sudo snap remove --purge openstack

Remove openstack snap configuration:

rm -rf ~/.local/share/openstack

Remove the k8s snap:

sudo k8s remove-node
sudo snap remove --purge k8s

Note

The above steps can take a few minutes to complete.

Remove the disk(s) used by MicroCeph on this node:

sudo microceph disk list
sudo microceph disk remove <OSD on this node>

Remove the microceph snap:

sudo microceph disk list
sudo snap remove --purge microceph

If required clean the disk(s) identified in the earlier command:

Warning

The dd command will result in the permanent erasure of data. It is vital that you have specified the correct disk path to avoid unintended data loss.

sudo dd if=/dev/zero of=PATH bs=4M count=10

PATH is a path to the disk being cleaned.

Clear the remaining network configuration with a reboot:

sudo reboot

Scaling the cluster in using Canonical MAAS

The following section provides instructions on scaling the cluster out with Canonical MAAS.

Coming soon.