Non-snap MAAS installs

Snap is the preferred method of installing MAAS. Fully-confined snap installs begin with version 2.7.0. For completeness, this page offers package installation instructions. There is also a more detailed page about installing from packages that may be useful for installing packages for versions 2.7 and below.

Install MAAS from packages

This section covers the obsoleted use of deb/APT packages to install MAAS. With the advent of MAAS 2.7.0, installation via snap is the recommended method to acquire MAAS. You may want to consider an installation within LXD containers. These containers allow MAAS nodes to also run as local containers and are ideal for testing and experimenting with MAAS.

You can install a newer stable version via PPAs listed on the MAAS launchpad, including:

For example, to add the 2.8 PPA, type:

sudo apt-add-repository -yu ppa:maas/2.8

There is also a “transitional” PPA:

This PPA contains the same transitional deb packages that are available in 20.04. It’s designed to help people running deb-based MAAS on 18.04 to migrate to the snap even before upgrading to 20.04.

Installation scenarios

The recommended way to set up an initial MAAS environment is to put everything on one machine:

sudo apt install maas

Executing this command leads you to a list of dependent packages to be installed, and a summary prompt that lets you choose whether to continue with the install:

Choosing “Y” proceeds with a standard apt package install.

Distributed environment

For a more distributed environment, you can place the region controller on one machine:

sudo apt install maas-region-controller

and the rack controller (see Rack controller for details) on another:

sudo apt install maas-rack-controller
sudo maas-rack register

These two steps will lead you through two similar apt install sequences.

Creating a MAAS user

Finally, you will need to create a MAAS administrator user to access the web UI:

sudo maas createadmin --username=$PROFILE --email=$EMAIL_ADDRESS

For example, the process might go like this:

The username can be anything. You will also be prompted to supply a password for the user. The command option --password=$PASSWORD can be used to specify one but, depending on your environment, this may pose a security risk.

At this time, MAAS does not make use of the email address. However, it may do so in the future.

Finally, the createadmin option asks for an SSH key:


If you have an SSH key associated with your launchpad or github accounts, you can enter the username here to include the key. For launchpad, just enter lp:username, and for github, enter gp:username at the prompt. In both cases, the actual username has to be supplied after the lp: or gh: prefix.

If you don't have a key associated with either of these services, you will have an opportunity to paste your public key into the MAAS SSH key list, after you've started MAAS for the first time as part of the welcome screens.

Once all this is done, you’re ready to access MAAS from the web UI and begin your Configuration journey.

Upgrading packages (2.5 through 2.7)

To upgrade any version from 2.5 to 2.7 to the next higher version, simply perform the following steps:

sudo apt-add-repository ppa:maas/2.n
sudo apt update
sudo apt upgrade maas

This should lead you through the upgrade process. Upgrading MAAS 2.8 to MAAS 2.9 via packages is covered in the relevant install article.

Next steps

Once you have installed your MAAS environment (region + rack controller) and any possible extra rack controllers(s), you are ready to begin your Configuration journey.

1 Like