update

Signed-off-by: Abhishek Kumar <[email protected]>

Author: shwstppr

source/adminguide/extensions.rst

@@ -66,7 +66,7 @@ An Orchestrator extension enables CloudStack to delegate VM orchestration to an
 
    - Instance Lifecycle Support: Orchestrator extensions can handle basic VM actions like prepare, deploy, start, stop, reboot, status and delete.
 
-   - Console Access: Instances can be accessed via VNC consoles. CloudStack retrieves console details from extensions using the ``getconsole`` action, and forwards them to the Console Proxy VM (CPVM) to provide users with console access. Currently, the built-in Proxmox extension supports console access for instances.
+   - 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.
 
    - Configuration Details: Key-value configuration details can be specified at different levels - extension, cluster mapping, host, template, service offering, instance.
 

source/adminguide/extensions/developer.rst

@@ -125,12 +125,15 @@ Action Lifecycle
 Console Access for Instances with Orchestrator Extensions
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Orchestrator extensions can provide console access for instances via VNC.
-To enable this, the extension must implement the ``getconsole`` action and return output in the following JSON format:
+Orchestrator extensions can provide console access for instances either through **VNC** or a **direct URL**.
+To enable this, the extension must implement the ``getconsole`` action and return output in one of the following JSON formats:
+
+VNC-based console:
 
 .. code-block:: json
 
     {
+      "status": "success",
       ...
       "console": {
         "host": "pve-node1.internal",
@@ -140,8 +143,20 @@ To enable this, the extension must implement the ``getconsole`` action and retur
       }
     }
 
-The returned details are forwarded to the Console Proxy VM (CPVM) running in the same zone as the instance.
-It is required that the specified **host** and **port** are reachable from the CPVM.
+For VNC-based access, the returned details are forwarded to the Console Proxy VM (CPVM) in the same zone as the instance. The specified **host** and **port** must be reachable from the CPVM.  
+
+Direct URL-based console:
+
+.. code-block:: json
+
+    {
+      "status": "success",
+      ...
+      "console": {
+        "url": "CONSOLE_URL",
+        "protocol": "direct"
+      }
+    }
 
 
 Custom Actions

source/adminguide/extensions/limitations.rst

@@ -38,7 +38,7 @@ by adding custom actions in the scripts written for the built-in extensions.
 
    - Add Nics to Instance post deployment.
 
-   - Console access to the in-built Hyper-V orchestrator Instances.
+   - Console access for instances using the built-in Hyper-V orchestrator is not available out of the box.
 
 **Actions which can be implemented using Custom Actions in built-in extensions:**