How to initialise MicroCloud¶
The initialisation process bootstraps the MicroCloud cluster. You run the initialisation on one of the machines, and it configures the required services on all machines.
Interactive configuration¶
If you run the initialisation process in interactive mode (the default), you are prompted for information about your machines and how you want to set them up. The questions that you are asked might differ depending on your setup; for example, if you do not have the MicroOVN snap installed, you will not be prompted to configure your network, and if your machines don’t have local disks, you will not be prompted to set up local storage.
The following instructions show the full initialisation process.
Tip
During initialisation, MicroCloud displays tables of entities to choose from.
To select specific entities, use the Up and Down keys to choose a table row and select it with the Space key. To select all rows, use the Right key. You can filter the table rows by typing one or more characters.
When you have selected the required entities, hit Enter to confirm.
Complete the following steps to initialise MicroCloud:
On one of the machines, enter the following command:
sudo microcloud init
Select the IP address that you want to use for MicroCloud’s internal traffic (see Network interface for intra-cluster traffic). MicroCloud automatically detects the available addresses (IPv4 and IPv6) on the existing network interfaces and displays them in a table.
You must select exactly one address.
Decide if you want to limit the search for other machines.
If you accept the default (
yes), MicroCloud will automatically detect machines in the local subnet. Otherwise, it will detect all available machines, which might include duplicates (if machines are available both on IPv4 and on IPv6).See Automatic server detection for more information.
Select the machines that you want to add to the MicroCloud cluster.
MicroCloud displays all machines that it detects. This list will periodically update as new machines are detected. Make sure that all machines that you select have the required snaps installed.
Select whether you want to set up local storage.
Note
To set up local storage, each machine must have a local disk. The disks must not contain any partitions.
If you choose
yes, configure the local storage:Select the disks that you want to use for local storage.
You must select exactly one disk from each machine.
Select whether you want to wipe any of the disks. Wiping a disk will destroy all data on it.
Select whether you want to set up distributed storage (using MicroCeph).
Note
To set up distributed storage, you need at least three additional disks on at least three different machines. The disks must not contain any partitions.
If you choose
yes, configure the distributed storage:Select the disks that you want to use for distributed storage.
You must select at least three disks.
Select whether you want to wipe any of the disks. Wiping a disk will destroy all data on it.
You can choose to optionally set up a CephFS distributed file system.
Select whether you want to set up distributed networking (using MicroOVN).
If you choose
yes, configure the distributed networking:Select the network interfaces that you want to use (see Network interface to connect to the uplink network).
You must select one network interface per machine.
If you want to use IPv4, specify the IPv4 gateway on the uplink network (in CIDR notation) and the first and last IPv4 address in the range that you want to use with LXD.
If you want to use IPv6, specify the IPv6 gateway on the uplink network (in CIDR notation).
MicroCloud now starts to bootstrap the cluster. Monitor the output to see whether all steps complete successfully. See Bootstrapping process for more information.
Once the initialisation process is complete, you can start using MicroCloud.
See an example of the full initialisation process in the Get started with MicroCloud tutorial.
Excluding MicroCeph or MicroOVN from MicroCloud¶
If the MicroOVN or MicroCeph snap is not installed on the system that runs microcloud init, you will be prompted with the following question:
MicroCeph not found. Continue anyway? (yes/no) [default=yes]:
MicroOVN not found. Continue anyway? (yes/no) [default=yes]:
If you choose yes, only existing services will be configured on all systems.
If you choose no, the setup will be cancelled.
All other systems must have at least the same set of snaps installed as the system that runs microcloud init, otherwise they will not be available to select from the list of systems. Any questions associated to these systems will be skipped. For example, if MicroCeph is not installed, you will not be prompted for distributed storage configuration.
Reusing an existing MicroCeph or MicroOVN with MicroCloud¶
If some of the systems are already part of a MicroCeph or MicroOVN cluster, you can choose to reuse this cluster when initialising MicroCloud when prompted with the following question:
"micro01" is already part of a MicroCeph cluster. Do you want to add this cluster to MicroCloud? (add/skip) [default=add]:
"micro01" is already part of a MicroOVN cluster. Do you want to add this cluster to MicroCloud? (add/skip) [default=add]:
If you choose add, MicroCloud will add the remaining systems selected for initialisation to the pre-existing cluster.
If you choose skip, the respective service will not be set up at all.
If more than one MicroCeph or MicroOVN cluster exists among the systems, the MicroCloud initialisation will be cancelled.
Non-interactive configuration¶
If you want to automate the initialisation process, you can provide a preseed configuration in YAML format to the microcloud init command:
cat <preseed_file> | microcloud init --preseed
The preseed YAML file must use the following syntax:
# `lookup_subnet` limits the subnet when looking up systems with mDNS.
lookup_subnet: 10.0.0.1/24
# `systems` lists the systems we expect to find by their host name.
# `name` represents the host name
# `ovn_uplink_interface` is optional and represents the name of the interface reserved for use with OVN.
# `storage` is optional and represents explicit paths to disks for each system.
systems:
- name: micro01
ovn_uplink_interface: eth1
- name: micro02
ovn_uplink_interface: eth1
storage:
local:
path: /dev/nvme5n1
wipe: true
ceph:
- path: /dev/nvme4n1
wipe: true
- path: nvme3n1
wipe: true
- name: micro03
ovn_uplink_interface: eth1
- name: micro04
ovn_uplink_interface: eth1
# `ovn` is optional and represents the OVN & uplink network configuration for LXD.
ovn:
ipv4_gateway: 192.0.2.1/24
ipv4_range: 192.0.2.100-192.0.2.254
ipv6_gateway: 2001:db8:d:200::1/64
dns_servers: 192.0.2.1,2001:db8:d:200::1
# `storage` is optional and is used as basic filtering logic for finding disks across all systems.
# Filters are checked in order of appearance.
# The names and values of each key correspond to the YAML field names for the `api.ResouresStorageDisk`
# struct here:
# https://github.com/canonical/lxd/blob/c86603236167a43836c2766647e2fac97d79f899/shared/api/resource.go#L591
# Supported operands: &&, ||, <, >, <=, >=, ==, !=, !
# String values must not be in quotes unless the string contains a space.
# Single quotes are fine, but double quotes must be escaped.
# `find_min` and `find_max` can be used to validate the number of disks each filter finds.
# `cephfs: true` can be used to optionally set up a CephFS file system alongside Ceph distributed storage.
storage:
cephfs: true
local:
- find: size > 10GiB && size < 50GiB && type == nvme
find_min: 1
find_max: 1
wipe: true
- find: size > 10GiB && size < 50GiB && type == hdd && block_size == 512 && model == 'Samsung %'
find_min: 3
find_max: 3
wipe: false
ceph:
- find: size > 10GiB && size < 50GiB && type == nvme
find_min: 1
find_max: 2
wipe: true
- find: size > 10GiB && size < 50GiB && type == hdd && partitioned == false && block_size == 512 && model == 'Samsung %'
find_min: 3
find_max: 8
wipe: false