-
Notifications
You must be signed in to change notification settings - Fork 119
Added documentation for MaaS Extension #561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Added documentation for MaaS Extension #561
Conversation
@blueorangutan docbuild |
@harikrishna-patnala a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/561. (QA-JID 424) |
@@ -79,7 +79,7 @@ An Orchestrator extension enables CloudStack to delegate VM orchestration to an | |||
|extension.png| | |||
|
|||
|
|||
CloudStack provides in-built Orchestrator Extensions for Proxmox and Hyper-V which work with Proxmox and Hyper-V environments out of the box. | |||
CloudStack provides in-built Orchestrator Extensions for Proxmox, Hyper-V, MaaS which work with Proxmox, Hyper-V and MaaS environments out of the box. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe reword to "CloudStack provides in-build Orchestrator Extensions for Proxmox, Hyper-V and MaaS which work with their respective environments out of the box.
CloudStack provides in-built Orchestrator Extensions for Proxmox, Hyper-V and MaaS. These extensions work with Proxmox, Hyper-V and MaaS environments out of the box, and can also serve as reference implementations for anyone looking to develop new custom extensions. | ||
The Extension files are located at `/usr/share/cloudstack-management/extensions/Proxmox`, `/usr/share/cloudstack-management/extensions/HyperV` and `/usr/share/cloudstack-management/extensions/MaaS` respectively. | ||
The Proxmox Extension is written in shell script, while the Hyper-V and MaaS Extensions are written in python. | ||
All of these Extensions support some custom actions in addition to the standard VM actions like deploy, start, stop, reboot, status and delete. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MaaS doesn't have any custom actions, right?
Can modify this to "Proxmox and Hyper-V Extensions support some custom actions ..."
The Proxmox Extension is written in shell script, while the Hyper-V Extension is written in python. | ||
Both of these Extensions support some custom actions in addition to the standard VM actions like deploy, start, stop, reboot, status and delete. | ||
CloudStack provides in-built Orchestrator Extensions for Proxmox, Hyper-V and MaaS. These extensions work with Proxmox, Hyper-V and MaaS environments out of the box, and can also serve as reference implementations for anyone looking to develop new custom extensions. | ||
The Extension files are located at `/usr/share/cloudstack-management/extensions/Proxmox`, `/usr/share/cloudstack-management/extensions/HyperV` and `/usr/share/cloudstack-management/extensions/MaaS` respectively. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Extension files are located at `/usr/share/cloudstack-management/extensions/Proxmox`, `/usr/share/cloudstack-management/extensions/HyperV` and `/usr/share/cloudstack-management/extensions/MaaS` respectively. | |
The Extension files are located in `/usr/share/cloudstack-management/extensions/`, under the subdirectories `Proxmox`, `HyperV`, and `MaaS`. |
MaaS | ||
^^^^^^^^ | ||
|
||
The MaaS CloudStack Extension is written in python script and communicates with the Canonical MaaS `https://canonical.com/maas`_ using the MaaS APIs `https://canonical.com/maas/docs/api`_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure, but the
doesn't look right here. Also check if the links display is better with the suggestion.

The MaaS CloudStack Extension is written in python script and communicates with the Canonical MaaS `https://canonical.com/maas`_ using the MaaS APIs `https://canonical.com/maas/docs/api`_. | |
The MaaS CloudStack Extension is written in python script and communicates with `Canonical MaaS <https://canonical.com/maas`_ using the `MaaS APIs <https://canonical.com/maas/docs/api>`_. |
Please make the change to Proxmox API link as well on line #32
The Proxmox CloudStack Extension is written in shell script and communicates with the Proxmox Cluster using the `Proxmox VE API <https://pve.proxmox.com/wiki/Proxmox_VE_API>`_ over HTTPS."
|
||
If not already set up, create a new API Key in the MaaS UI by navigating to left column under `admin > API keys`. | ||
|
||
Existing `MAAS consumer` token can used or a new API key can be generated by clicking `Generate MAAS API Key` button |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Existing `MAAS consumer` token can used or a new API key can be generated by clicking `Generate MAAS API Key` button | |
Existing `MAAS consumer` token can be used or a new API key can be generated by clicking the `Generate MAAS API Key` button |
|
||
#. **Deploy Instance** | ||
|
||
Deploy an Instance using the Template created above. Optionally, provide the detail `vm_name` to specify the name of the VM in MaaS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please check if we should call it VM or some generic term like system or machine
This add content in relation to the PR apache/cloudstack#11613
📚 Documentation preview 📚: https://cloudstack-documentation--561.org.readthedocs.build/en/561/