[Maas-devel] MAAS testing: maas 0.1+bzr1116+dfsg-0+1117+109~ppa0~quantal1
Diogo Matsubara
matsubara at canonical.com
Tue Oct 2 05:00:07 UTC 2012
Hi there,
today I tested maas 0.1+bzr1116+dfsg-0+1117+109~ppa0~quantal1 from the
daily builds PPA.
The new packaging scheme is shaping up well. I found some issues which
I raised with Julian and Andres on IRC.
Here are the steps I took.
Installed maas, maas-dhcp and maas-dns packages
After install reconfigured maas-region-controller with the correct
provisioning address.
I enabled ssl by following the instructions in the INSTALL.txt file.
Then created the admin user and set up the maas-cli to connect to the
maas server.
Using the https for the api address, I got the following error:
https://bugs.launchpad.net/maas/+bug/1059970. The web ui works fine
though.
Once maas-cli was authenticated, I set up the dhcp configuration:
$ maas-cli api maas node-group-interfaces new master ip=192.168.21.1
interface=eth0 management=2 subnet_mask=255.255.255.0
broadcast_ip=192.168.21.255 router_ip=192.168.21.1
ip_range_low=192.168.21.10 ip_range_high=192.168.21.50
I mistakenly choose interface=eth0 when it should be br0 (I'm working
with Larry to change the network for the lenovo-rd230-01 machine so we
can run the auto-package-tests there). I couldn't delete this
configuration or update the values. Filed
https://bugs.launchpad.net/maas/+bug/1059954
Once I got the dhcp config correct, I updated
/etc/maas/import_ephermerals and /etc/maas/import_pxe_files and ran
maas-import-pxe-files. Then booted 4 nodes which 3 of them enlisted
correctly. Still debugging why the 4th node failed. I'll update the
list once we have a bug filed.
I found this bug too
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1059973 when you
apt-get remove --purge maas which doesn't seem to cause much problems.
And a small usability problem in the maas-cli:
https://bugs.launchpad.net/maas/+bug/1059984
Cheers,
--
Diogo M. Matsubara
More information about the Maas-devel
mailing list