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):
CLOUD
supported versions: Starting with juju v.3.0, versions of MAAS <2 are no longer supported.
requirements: TBA
definition:
- name: user-defined
- type: maas
- authentication types: [oauth1]
- regions: [TO BE ADDED]
- cloud-specific model configuration keys: -
CREDENTIAL
definition: auth-type: oauth1, which requires you to provide your maas-oauth, i.e., your MAAS API key.
> See more: [MAAS `
CONTROLLER
notes on bootstrap:
other (alphabetical order:)
CONSTRAINT
conflicting: TBA
supported?
- allocate-public-ip :x:
- arch :white_check_mark:
Valid values: See cloud provider.
- container :white_check_mark:
- cores :white_check_mark:
- cpu-power :x:
- image-id :white_check_mark: (Starting with Juju 3.2)
Type: String.
Valid values: An image name from MAAS.
- instance-role :x:
- instance-type :x:
- mem :white_check_mark:
- root-disk :white_check_mark:
- root-disk-source :x:
- spaces :white_check_mark:
- tags :white_check_mark:
- virt-type :x:
- zones :white_check_mark:
PLACEMENT DIRECTIVE
<machine> TBA
subnet=... :x:
system-id=... :white_check_mark:
zone=... :white_check_mark:
If there’s no ‘=’ delimiter, assume it’s a node name.
MACHINE
RESOURCE (cloud)

Consistent naming, tagging, and the ability to add user-controlled tags to created instances.

:x:

Contributors (starting with January 2024): @jadonn

Last updated a day ago. Help improve this document in the forum.