MAAS-ansible-playbook

An Ansible playbook for installing and configuring MAAS

Install

git clone git@github.com:maas/maas-ansible-playbook

Setup

This playbook has several main roles, each has a corresponding group to assign hosts to. They are as follows:

maas_postgres_primary: This role and group is for a host to be configured as an initial Postgres primary instance for the MAAS stack. This role is required.
maas_postgres_secondary: This role and group is for hosts to be configured as Postgres secondaries in hot standby with synchronous replication. This role is optional.
maas_region_controller: This role and group is for hosts to be configured as MAAS Region Controllers. This role is required at least once.
maas_rack_controller: This role and group is for hosts to be configured as MAAS Rack Controllers. This role is required at least once.
maas_proxy: This role and group is for hosts to be configured as an HAProxy instance in front of region controllers for HA stacks. This role is optional.

Example Host File:

[maas_postgres_primary]
db01.example.com

[maas_postgres_secondary]
db02.example.com
db03.example.com

# DO NOT MODIFY THIS GROUP
[maas_postgres:children]
maas_postgres_primary
maas_postgres_secondary

[maas_region_controller]
region01.example.com
region02.example.com
region03.example.com

[maas_rack_controller]
region01.example.com
rack01.example.com
rack02.example.com

[maas_proxy]
proxy01.example.com

Run

This playbook requires a user to set the following set of variables:

maas_version: The intended version of MAAS to install. Example: '3.2'
maas_postgres_password: The password for the MAAS postgres user. Example: 'my_password'
maas_installation_type: The intended type of MAAS installation. Possible values are: 'deb' or 'snap'
maas_url: The MAAS URL MAAS will be accessed and rack controllers should use for registering with region controllers. Example: 'http://proxy01.example.com:5240/MAAS'

Deploy the MAAS stack

ansible-playbook -i ./hosts\
    --extra-vars="maas_version=3.2 maas_postgres_password=example maas_installation_type=deb maas_url=http://example.com:5240/MAAS\
    ./site.yaml"

Teardown the MAAS stack

ansible-playbook -i ./hosts ./teardown.yaml

Backup the MAAS stack

Backup MAAS requires the maas_backup_download_path variable to be set, it will designate a path local to where the playbook is being run to download backup archives. This path must exist prior to running the playbook. maas_installation_type is also required.

ansible-playbook -i ./hosts --extra-vars="maas_backup_download_path=/tmp/maas_backups/ maas_installation_type=deb" ./backup.yaml"

Restore from Backup

Since backup is per-host, it is recommended to set the maas_backup_file variable as a host variable, or filter execution to a specific host, but maas_backup_file should be set to a gzipped tar file from the backup action and maas_installation_type should be set as well.

The below example assumes maas_backup_file is set in ./hosts

ansible-playbook -i ./hosts --extra-vars="maas_installation_type=deb" ./restore.yaml

Create a new admin user

For an already existing MAAS installation, a new admin user can be created. The below example assumes the host for which the account is to be created is set under [maas_region_controller] in ./hosts. user_ssh allows for upload of a Launchpad (lp:id) or GitHub (gh:id) public key, or can be left blank (user_ssh=).

ansible-playbook -i ./hosts --extra-vars="user_name=newuser user_pwd=newpwd user_email=user@email.com user_ssh=lp:id" ./createadmin.yaml

troyanov/maas-ansible-playbook