The MAAS cloud and Juju

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):
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:

<user-defined cloud name>:
   type: maas
    auth-types: [oauth1]
    endpoint: <the endpoint>

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
notes on bootstrap:
other (alphabetical order:)
cloud-specific: TBA
conflicting: TBA
allocate-public-id :negative_squared_cross_mark:
arch :white_check_mark:
Valid values: See cloud provider.
container :white_check_mark:
cores :white_check_mark:
cpu-power :negative_squared_cross_mark:
instance-role :negative_squared_cross_mark:
instance-type :negative_squared_cross_mark:
mem :white_check_mark:
root-disk :white_check_mark:
root-disk-source :negative_squared_cross_mark:
spaces :white_check_mark:
tags :white_check_mark:
virt-type :negative_squared_cross_mark:
zones :white_check_mark:
<machine> TBA
subnet=... :negative_squared_cross_mark:
system-id=... :white_check_mark:
zone=... :white_check_mark:
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.


Last updated a month ago.