-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- update to latest MAAS release (3.3) - add instructions to install Ansible on Jammy - add note about DB data preserved in the nodes after a teardown
- Loading branch information
1 parent
6cc177e
commit 431933f
Showing
1 changed file
with
12 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,6 +6,15 @@ This playbook has been tested with Ansible version 5.10.0 and above. We recommen | |
|
||
## Install | ||
|
||
On systems running the latest Ubuntu LTS version (Jammy), run the following commands to install Ansible: | ||
|
||
``` | ||
sudo apt-get install ansible | ||
ansible-galaxy collection install ansible.utils | ||
``` | ||
|
||
Finally, download the playbook from Github using git | ||
|
||
``` | ||
git clone [email protected]:maas/maas-ansible-playbook | ||
``` | ||
|
@@ -193,7 +202,7 @@ The following variables are only required when using HA Postgres: | |
|
||
``` | ||
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"\ | ||
--extra-vars="maas_version=3.3 maas_postgres_password=example maas_installation_type=deb maas_url=http://example.com:5240/MAAS"\ | ||
./site.yaml | ||
``` | ||
|
@@ -217,6 +226,8 @@ ansible-playbook -i ./hosts \ | |
ansible-playbook -i ./hosts ./teardown.yaml | ||
``` | ||
> Note: this action teardowns only the services, the MAAS database is preserved in the `maas_postgres_*` nodes. You must remove these files manually before attempting to redeploy the stack. | ||
### 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. | ||
|