Bionic maas

From silverwiki

Installed server with ubuntu 18.04 from usb

Configured one switchport on home lan and one switchport on lab lan. The pair of slave nodes are configured with both switchports on the lab lan only.

installed 'maas' package on server

apt-get install maas

create new admin user with

sudo maas init

ip a shows enp5s0 disabled and enp6s0 running dhcp. We need to configure enp5s0 with a static IP. sudo vi /etc/netplan/50-cloud-init.yaml

            dhcp4: no
            dhcp6: no
            addresses: []

After successfully booting a node from the maas server it was attempting to use it's wan address (The one associated with the hostname) to run cloud init. The address clients use needs to be modified in these two files to make cloud-init point to the provisioning lan address and work properly.

vi /etc/maas/regiond.conf vi /etc/maas/rackd.conf


Go to the controllers page. Click add rack controller. It will give you a shell blurb like sudo maas-rack register --url --secret borkborkborkborkborkborkborkbork Run that on the maas node itself.


Add a subnet to the provisioning fabric, then add a reserved range in the subnet, then in the fabric click take action and provide dhcp.

Richard Tapdancing Stallman it's working.... After powering on the managed nodes, they are pxe booting from the maas node!

APC pdu not working for a provisioned node. Needed snmp package.

sudo apt-get install snmp

Now a managed node can be commissioned, tested, and then deployed.

Onward to bionic juju or bionic_maas_pod