The overall target of the setup is a lab system based on a single server. To get familiar with Ubuntu MAAS, Juju and Openstack my goal is to "simulate" physical servers to be controlled/managed by MAAS.
The host system OS is Ubuntu server 14.04.3 LTS release and should host a MAAS controller (mass-controller-vm) and "physical" servers (vm1 - vm8).
For the "mass-network" I have created a virtual bridge (virbr1) with connectivity outside the system via NAT. The MAAS controller managed interface is connected via eth1 (172.16.0.200) to virbr1. To reach the MAAS GUI from remote, I have created an interface (eth0 10.49.228.163) to br0.
The initial setup of the VM's (vm1 - vm8) is done via remote VMM.
The MAAS controller eth1 interface is configured according MAAS documentation. The only point where I have an issue is regarding the MAAS cluster managed interface configuration (eth1). When I configure under the "edit cluster interface" the "router IP" = 172.16.0.1 than the "physical" server PXE boot process will not finish successfully. The next two screenshot showing the last state: Followed by following error messages:
When I configure under the "edit cluster interface" the "router IP" = 172.16.0.200 than the "physical" server PXE boot process will finish succesful but the default gateway on the "physical" server (e.g. vm1) is 172.16.0.200 which is indeed wrong for the 172.16.0.0 subnet.
Routing table on MAAS controller:
c220@maas-controller:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.49.228.170 0.0.0.0 UG 0 0 0 eth0 10.49.228.160 0.0.0.0 255.255.255.224 U 0 0 0 eth0 172.16.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 c220@maas-controller:~$
What's going wrong here? The ethe0 interface on the MAAS controller vm is declared as an unmanned interface under "edit cluster controller" page.
Any help/ideas are welcome.