Appendix F. Installing a Websocket Proxy on a Separate Machine
The websocket proxy and noVNC are Technology Preview features only. Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information see Red Hat Technology Preview Features Support Scope.
The websocket proxy allows users to connect to virtual machines through a noVNC console. The noVNC client uses websockets to pass VNC data. However, the VNC server in QEMU does not provide websocket support, so a websocket proxy must be placed between the client and the VNC server. The proxy can run on any machine that has access to the network, including the the Manager machine.
For security and performance reasons, users may want to configure the websocket proxy on a separate machine.
This section describes how to install and configure the websocket proxy on a separate machine that does not run the Manager. See Section 2.3, “Configuring the Red Hat Virtualization Manager” for instructions on how to configure the websocket proxy on the Manager.
Installing and Configuring a Websocket Proxy on a Separate Machine
Install the websocket proxy:
# yum install ovirt-engine-websocket-proxy
engine-setupcommand to configure the websocket proxy.
rhvmpackage has also been installed, choose
Nowhen asked to configure the Manager (
Engine) on this host.
engine-setupto configure a websocket proxy server on the machine.
Configure WebSocket Proxy on this machine? (Yes, No) [Yes]:
Enterto accept the automatically detected host name, or enter an alternative host name and press
Enter. Note that the automatically detected host name may be incorrect if you are using virtual hosts:
Host fully qualified DNS name of this server [host.example.com]:
engine-setupto configure the firewall and open the ports required for external communication. If you do not allow
engine-setupto modify your firewall configuration, then you must manually open the required ports.
Setup can automatically configure the firewall on this system. Note: automatic configuration of the firewall may overwrite current settings. Do you want Setup to configure the firewall? (Yes, No) [Yes]:
Enter the fully qualified DNS name of the Manager machine and press
Host fully qualified DNS name of the engine server : engine_host.example.com
engine-setupto perform actions on the Manager machine, or press
2to manually perform the actions.
Setup will need to do some actions on the remote engine server. Either automatically, using ssh as root to access it, or you will be prompted to manually perform each such action. Please choose one of the following: 1 - Access remote engine server using ssh as root 2 - Perform each action manually, use files to copy content around (1, 2) :
Enterto accept the default SSH port number, or enter the port number of the Manager machine.
ssh port on remote engine server :
Enter the root password to log in to the Manager machine and press
root password on remote engine server engine_host.example.com:
Select whether to review iptables rules if they differ from the current settings.
Generated iptables rules are different from current ones. Do you want to review them? (Yes, No) [No]:
Enterto confirm the configuration settings.
--== CONFIGURATION PREVIEW ==-- Firewall manager : iptables Update Firewall : True Host FQDN : host.example.com Configure WebSocket Proxy : True Engine Host FQDN : engine_host.example.com Please confirm installation settings (OK, Cancel) [OK]:
Instructions are provided to configure the Manager machine to use the configured websocket proxy.
Manual actions are required on the engine host in order to enroll certs for this host and configure the engine about it. Please execute this command on the engine host: engine-config -s WebSocketProxy=host.example.com:6100 and than restart the engine service to make it effective
Log in to the Manager machine and execute the provided instructions.
# engine-config -s WebSocketProxy=host.example.com:6100 # systemctl restart ovirt-engine.service