Add support for OpenStack hypervisor-specific VNC console access #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This support adds a new way to access the grahical console of any VDI instance and provide it to web clients via Guacamole. In addition to the available standard console access of the integrated RDP server from each VDI instance, the hypervisor's VNC console from OpenStack can now be used as an alternative. The alternative offers the advantage that the graphic output can already be accessed during the boot process of a VDI instance. In addition, this option saves resources, since no extra RDP server has to run in each deployed VDI instance.
The new OpenStack VNC console access can be selected via the new configuration option
by assigning the value 'openstack_hypervisor'. The prerequisite for activating the OpenStack VNC console access is that an OpenStack-based cloud is set up with the console type 'noVNC'.