I’ve recently installed MaaS 3.4 and deployed Ubuntu 22.04 on three separate machines. I chose not to automatically register these machines as VM hosts via the MaaS UI. The reason was, MaaS seemed to deploy three isolated LXD hosts, which would later prevent me from forming an LXD Cluster. This would necessitate a reinstallation of LXD. Therefore, I initiated these machines in a blank state, with just the OS installed. Additionally, MaaS’s use of the PXE network to communicate with LXD is not ideal for my setup, as the PXE network (kinda OOBM here) does not align with my InBand on top of a bond channel.
Following this, I manually created an LXD Cluster on these freshly deployed machines and connected it with MaaS. However, I’ve encountered a problem: MaaS only recognizes one IP from the LXD Cluster. If the LXD node known to MaaS goes offline, MaaS loses its ability to manage the LXD Cluster.
To address this, I added a second LXD node (from the same LXD Cluster) in MaaS, but this resulted in a duplicate host listing in the MaaS UI.
I’m seeking advice on how to properly integrate an LXD Cluster into MaaS so that it remains functional even if one or two nodes go offline. Would adding a VIP to the LXD Cluster and then integrating the LXD Cluster into MaaS using that VIP be a viable solution? What is the recommended method to achieve this?
I also came across a StackOverflow post stating that MaaS doesn’t support LXD Clusters with Ubuntu 22.04:
Is this still the case with MaaS 3.4? Could this be the reason behind the issue I’m experiencing?
Here are some screenshots for reference:
- LXD Cluster added to MaaS:
- LXD node known to MaaS rebooted intentionally, MaaS losing access to LXD Cluster:
NOTE: MaaS regains access after LXD Node comes back online.
- Another LXD node was added to MaaS to address the SPOF situation:
- Resulting duplicate LXD Cluster listing in MaaS UI:
I’m eager to find a proper setup that eliminates the SPOF. Any guidance would be greatly appreciated.