List of supported clouds > MAAS
This document describes details specific to using your existing MAAS cloud with Juju.
See more: MAAS
When using the MAAS 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 in Juju
As the differences related to (1) are already documented generically in our Tutorial, How-to guides, and Reference docs, here we record just those that follow from (2).
| Juju points of variation | Notes for the MAAS cloud |
|---|---|
| setup (chronological order): | |
| CLOUD | |
| supported versions: | Starting with juju v.3.0, versions of MAAS <2 are no longer supported. |
| requirements: | TBA |
| definition: | Cloud type: maas. You will need to provide your cloud API endpoint. If you want to use a YAML file: |
| CREDENTIAL | |
| definition: |
auth-type: oauth1, which requires you to provide your maas-oauth, i.e., your MAAS API key. > See more: MAAS | How to add an API key for a user
|
| CONTROLLER | |
| notes on bootstrap: | – |
| other (alphabetical order:) | |
| CONFIGURATION (model) | |
| cloud-specific: | TBA |
| CONSTRAINT | |
| conflicting: | TBA |
allocate-public-id |
 |
arch |
 Valid values: See cloud provider. |
container |
|
cores |
|
cpu-power |
|
instance-role |
|
instance-type |
|
mem |
|
root-disk |
|
root-disk-source |
|
spaces |
|
tags |
|
virt-type |
|
zones |
|
| PLACEMENT DIRECTIVE | |
<machine> |
TBA |
subnet=... |
|
system-id=... |
|
zone=... |
If there’s no ‘=’ delimiter, assume it’s a node name. |
|
RESOURCE (cloud) Consistent naming, tagging, and the ability to add user-controlled tags to created instances. |
|