You can't use MAAS unless you install it
Errors or typos? Topics missing? Hard to read? Let us know!
This page explains how to install MAAS from scratch. If you're already running MAAS, it's probably easier to upgrade.
Note that support for PostgreSQL version 12 is deprecated for MAAS version 3.4, and will be discontinued in MAAS 3.5. We recommend upgrading to PostgreSQL version 14 before installing MAAS 3.4.
To install MAAS 3.4 from packages:
Check the MAAS installation requirements to make sure that your hardware will support MAAS.
Add the MAAS 3.4 PPA to your apt
repository paths:
nohighlight
sudo apt-add-repository ppa:maas/3.4
Update your apt
repository lists:
nohighlight
sudo apt update
Install MAAS with the following command:
nohighlight
sudo apt-get -y install maas
Choose "Y" if asked about whether to continue with the install.
When installing MAAS on Ubuntu, there can be conflicts between the existing NTP client, systemd-timesyncd
, and the NTP client/server provided by MAAS, chrony. This can lead to time synchronization issues, especially if MAAS is configured with different upstream NTP servers than the ones used by systemd-timesyncd
. To avoid conflicts, users can manually disable and stop systemd-timesyncd
using the following command:
sudo systemctl disable --now systemd-timesyncd
Also note that support for PostgreSQL 12 has been deprecated in MAAS 3.3 and will be discontinued in MAAS 3.5.
Create a distributed environment
To run MAAS region and rack controllers on separate machines:
Check the MAAS installation requirements to make sure that your hardware will support MAAS.
Add the MAAS 3.3 PPA to your apt
repository paths on both region and rack target hosts:
nohighlight
sudo apt-add-repository ppa:maas/3.3
Update your apt
repository lists on both region and rack hosts:
nohighlight
sudo apt update
Install the MAAS region controller on the target region host:
nohighlight
sudo apt install maas-region-controller
Install the MAAS rack controller on the target rack host:
nohighlight
sudo apt install maas-rack-controller
Register the rack controller with the region controller by running the following command on the rack host:
nohighlight
sudo maas-rack register
These two steps will lead you through two similar apt
install sequences.
To create a MAAS administrative user:
Create a MAAS administrator user to access the web UI:
nohighlight
sudo maas createadmin --username=$PROFILE --email=$EMAIL_ADDRESS
Substitute $PROFILE
is the administrative MAAS username you wish to create. $EMAIL_ADDRESS
is an email address you may type in at random (currently, MAAS does not use this email address). The createadmin
option will cause MAAS to ask for an SSH key.
To use an SSH key associated with your launchpad accounts, enter lp:$USERNAME
(substitute your LP username for $USERNAME
).
Alternatively, to use an SSH key associated with your github account, enter gh:$USERNAME
(substitute your github username for $USERNAME
)
Check the status of MAAS services
To check the status of running services, enter:
sudo maas status
Typical output looks like this:
bind9 RUNNING pid 7999, uptime 0:09:17
dhcpd STOPPED Not started
dhcpd6 STOPPED Not started
ntp RUNNING pid 8598, uptime 0:05:42
postgresql RUNNING pid 8001, uptime 0:09:17
proxy STOPPED Not started
rackd RUNNING pid 8000, uptime 0:09:17
regiond:regiond-0 RUNNING pid 8003, uptime 0:09:17
regiond:regiond-1 RUNNING pid 8008, uptime 0:09:17
regiond:regiond-2 RUNNING pid 8005, uptime 0:09:17
regiond:regiond-3 RUNNING pid 8015, uptime 0:09:17
tgt RUNNING pid 8040, uptime 0:09:15
Your mileage may vary.
List additional MAAS initialisation options
The init
command can takes optional arguments. To list them, as well as read a brief description of each, you can enter:
sudo maas init --help
To configure MAAS for first-time use:
Access MAAS at this address, where $API_HOST
is the hostname or IP address of the region API server, which was set during installation:
http://${API_HOST}:5240/MAAS
2. Log in at the prompts, with the login information you created when initialising MAAS.
On the first welcome screen, set the DNS forwarder to a suitable value, e.g., 8.8.8.8
. This could be your own internal DNS server, if you have one.
Select an Ubuntu image to import; you may be required to select at least one LTS version.
Click Continue; a screen labelled, “SSH keys for admin:” appears.
In the Source drop-down, select “Launchpad,” “Github,” or “Upload.”
If you want to upload your SSH public key from Launchpad, you would enter the following, where <username>
is your Launchpad username:
nohighlight
lp:<username>
If you want to upload your github public SSH key, you would enter the following, where <username>
is your GitHub username:
nohighlight
gh:<username>
If you want to use your existing public key from your home directory, select Upload.
Copy your entire public key from .ssh/id_rsa.pub
(or wherever you may have stored the key).
Paste the public key into the block labelled “Public key.”
Press the “Import” button to import this key.
You should see a message that MAAS has been successfully set up. Click Go to the Dashboard to proceed.
Select Subnets from the top menu.
Choose the VLAN on which you want to enable DHCP.
Select Enable DHCP.
You should now be able to add, commission, and deploy machines.