Part of a series: Install · Configure · DHCP · Commission · Deploy · jq · SSH · More jq


Acquiring a machine

Once commissioning finishes, acquire the machine — this assigns ownership to your username:

stormrider@wintermute:~$ maas admin machines allocate system_id=bhxws3

Key fields in the response confirm the machine is ready to deploy:

  • "status_name": "Allocated" — now owned by admin
  • "ip_addresses": ["192.168.123.190"] — DHCP assigned an address
  • "commissioning_status_name": "Passed" — all tests cleared
  • "storage_test_status_name": "Passed" — disk tests passed
  • "power_state": "off" — waiting for deploy command

Deploying the machine

Having acquired the machine, deploy it:

stormrider@wintermute:~$ maas admin machine deploy bhxws3

The response confirms deployment is underway:

  • "status_name": "Deploying" — OS install in progress
  • "status_message": "Deploying" — confirmed
  • "distro_series": "bionic" — deploying Ubuntu 18.04
  • "hwe_kernel": "ga-18.04" — hardware enablement kernel
  • "current_installation_result_id": 10 — install result being tracked

What just happened

In sequence, via CLI only:

  1. Installed and configured MAAS
  2. Started DHCP
  3. Created a machine
  4. Commissioned it
  5. Acquired it
  6. Deployed it

No UI touched.

Next up: using jq to make CLI output human-readable.