Juju MaaS cloud, one less node available than I expected?

getting started
1

I’m trying a HomeLab experiment creating a bar metal MaaS cloud to be controlled by Juju. The next goal would be a Kubernetes cluster on the MaaS Cloud.

Lots of demos and tutorials using virtual fake bare metal machines but I am using real machines. HP-EliteDesk and HP-ProDesk mini machines.

The intention of the five machines is to have one controller node for MaaS and Juju controllers and a four node MaaS cloud.

efed17a074679782f45ee6eeaf9322972ff4ccc7

I installed MaaS on my controller node and tinkered with commissioning and deploying to the four machines. Pretty cool.

I then went to install Juju and creating a MaaS network.

When I did, it seems like Juju is claiming one of my four nodes for some reason leaving only three remaining for deployment.

Anyone know why Juju is claiming one node when I create a MaaS Cloud?

2

I did read in the documentation that this behavior is expected. The maas cloud juju controller is installed on one of the maas nodes. My next investigation is whether that maas node is still available for additional workload or if it is entirely consumed by the presence of the maas cloud juju controller.