Comment 0 for bug 1915869

$ maas -h
/snap/maas/11778/usr/lib/python3/dist-packages/netaddr/strategy/__init__.py:189: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if word_sep is not '':
usage: maas [-h] COMMAND ...

optional arguments:
  -h, --help show this help message and exit

drill down:
  COMMAND
    login Log in to a remote API, and remember its description and credentials.
    logout Log out of a remote API, purging any stored credentials.
    list List remote APIs that have been logged-in to.
    refresh Refresh the API descriptions of all profiles.
    init Initialise MAAS in the specified run mode.
    config View or change controller configuration.
    status Status of controller services.
    migrate Perform migrations on connected database.
    apikey Used to manage a user's API keys. Shows existing keys unless --generate or --delete is passed.
    configauth Configure external authentication.
    createadmin Create a MAAS administrator account.
    changepassword
                  Change a MAAS user's password.

http://maas.io/

(Note the "SyntaxWarning" string; while it's not harmful at all, currently it breaks some FCE-related automation which relies on MAAS CLI outputs).

$ snap list maas
Name Version Rev Tracking Publisher Notes
maas 2.9.2-9165-g.b5dc1fd6c 11778 2.9/stable canonical✓ -

$ snap info maas
name: maas
summary: Metal as a Service
publisher: Canonical✓
store-url: https://snapcraft.io/maas
contact: https://discourse.maas.io/
license: unset
description: |
  **MAAS - Very fast server provisioning**

  Metal as a Service -- MAAS -- lets you treat physical servers like virtual machines in the cloud.
  Rather than having to manage each server individually, MAAS turns your bare metal into an elastic
  cloud-like resource.

  What does that mean in practice? Tell MAAS about the machines you want it to manage and it will
  boot them, check the hardware's okay, and have them waiting for when you need them. You can then
  pull nodes up, tear them down and redeploy them at will; just as you can with virtual
  machines in the cloud.

  When you're ready to deploy a service, MAAS gives your tool of choice (e.g. Ansible, Chef, Puppet,
  SALT, Juju) the nodes it needs to power that service. It's as simple as that: no need to manually
  provision, check and, afterwards, clean-up. As your needs change, you can easily scale services up
  or down. Need more power for your Hadoop cluster for a few hours? Simply tear down one of your
  Nova compute nodes and redeploy it to Hadoop. When you're done, it's just as easy to give the node
  back to Nova.

  MAAS is ideal where you want the flexibility of the cloud, and the hassle-free power of Juju
  charms, but you need to deploy to bare metal.
commands:
  - maas
  - maas.power
services:
  maas.supervisor: simple, enabled, active
snap-id: shY22YTZ3RhJJDOj0MfmShTNZTEb1Jiq
tracking: 2.9/stable
refresh-date: today at 19:25 UTC
channels:
  2.9/stable: 2.9.2-9165-g.b5dc1fd6c 2021-02-16 (11778) 137MB -
  2.9/candidate: ↑
  2.9/beta: ↑
  2.9/edge: 2.9.3~alpha1-9167-g.77a9b6c3d 2021-02-16 (11800) 143MB -
  latest/stable: –
  latest/candidate: –
  latest/beta: –
  latest/edge: 2.10.0~alpha1-9475-g.ea405085f 2021-02-16 (11805) 143MB -
  2.8/stable: 2.8.2-8577-g.a3e674063 2020-09-01 (8980) 140MB -
  2.8/candidate: 2.8.3~rc1-8583-g.9ddc8051f 2020-11-19 (10539) 137MB -
  2.8/beta: 2.8.3~rc1-8583-g.9ddc8051f 2020-11-19 (10539) 137MB -
  2.8/edge: 2.8.3~rc1-8590-g.4c151dda9 2021-02-16 (11781) 138MB -
  2.7/stable: 2.7.3-8290-g.ebe2b9884 2020-08-21 (8724) 144MB -
  2.7/candidate: ↑
  2.7/beta: ↑
  2.7/edge: 2.7.3-8297-g.68a767295 2021-02-16 (11806) 143MB -
installed: 2.9.2-9165-g.b5dc1fd6c (11778) 137MB -