I’m trying to split my MaaS deployments into two, first server will be for MaaS Region Controller and the second, isolated, will be the MaaS Rack Controller.
However, since my network topology is a bit complex (yes, just a bit), the Machine’s deployments are failing if I run the Rack stuff in a separated server. When they’re running on the same server, it’s all good.
Here is my network topology:
Number of VLANs: 3
VLAN 2: Called “Metal”, Subnet 192.168.0.0/22, ONLY to ssh into MaaS’ boxes (default gw for both Region and Rack)
VLAN 3: Called “Maas-PXE”, Subnet 192.168.4.0/22, ONLY for MaaS’ PXE Boot (not the default gw of the nodes)
VLAN 4: Called “Public”, Subnet 172.29.232.0/22, ONLY for deployed Machines (this is the default gw of them and how users will reach them)
1- MaaS Region Controller have only 1 IP, 192.168.0.5
2- MaaS Rack Controller have 2 IPs, 192.168.0.10 AND 192.168.4.10 (PXE Net)
3- Deployed Machines are supposed to have 2 IPs, 192.168.4.50~100 (PXE) AND 172.29.232.10
Thing is, when I try to deploy a Machine WITHOUT VLAN 4, it works! However, soon as I try to deploy the very same Machine, with an interface at VLAN 4, the deployment fails.
If I’m not mistaken, I can see that cloud-init can’t communicate with MaaS…
I though that with MaaS 2.5, it would be possible to use the Rack Controller as a Proxy to reach the Region Controller, is this already working with beta 4?
Also, I’m confused about the “dpkg-reconfigure maas-region-controller” option! It says:
The Ubuntu MAAS Server automatically detects the IP address that is used for PXE and provisioning. However, it needs to be reacheable by the clients (e.g L2 or L3 network). If the
automatically detected address is not reacheable by the clients, it needs to be changed.
Ubuntu MAAS PXE/Provisioning network address:
I’m confused! Why the MaaS Region Controller should “care” about the PXE Addr if it isn’t supposed to have connection there? Remember, the PXE network is behind the Rack Controller only, not reachable from the Region Ctrl.
Then, on MaaS Rack Controller, the “dpkg-reconfigure maas-rack-controller” says:
The MAAS cluster controller and nodes need to contact the MAAS region controller API. Set the URL at which they can reach the MAAS API remotely, e.g. “http://192.168.1.1/MAAS”. Since nodes must be able to access this URL, localhost or 127.0.0.1 are not useful values here.
Ubuntu MAAS API address:
So, here, it makes more sense, since the Machines can ONLY reach the Rack Controller, I’m configuring its IP, so, in theory, the Machines will try to contact the Rack controller for metadata.
BUT, it isn’t working!
I even tried to connect the Region Controller directly at the PXE Network (new IP 192.168.4.5) and point to it on both “dpkg-reconfigure maas-*-controller” but, doesn’t work!
If I run both Region and Rack controllers within the same server, it’s all good.