The starting point our lab is the following:
1 STEP – ADD AND UPDATE MAAS VIA REPOSITORY PPA STABLE
Make the upgrade of MaaS to have the last stable release installed
$: sudo add-apt-repository -yu ppa:maas/stable $: sudo apt update
2 STEP – INSTALL UBUNTU MAAS
There are four ways to install MAAS:
for our lab we’ll use as way to install it the third method, via snappy. Once we have our Ubuntu 16.04 LTS installed we can proceed with the rest. Currently, only the stable and development MAAS versions are available via snaps. This corresponds, respectively, to the ‘stable’ and ‘edge’ snapchannels:
$: snap info maas
name: maas summary: "Metal as a Service" publisher: maas contact: firstname.lastname@example.org description: | Total automation of you physical servers for amazing data center operational efficiency. channels: latest/stable: 2.2.0+bzr6057-snap (91) 98MB - latest/edge: trunk+bzr6071-snap (101) 98MB devmode
To install the snap from the ‘stable’
$: sudo snap install --devmode --stable maas sudo: unable to resolve host maas core 5.97 MB / 79.49 MB [=======>-------------------] 26.54% 457.40 KB/s 2m10 ...... ..... maas 2.2.0+bzr6057-snap from 'maas' installed
We will now need to tell the snap what mode MAAS will run in. This is known as initialization and it is performed by choosing one of the below options.
all– All services;
region– A region API server only (no database);
rack– A rack controller only;
region+rack– A region API server and a rack controller (no database);
The ‘rack’ and ‘region+rack’ modes will additionally ask for the shared secret that will allow the new rack controller to register with the region controller.
2 STEP – INITIALIZATION OF MAAS
This is where MAAS components will be installed and configured. Here, the typical all-in-one design (mode ‘all’) will be chosen as an example:
$: sudo maas init --mode all
A dialog will appear that will gather some basic information:
MAAS URL [default=http://188.8.131.52:5240/MAAS]: http://184.108.40.206:5240/MAAS Create first admin account: Username: email@example.com Password: ****** Again: ****** Email: firstname.lastname@example.org Import SSH keys  (lp:user-id or gh:user-id): lp:riccardo-magrini
A verification of the currently running configuration can be done with:
$: sudo maas config [sudo] password for dakj: Mode: all Settings: maas_url=http://220.127.116.11:5240/MAAS
The status of running services can likewise be checked:
$: sudo maas status bind9 RUNNING pid 6968, uptime 0:20:00 dhcpd STOPPED Not started dhcpd6 STOPPED Not started ntp RUNNING pid 7564, uptime 0:17:13 postgresql RUNNING pid 6975, uptime 0:20:00 proxy RUNNING pid 7892, uptime 0:16:34 rackd RUNNING pid 6967, uptime 0:20:00 regiond:regiond-0 RUNNING pid 6969, uptime 0:20:00 regiond:regiond-1 RUNNING pid 6971, uptime 0:20:00 regiond:regiond-2 RUNNING pid 6974, uptime 0:20:00 regiond:regiond-3 RUNNING pid 6973, uptime 0:20:00 tgt RUNNING pid 8007, uptime 0:16:05
Now to see its dashboard we need to use our preferred browser and point on URL http://18.104.22.168:5240/MAAS/.
lets go with our first login. The first part is done see you to next one.
Disclaimer: All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.
“We learn from our mistakes”