Re: [ovirt-users] accessing SPICE console when host not on management network

On Apr 3, 2015, at 08:35 , shimano wrote: > That's why I recommend squid. Without that you should make port forwarding on > your network's gateway (router). But Spice consoles working on the same port > and you can't make port forwarding to few different hosts on the same port. > > I gave you

Re: [ovirt-users] accessing SPICE console when host not on management network

That's why I recommend squid. Without that you should make port forwarding on your network's gateway (router). But Spice consoles working on the same port and you can't make port forwarding to few different hosts on the same port. I gave you a complete working solution. If you don't like to use VP

Re: [ovirt-users] accessing SPICE console when host not on management network

You call all of that configuration for accessing consoles, easy? :) :) Engine should be able to set up the proxy automatically... I haven't used squid, so I have to look in more detail at the configuration that you've provided. I did find some other functionality which would have been much

Re: [ovirt-users] accessing SPICE console when host not on management network

You can use Spice Proxy. The easiest way is to run proxy on Squid. I recommend connect via VPN. Here is a part of my Squid's configuration to connect Spice consoles from VPN 10.25.0.0/16 and LAN 192.168.0.0/16 to oVirt's hosts on 192.168.2.0/24: acl manager proto cache_object acl localhost src 12

[ovirt-users] accessing SPICE console when host not on management network

I'm trying to figure out the most reasonable method for me to access the console on my ovirt installation. Each node has ovirtmgmt, storage, and external network connectivity. The standalone engine host has ovirtmgmt, and external network. I connect to engine via the external network, right click