The MAAS cloud and Juju¶

This document describes details specific to using your existing MAAS cloud with Juju.

See more: MAAS

When using this cloud with Juju, it is important to keep in mind that it is a (1) machine cloud and (2) not some other cloud.

See more: Cloud differences

As the differences related to (1) are already documented generically in the rest of the docs, here we record just those that follow from (2).

Requirements¶

Starting with juju v.3.0, versions of MAAS <2 are no longer supported.

Type in Juju: maas

Name in Juju: User-defined.

Attributes:

Note

maas-oauth is your MAAS API key. See more: MAAS | How to add an API key for a user](https://maas.io/docs/how-to-manage-user-accounts#heading–api-key)

CONSTRAINT
conflicting:
supported?
- allocate-public-ip	✕
- arch	✓ Valid values: See cloud provider.
- container	✓
- cores	✓
- cpu-power	✕
- image-id	✓ (Starting with Juju 3.2) Type: String. Valid values: An image name from MAAS.
- instance-role	✕
- instance-type	✕
- mem	✓
- root-disk	✓
- root-disk-source	✕
- spaces	✓
- tags	✓
- virt-type	✕
- zones	✓

PLACEMENT DIRECTIVE
- <machine>	TBA
- subnet=<subnet>	✕
- system-id=<system ID>	✓
- zone=<zone>	✓ If there’s no ‘=’ delimiter, assume it’s a node name.