Is there documentation of tech preview 'WebSocket proxy'?
I have RHEV in a lab where vnc and spice protocols are prevented from leaving the lab directly.
The tech preview and some other documentation mentions the 'WebSocket' proxy but I don't have
a clue what exactly that entails. Upstream Ovirt doc is slightly more enlightening, but not by
much.
Is there a pointer to an example setup?
Responses
Hey Richard, thanks for the question. I am one of the Virtualization specialists here so I thought I would answer your question. The guides are a bit sparse on this feature at the moment because of its tech preview nature. However, I will point you to a section in the Appendix that probably should be moved up to the installation steps (I'm filing a docs bug on this now):
RHEV 3.3 Installation Guide: Squid Proxy - Step 6
To use the noVNC or Spice HTML 5 consoles to connect to the console of virtual machines,enable the
websockets proxy server in the engine machine. Make sure that the ovirt-engine-websocket-proxy
package was installed prior to installing the engine, otherwise it won't be correctly configured.
If you missed that step during installation, there should be a way to get a proper configuration after the fact but at this time it is not known. If you would, please open a support case and point to this discussion. I will work with the case owner to figure this out.
Knowledge solution 718653 was created to document the procedure for installing and configuring the WebSockets Proxy.
In my case, the webproxy server ends up in
I'm unable to force it to log anything.
Hey Richard. It sounds like you were able to get the RHEV-M (Admin Portal or User Portal) to display using the Squid proxy. However, the WebSocketProxy will not work via the Squid proxy at the current time. The WebSocketProxy is only to allow the HTML5 clients to work. If you're having an issue with that, please open a support case and reference this discussion thread.
I also updated the knowledge solution 718653 with some diagnostic steps to check to make sure the service is configured and running with the port open on the firewall. Clients need direct access to the RHEV-M over that port to use the HTML5 spice or vnc display.
Edit: Yeah, I agree about that section of the docs being a little confusing. I'm working with the docs team to enhance that section via the support case you opened.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
