@@ -285,6 +285,20 @@ Existing `MAAS consumer` token can be used or a new API key can be generated by
285285
286286Note down the **key ** value.
287287
288+ You can verify the MAAS API key and connectivity from the CloudStack Management Server by using the MAAS CLI as shown below (replace the example values with your own):
289+
290+ .. code-block :: bash
291+
292+ maas login admin http://< MAAS-ENDPOINT> :5240/MAAS < API_KEY>
293+
294+ # Example:
295+ maas login admin http://10.0.80.47:5240/MAAS QqeFTc4fvz9qQyPzGy:UUGKTDf6VwPVDnhXUp:wtAZk6rKeHrFLyDQD9sWcASPkZVSMu6a
296+
297+ # Verify MAAS connectivity and list machines
298+ maas admin machines read | jq ' .[].system_id'
299+
300+ If the connection is successful, the command will list all registered machine system IDs from MAAS.
301+
288302Install required Python libraries
289303~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
290304
@@ -335,24 +349,27 @@ To set up the MaaS Extension, follow these steps in CloudStack:
335349 * **release **: Numeric OS release (e.g., `20.04 `, `22.04 `)
336350 * **architecture **: Image architecture name as listed in MaaS (e.g., `amd64/ga-20.04 `, `amd64/hwe-22.04 `, `amd64/generic `)
337351
352+ MAAS uses only distro_series to identify the operating system for Ubuntu-based images (for example, focal, jammy).
353+ Do not specify both release and distro_series, if both are provided, MAAS will ignore release.
354+
338355 Example configurations:
339356
340357 .. code-block :: text
341358
342- os=ubuntu
343- distro_series=focal
344- release=20.04
345- architecture=amd64/ga-20.04
359+ # Ubuntu 20.04 (Focal)
360+ os=ubuntu
361+ distro_series=focal
362+ architecture=amd64/ga-20.04
346363
347- os=ubuntu
348- distro_series=jammy
349- release=22.04
350- architecture=amd64/hwe-22.04
364+ # Ubuntu 22.04 (Jammy)
365+ os=ubuntu
366+ distro_series=jammy
367+ architecture=amd64/hwe-22.04
351368
352- os=centos
353- distro_series=8
354- release=8
355- architecture=amd64/generic
369+ # CentOS 8
370+ os=centos
371+ release=8
372+ architecture=amd64/generic
356373
357374 |MaaS-add-template.png |
358375
@@ -366,8 +383,8 @@ To set up the MaaS Extension, follow these steps in CloudStack:
366383
367384 Operations **Start **, **Stop **, **Reboot **, and **Delete ** can be performed on the Instance from CloudStack.
368385
369- Additional Notes and Tested Scenarios
370- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
386+ Configuring Networking and additional details
387+ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
371388
372389The MaaS scenarios have been tested and verified with a Shared Network setup in CloudStack, using the MAAS Orchestrator Extension.
373390Please find some additional notes with respect to the networking and access related configuration as below,
@@ -417,8 +434,6 @@ Please find some additional notes with respect to the networking and access rela
417434 1. Navigate to **Compute → SSH Keypairs → Create SSH Keypair **.
418435 2. Save the generated **private key ** for later use (CloudStack stores only the public key).
419436
420- |Cloudstack-create-sshkeypair.png |
421-
422437 **In MAAS **
423438
424439 1. Navigate to **Admin → SSH Keys → Import **.
@@ -456,5 +471,4 @@ Please find some additional notes with respect to the networking and access rela
456471.. |MaaS-subnet-configuration.png | image :: /_static/images/MaaS-subnet-configuration.png
457472.. |MaaS-add-reserve-iprange.png | image :: /_static/images/MaaS-add-reserve-iprange.png
458473.. |MaaS-disable-dhcp.png | image :: /_static/images/MaaS-disable-dhcp.png
459- .. |Cloudstack-create-sshkeypair.png | image :: /_static/images/Cloudstack-create-sshkeypair.png
460474.. |MaaS-add-sshkeypair.png | image :: /_static/images/MaaS-add-sshkeypair.png
0 commit comments