Red Hat Bugzilla – Bug 1032584
[RFE] spice proxy support at cluster/vm-pool granularity
Last modified: 2014-03-31 11:05:55 EDT
3.2 added spice proxy support as a global config. This RFE is to extend the support to allow configuration spice proxy per cluster, and per vm-pool (vm-pool configuration will override the cluster level if defined).
Will there be added a possibility to automatically enable/disable the spice proxy based on where the user is accessing the User Portal from?
We're evaluating Ovirt/RHEV for RHEL Client VDI and how we can access the Linux VDI machines from outside our LAN. We are required to accomplish this using a SSLVPN device having 2 factor autentication to satisfy company policy.
However when the users access the VDI's from inside the LAN this proxy will not be available to them. Hence the request to be able to switch the spice proxy on/off for each session the user creates to the user portal, depending on if he's logging in from inside the network or remotely through the SSLVPN device.
This is functionality already found in other similar products. Asking the users to enable/disable the spice proxy manually will generate phone calls to our helpdesk and not be very user friendly.
oVirt 3.4.0 alpha has been released including the fix for this issue.
Moving to verified, based on test plan passed on rhevm 3.4 av2: https://tcms.engineering.redhat.com/run/119097/?from_plan=12341
This is an automated message: moving to Closed CURRENT_RELEASE since oVirt 3.4.0 has been released.