Bug 1443989

Hello everybody!

I don't think removing SPICE HTML5 support is good idea. It is the simpliest way to get SPICE console using only web browser. virt-viewer is another app which I need to have installed first. virt-viewer doesn't support web socket proxy. I am not shure "alpha-quality support" is better than SPICE HTML5. IMHO it will be better to give some support to SPICE HTML5 or at least keep it as is.

(In reply to Vladimir Rulev from comment #10)
> Hello everybody!
> 
> I don't think removing SPICE HTML5 support is good idea. It is the simpliest
> way to get SPICE console using only web browser. virt-viewer is another app
> which I need to have installed first. virt-viewer doesn't support web socket
> proxy. I am not shure "alpha-quality support" is better than SPICE HTML5.
> IMHO it will be better to give some support to SPICE HTML5 or at least keep
> it as is.

it's just the integration bits which are being removed, you can still set up and run spice-html5 project from upstream independently, a custom integration for your specific case is likely scriptable. It's just that we're not interested in maintaining it globally for all the cases in oVirt, unfortunately that project is external to oVirt and we do not influence its development.

There are other alternatives too, not just to use virt-viewer directly. You can use SPICE+VNC display type and a custom vnc client, or novnc if you for whatever reason require a web socket proxy.
Or SPICE proxy + virt-viewer if you need a squid-based proxy.

(In reply to Michal Skrivanek from comment #11)
> (In reply to Vladimir Rulev from comment #10)
> > Hello everybody!
> > 
> > I don't think removing SPICE HTML5 support is good idea. It is the simpliest
> > way to get SPICE console using only web browser. virt-viewer is another app
> > which I need to have installed first. virt-viewer doesn't support web socket
> > proxy. I am not shure "alpha-quality support" is better than SPICE HTML5.
> > IMHO it will be better to give some support to SPICE HTML5 or at least keep
> > it as is.
> 
> it's just the integration bits which are being removed, you can still set up
> and run spice-html5 project from upstream independently, a custom
> integration for your specific case is likely scriptable. It's just that
> we're not interested in maintaining it globally for all the cases in oVirt,
> unfortunately that project is external to oVirt and we do not influence its
> development.
> 
> There are other alternatives too, not just to use virt-viewer directly. You
> can use SPICE+VNC display type and a custom vnc client, or novnc if you for
> whatever reason require a web socket proxy.
> Or SPICE proxy + virt-viewer if you need a squid-based proxy.

Michal, I don't think it is my specific case. I suppose many oVirt users need it as well. Is it possible to discuss removal of SPICE HTML5 publicly? Can you make survey on ovirt.org home page? Because I have found this bug accidentally and I'm afraid most of users miss it and will face this change only after upgrade to 4.2.

About alternatives: AFAIK novnc is external project to oVirt as well, and it has it's own bugs. Do you plan to drop it next to SPICE HTML5?

Hi, Michal

Can you tell what is the final result? Is spice-html5 is going be removed from oVirt?

yes, the integration is removed already in 4.2
We do not plan to deprecate or remove novnc (though beware we didn't yet update the integration to work with latest available novnc version upstream - bug 1502652, bug 1475845)

requires documentation

The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Verified on 
RHEVM version : 4.2.0.2-0.1.el7

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:1488

This feature breaks the spice html5 console in other redhat products like Cloudforms and Satellite 6 which previously were able to connect to the remote console over html5?

(In reply to Greg Procunier from comment #22)
> This feature breaks the spice html5 console in other redhat products like
> Cloudforms and Satellite 6 which previously were able to connect to the
> remote console over html5?

no. This is about the integrated spice-html5 inside RHV GUI only. See comment #11. Even the websocket proxy in the middle still says the same and is protocol agnostic, though IIRC CFME is not using that one either.

Though you need to really check/ask the respective products about the level of their support.

BZ<2>Jira Resync