Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hello, First thing: Please switch to Ubuntu 13.10 if you can, it has many bugs fixed. You wrote "The enlistment and commission process take a very long time (just food for thought)", I will give you one more :) In 13.10 there's a fast installer tag, use it to save some serious node deployment time. I will tell you what I did in my setup: I used Ubuntu 13.10 and KVM 1) Nodes added in KVM must only be prepared to PXE boot and left as is. 2) This will in turn invoke the maas-dhcp and maas-dns, which takes over and assigns an IP from the dhcp pool provided in the cluster configuration. 3) Then the VM shuts down and needs to be powered on manually(trying to get over this: see virsh-settings image) 4) On your MaaS server, you need to do following: a) Install Juju and core dependencies b) juju generate-config: which provides an environments.yaml file to be edited as per your needs (hp cloud/azure/maas/linux containers/maas) c) juju sync-tools: juju tools to be downloaded from amazonaws which are used by the juju nodes in cloud-init scripts. d) juju -v bootstrap --upload-tools: This will bootstrap a VM and install specified OS(used precise Pangolin) on it. e) juju deploy mysql: Will deploy the mysql charm on one of the 'ready' nodes.

5) So, for the 4th step to properly execute, we need to ensure that all nodes that are in 'Declared' state must be 'Commission'ed. Doing this will make the state to be 'Ready'. 6) Bootstrap and deployment of charms works only if the nodes are in ready state. MaaS takes care of installation of OS and other things. Use fast installer tag. 7) Once you’ve run “juju bootstrap --upload-tools” from the MAAS Controller, the MAAS GUI will show the node as allocated (a section of the pie chart will go from green to light blue). 8) One more important thing: We need to add the MAAS IP address as a nameserver in /etc/resolv.conf when using Juju otherwise the ‘juju status’ command will timeout.

Hope this helps.