Skip to content

Commit 19124f3

Browse files
committed
review
Signed-off-by: Abhishek Kumar <[email protected]>
1 parent ed0f119 commit 19124f3

File tree

3 files changed

+5
-3
lines changed

3 files changed

+5
-3
lines changed

source/adminguide/extensions.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ An Orchestrator extension enables CloudStack to delegate VM orchestration to an
6666

6767
- Instance Lifecycle Support: Orchestrator extensions can handle basic VM actions like prepare, deploy, start, stop, reboot, status and delete.
6868

69-
- Console Access: Instances can be accessed either via VNC consoles or through a direct URL, depending on the capabilities of the orchestrator extension. CloudStack retrieves console details from extensions using the ``getconsole`` action and either forwards them to the Console Proxy VM (CPVM) (for VNC access) or provides the direct console URL to the user. Out of the box, only the built-in Proxmox extension supports console access for instances.
69+
- Console Access: Instances can be accessed either via VNC consoles or through a direct URL, depending on the capabilities of the orchestrator extension. CloudStack retrieves console details from extensions using the ``getconsole`` action and either forwards them to the Console Proxy VM (CPVM) (for VNC access) or provides the direct console URL to the user. Since 4.22.0, out-of-the-box console access support is available for instances deployed using the in-built Proxmox extension. See :ref:`Console Access for Instances with Orchestrator Extensions <console-access-for-instances-with-orchestrator-extensions>`for details on adding console access support in developed extensions.
7070

7171
- Configuration Details: Key-value configuration details can be specified at different levels - extension, cluster mapping, host, template, service offering, instance.
7272

source/adminguide/extensions/inbuilt_extensions.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,8 @@ The Proxmox CloudStack Extension is written in shell script and communicates wit
3333

3434
Before using the Proxmox Extension, ensure that the Proxmox Datacenter is configured correctly and accessible to CloudStack.
3535

36+
Since 4.22.0, console access support is available for instances deployed using the in-built Proxmox extension via VNC and console proxy VM.
37+
3638
Get the API Token-Secret from Proxmox
3739
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3840

@@ -161,6 +163,8 @@ using NTLM authentication for secure remote execution of PowerShell commands tha
161163

162164
Each Hyper-V host maps to a CloudStack Host. Before using the Hyper-V Extension, ensure that the Hyper-V host is accessible to the CloudStack Management Server via WinRM over HTTPS.
163165

166+
Console access for instances using the Hyper-V extension is not available out of the box.
167+
164168
Configuring WinRM over HTTPS
165169
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
166170

source/adminguide/extensions/limitations.rst

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,6 @@ by adding custom actions in the scripts written for the built-in extensions.
3838

3939
- Add Nics to Instance post deployment.
4040

41-
- Console access for instances using the built-in Hyper-V orchestrator is not available out of the box.
42-
4341
**Actions which can be implemented using Custom Actions in built-in extensions:**
4442

4543
- Reinstall Instance.

0 commit comments

Comments
 (0)