Skip to content

Commit 28a41cc

Browse files
committed
another fix
Signed-off-by: Abhishek Kumar <[email protected]>
1 parent d6e7c67 commit 28a41cc

File tree

2 files changed

+7
-6
lines changed

2 files changed

+7
-6
lines changed

source/adminguide/extensions.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ In the UI, extensions can be managed under *Extensions* menu.
2424
|extensions.png|
2525

2626
Overview
27-
~~~~~~~~
27+
^^^^^^^^
2828

2929
An extension in CloudStack is defined as an external binary (written in any programming language) that implements specific actions CloudStack can invoke. This allows operators to manage resource lifecycle operations outside CloudStack, such as provisioning VMs in third-party systems or triggering external automation pipelines.
3030

@@ -33,7 +33,7 @@ Extensions are managed through the API and UI, with support for configuration, r
3333
|create-extension.png|
3434

3535
Configuration
36-
~~~~~~~~~~~~~
36+
^^^^^^^^^^^^^
3737

3838
Administrators can define and manage the following components of an extension:
3939

@@ -44,19 +44,19 @@ Administrators can define and manage the following components of an extension:
4444
- Resource Mappings: Association between extensions and CloudStack resources such as clusters, etc.
4545

4646
Entry Point
47-
~~~~~~~~~~~
47+
^^^^^^^^^^^
4848

4949
The entry point for an extension can be any binary or executable script. If no explicit entry point is provided, CloudStack uses a default base Bash script. The state of the entry point is validated across all management servers. In the UI, the Entry Point State is displayed as Not Ready if the file is missing, inaccessible, or differs across management servers.
5050

5151
All extension entry point files are stored under a directory named after the extension within `/usr/share/cloudstack-management/extensions`.
5252

5353
Payload
54-
~~~~~~~
54+
^^^^^^^
5555

5656
CloudStack sends structured JSON payloads to the extension binary during each operation. These payloads are written to .json files stored under `/var/lib/cloudstack/management/extensions`. The extension binary is expected to read the file and return an appropriate result. CloudStack automatically attempts to clean up payload files older than one day.
5757

5858
Orchestrator Extension
59-
~~~~~~~~~~~~~~~~~~~~~~
59+
----------------------
6060

6161
An Orchestrator extension enables CloudStack to delegate VM orchestration to an external system. Key features include:
6262

source/adminguide/extensions/custom_actions.rst

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,8 +43,9 @@ A single parameter can have the following details:
4343

4444
- **valueoptions**: Options for the value of the parameter. This is allowed only for NUMBER and STRING type.
4545

46+
4647
Running Custom Action
47-
~~~~~~~~~~~~~~~~~~~~~
48+
^^^^^^^^^^^^^^^^^^^^^
4849

4950
All enabled custom actions can then be triggered for a resource of the type the action is defined for or provided while running, using the **Run Action** view or runCustomAction API.
5051

0 commit comments

Comments
 (0)