You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/adminguide/extensions/inbuilt_extensions.rst
+23-12Lines changed: 23 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -364,6 +364,7 @@ To set up the MaaS Extension, follow these steps in CloudStack:
364
364
#. **Deploy Instance**
365
365
366
366
Deploy an Instance using the Template created above. The Instance will be provisioned on a randomly selected MaaS machine.
367
+
**maas_system_id** value can be provided in the external details to deploy the instance on specific server.
367
368
368
369
|MaaS-deploy-instance.png|
369
370
@@ -377,40 +378,49 @@ Configuring Networking and additional details
377
378
The MaaS scenarios have been tested and verified with a Shared Network setup in CloudStack, using the MAAS Orchestrator Extension.
378
379
Please find some additional notes with respect to the networking and access related configuration as below,
379
380
381
+
#. **Configuring TFTP to point to MAAS**
382
+
383
+
Ensure that the TFTP or PXE boot configuration (for example, in pfSense or your network’s DHCP server) is set to point to the MAAS server as the TFTP source.
384
+
This ensures that VMs retrieve boot images directly from MAAS during PXE boot.
385
+
380
386
#. **Using CloudStack Virtual Router (VR) as an External DHCP Server**
381
387
382
388
If the end user wants the **CloudStack Virtual Router (VR)** to act as the external DHCP server for instances provisioned through MAAS, the following configuration steps must be performed.
383
389
384
390
**In CloudStack**
385
391
386
-
1. Navigate to **Networks → Add Shared Network**.
387
-
2. Create a Shared Network using the **DefaultSharedNetworkOffering**, and define an appropriate **Guest IP range**.
392
+
a. Navigate to **Networks → Add Shared Network**.
393
+
b. Create a Shared Network using the **DefaultSharedNetworkOffering**, and define an appropriate **Guest IP range**.
388
394
389
395
|CloudStack-shared-network.png|
390
396
391
397
**In MAAS**
392
398
393
-
1. Navigate to **Networking → Subnets → Add Subnet** and create a subnet corresponding to the same IP range used in CloudStack.
399
+
a. Navigate to **Networking → Subnets → Add Subnet** and create a subnet corresponding to the same IP range used in CloudStack.
394
400
395
401
|MaaS-add-subnet-1.png|
396
402
|MaaS-add-subnet-2.png|
397
403
398
-
2. Once the subnet is added:
404
+
b. Once the subnet is added:
399
405
- Ensure **Managed allocation** is **disabled**.
400
406
- Ensure **Active discovery** is **enabled**.
401
407
402
408
|MaaS-subnet-configuration.png|
403
409
404
-
3. Add a **Reserved IP range** that matches the CloudStack Guest range (optional, for clarity).
410
+
c. Add a **Reserved IP range** that matches the CloudStack Guest range (optional, for clarity).
405
411
406
412
|MaaS-add-reserve-iprange.png|
407
413
408
-
4. Disable the DHCP service in MAAS:
414
+
d. Disable the DHCP service in MAAS:
409
415
- Navigate to **Subnets → VLAN → Edit VLAN**.
410
416
- Ensure the **DHCP service** is **disabled**.
411
417
412
418
|MaaS-disable-dhcp.png|
413
419
420
+
e. For all the servers in MAAS, navigate to each server in the Ready state, go to Network → Server Interface → Edit Physical, and set the IP mode to DHCP.
421
+
422
+
|MaaS-enable-dhcp-on-servers.png|
423
+
414
424
This configuration allows the CloudStack Virtual Router (VR) to provide IP address allocation and DHCP services for the baremetal instances managed through MAAS.
415
425
416
426
#. **Using CloudStack-Generated SSH Keys for Baremetal Access**
@@ -419,14 +429,14 @@ Please find some additional notes with respect to the networking and access rela
0 commit comments