rohityadavcloud commented on code in PR #560: URL: https://github.com/apache/cloudstack-documentation/pull/560#discussion_r2377781265
########## source/adminguide/extensions/developer.rst: ########## @@ -120,7 +120,53 @@ Action Lifecycle 1. A CloudStack action (e.g., deploy VM) triggers a corresponding extension action. 2. CloudStack invokes the extension’s executable with appropriate parameters. 3. The extension processes the input and responds within the timeout. -4. CloudStack continues orchestration based on the result. +4. CloudStack continues action workflow based on the result. + +Console Access for Instances with Orchestrator Extensions +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Orchestrator extensions can provide console access for instances either through **VNC** or a **direct URL**. Review Comment: Here we state that console access can only be VNC or direct/external URL based? Also the word direct is confusing, probably you want to say it's an external URL (or just URL) ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
