Even though Ceph itself supports spine/leaf topologies with multiple subnets for public_network and cluster_network, Microceph and its charm expect only a single subnet for both. The microceph CLI fails when specifying multiple comma-delimited subnets during bootstrap (addresses are just an example):
root@storage1001-i1:~# microceph cluster bootstrap --mon-ip 10.0.1.2 --microceph-ip 10.0.1.2 --public-network 10.0.1.0/24,10.0.2.0/24,10.0.3.0/24 --cluster-network 10.1.1.0/24,10.1.2.0/24,10.1.3.0/24
Error: provided mon-ip 10.0.1.2 is not available on provided public network 10.0.1.0/24,10.0.2.0/24,10.0.3.0/24
The microceph charm (used by Sunbeam to deploy the integrated Microceph cluster) also picks the first network in the spaces mapped to the public and cluster networks, so even if the space lists multiple subnets Microceph will accept only the subnets belonging to the bootstrap node.
Even though Ceph itself supports spine/leaf topologies with multiple subnets for public_network and cluster_network, Microceph and its charm expect only a single subnet for both. The microceph CLI fails when specifying multiple comma-delimited subnets during bootstrap (addresses are just an example):
The microceph charm (used by Sunbeam to deploy the integrated Microceph cluster) also picks the first network in the spaces mapped to the public and cluster networks, so even if the space lists multiple subnets Microceph will accept only the subnets belonging to the bootstrap node.