Questo contenuto non è disponibile nella lingua selezionata.
E.3. Websocket Proxy
E.3.1. Websocket Proxy Overview Copia collegamentoCollegamento copiato negli appunti!
The websocket proxy allows users to connect to virtual machines via a noVNC console.
The websocket proxy can be installed and configured on the Red Hat Virtualization Manager machine during the initial configuration (see Configuring the Red Hat Virtualization Manager), or on a separate machine (see Installing a Websocket Proxy on a Separate Machine).
The websocket proxy can also be migrated from the Manager machine to a separate machine. See Section E.3.2, “Migrating the Websocket Proxy to a Separate Machine”.
E.3.2. Migrating the Websocket Proxy to a Separate Machine Copia collegamentoCollegamento copiato negli appunti!
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.
For security or performance reasons the websocket proxy can run on a separate machine that does not run the Red Hat Virtualization Manager. The procedure to migrate the websocket proxy from the Manager machine to a separate machine involves removing the websocket proxy configuration from the Manager machine, then installing the proxy on the separate machine.
The engine-cleanup command can be used to remove the websocket proxy from the Manager machine:
Removing the Websocket Proxy from the Manager machine
On the Manager machine, run
engine-cleanupto remove the required configuration.engine-cleanup
# engine-cleanupCopy to Clipboard Copied! Toggle word wrap Toggle overflow Type
Nowhen asked to remove all components and pressEnter.Do you want to remove all components? (Yes, No) [Yes]: No
Do you want to remove all components? (Yes, No) [Yes]: NoCopy to Clipboard Copied! Toggle word wrap Toggle overflow Type
Nowhen asked to remove the engine and pressEnter.Do you want to remove the engine? (Yes, No) [Yes]: No
Do you want to remove the engine? (Yes, No) [Yes]: NoCopy to Clipboard Copied! Toggle word wrap Toggle overflow Type
Yeswhen asked to remove the websocket proxy and pressEnter.Do you want to remove the WebSocket proxy? (Yes, No) [No]: Yes
Do you want to remove the WebSocket proxy? (Yes, No) [No]: YesCopy to Clipboard Copied! Toggle word wrap Toggle overflow Select
Noif asked to remove any other components.
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.
Procedure
Install the websocket proxy:
yum install ovirt-engine-websocket-proxy
# yum install ovirt-engine-websocket-proxyCopy to Clipboard Copied! Toggle word wrap Toggle overflow Run the
engine-setupcommand to configure the websocket proxy.engine-setup
# engine-setupCopy to Clipboard Copied! Toggle word wrap Toggle overflow NoteIf the
rhvmpackage has also been installed, chooseNowhen asked to configure the Manager (Engine) on this host.Press
Enterto allowengine-setupto configure a websocket proxy server on the machine.Configure WebSocket Proxy on this machine? (Yes, No) [Yes]:
Configure WebSocket Proxy on this machine? (Yes, No) [Yes]:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Press
Enterto accept the automatically detected host name, or enter an alternative host name and pressEnter. 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]:
Host fully qualified DNS name of this server [host.example.com]:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Press
Enterto allowengine-setupto configure the firewall and open the ports required for external communication. If you do not allowengine-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]:
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]:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Enter the FQDN of the Manager machine and press
Enter.Host fully qualified DNS name of the engine server []: manager.example.com
Host fully qualified DNS name of the engine server []: manager.example.comCopy to Clipboard Copied! Toggle word wrap Toggle overflow Press
Enterto allowengine-setupto perform actions on the Manager machine, or press2to 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) [1]:
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) [1]:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Press
Enterto accept the default SSH port number, or enter the port number of the Manager machine.ssh port on remote engine server [22]:
ssh port on remote engine server [22]:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Enter the root password to log in to the Manager machine and press
Enter.root password on remote engine server engine_host.example.com:
root password on remote engine server engine_host.example.com:Copy to Clipboard Copied! Toggle word wrap Toggle overflow
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]:
Generated iptables rules are different from current ones. Do you want to review them? (Yes, No) [No]:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Press
Enterto confirm the configuration settings.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Instructions are provided to configure the Manager machine to use the configured websocket proxy.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Log in to the Manager machine and execute the provided instructions.
engine-config -s WebSocketProxy=host.example.com:6100 systemctl restart ovirt-engine.service
# engine-config -s WebSocketProxy=host.example.com:6100 # systemctl restart ovirt-engine.serviceCopy to Clipboard Copied! Toggle word wrap Toggle overflow