MAAS requirements

The minimum requirements for the machines that run MAAS vary widely depending on local implementation and usage.

Below, you will find resource estimates based on MAAS components and operating system (Ubuntu Server). Both a test configuration (for proof of concept) and a production environment are considered.

Test environment

Here is a proof of concept scenario, with all MAAS components installed on a single host. This scenario assumes two complete sets of images (latest two Ubuntu LTS releases) for a single architecture (amd64).

Memory (MB) CPU (GHz) Disk (GB)
Region controller (minus PostgreSQL) 512 0.5 5
PostgreSQL 512 0.5 5
Rack controller 512 0.5 5
Ubuntu Server (including logs) 512 0.5 5

Therefore, the approximate requirements for this scenario are 2 GB memory, 2 GHz CPU, and 20 GB of disk space.

Production environment

Here is a production scenario designed to handle a high number of sustained client connections. This scenario implements both high availability (region and rack) and load balancing (region).

MAAS reserves extra space for images (database and rack controller), some images such as those for Microsoft Windows may require a lot more, so plan accordingly.

Memory (MB) CPU (GHz) Disk (GB)
Region controller (minus PostgreSQL) 2048 2.0 5
PostgreSQL 2048 2.0 20
Rack controller 2048 2.0 20
Ubuntu Server (including logs) 512 0.5 20

Therefore, the approximate requirements for this scenario are:

  • A region controller (including PostgreSQL) installed on one host, with 4.5 GB memory, 4.5 GHz CPU, and 45 GB of disk space.
  • A duplicate region controller (including PostgreSQL) on a second host, also with 4.5 GB memory, 4.5 GHz CPU, and 45 GB of disk space.
  • A rack controller installed on a third host, with 2.5 GB memory, 2.5 GHz CPU, and 40 GB of disk space.
  • A duplicate rack controller on a fourth host, also with 2.5 GB memory, 2.5 GHz CPU, and 40 GB of disk space.

The tables above refer to MAAS infrastructure only. They do not cover the resources needed by subsequently-added nodes. Note that machines should have IPMI-based BMC controllers for power cycling, see [BMC power types][power-types].

Examples of factors that influence hardware specifications include:

  • the number of connecting clients (client activity)
  • how you decide to distribute services
  • whether high availability is used
  • whether load balancing is used
  • the number of images that are stored (disk space affecting PostgreSQL and the rack controller)

Equally not taken into account is a possible [local image mirror][mirror] which would be a large consumer of disk space.

One rack controller should not be used to service more than 1000 nodes (whether on the same or multiple subnets). There is no load balancing at the rack level, so you will need additional, independent rack controllers. Each controller must service its own subnet(s).

Last updated a day ago. Help improve this document in the forum.