Bug 1332469

Summary:	[RFE]Include spice-html5 package in RHOS7 and RHOS8 repositories
Product:	Red Hat OpenStack	Reporter:	Chaitanya Shastri <cshastri>
Component:	spice-html5	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED WONTFIX	QA Contact:	Shai Revivo <srevivo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	eglynn, sacpatil, sgordon, srevivo
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-05 19:14:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Chaitanya Shastri 2016-05-03 09:32:43 UTC

Description of problem:

For an OpenStack instance, by default, a VNC console is enabled.

If I want to switch over to Spice console for the spawned instances, I need to perform some configuration changes in nova.conf file on compute and controller nodes like enabling the spice related features and enabling the spice agent. Also, I need to install two packages if I need to enable Spice console for the spawned instances:

1. spice-html5
2. openstack-nova-spicehtml5proxy

The second package 'openstack-nova-spicehtml5proxy' is present in 'rhel-7-server-openstack-7.0-rpms' repository. But 'spice-html5' (spice-html5-0.1.6-2.el7.noarch.rpm) package is a part of 'rhel-7-server-rhev-mgmt-agent-for-power-le-rpms' repository (https://access.redhat.com/downloads/content/spice-html5/0.1.6-2.el7/noarch/fd431d51/package) which is not accessible by the users that are subscribed to the required channels for installing RHOS7 and RHOS8.

I have tried manually installing the package 'spice-html5-0.1.6-2.el7.noarch.rpm' by downloading it manually from the channel and it works perfectly well.

So, shouldn't  the package 'spice-html5' (spice-html5-0.1.6-2.el7.noarch.rpm) be a part of RHOS7 and RHOS8 channels so that every user subscribed to these channels is able to access it?


Version-Release number of selected component (if applicable):

RHOS7
RHOS8

How reproducible:

100%

Steps to Reproduce:

Enable appropriate RHOS channels for installation and search for spice-html5 package.

Actual results:

spice-html5 package is not present in RHOS channels.


Expected results:

spice-html5 package should be present in RHOS repositories.

Additional info:

I have tried manually installing the package 'spice-html5-0.1.6-2.el7.noarch.rpm' by downloading it manually from the channel and it works perfectly well.

Comment 2 Chaitanya Shastri 2016-05-03 12:54:23 UTC

Also please consider including the package in RHOS6 repositories.

Comment 3 Stephen Gordon 2016-05-05 19:14:21 UTC

(In reply to cshastri from comment #0)

> I have tried manually installing the package
> 'spice-html5-0.1.6-2.el7.noarch.rpm' by downloading it manually from the
> channel and it works perfectly well.

What happens when, for example, you press ctrl-alt-del in a Windows guest to try get to the login screen?

> So, shouldn't  the package 'spice-html5'
> (spice-html5-0.1.6-2.el7.noarch.rpm) be a part of RHOS7 and RHOS8 channels
> so that every user subscribed to these channels is able to access it?

No, it was explicitly removed it from RHOSP under Bug # 956434 due to outstanding issues in spice-html5 and the lack of available resources to fix them. Its omission is not accidental.

We have no plans to add spice-html5 to RHOSP at this time. I am however in discussions with my counterparts in RHEL virtualization to determine how and when we might go about adding support for the full SPICE client (not spice-html5).

Comment 4 Stephen Gordon 2016-05-05 19:32:21 UTC

Looking at the case it also seems like what they want is not in fact spice-html5 but the full SPICE client similar to that provided by RHEV. We currently do not support this in OpenStack (the underlying enablement isn't there) but if you can re-frame correctly the request then we can consider it.

Comment 5 Sachin 2016-05-06 10:10:48 UTC

I completely agree that we don't fully support spice-html5 in RHOSP. But it doesn't make any sense to subscribe to RHEV just to install a single package. Please also consider that we have 'openstack-nova-spicehtml5proxy' included in RHOSP but not 'spice-html5'.

Can't we include 'spice-html5' in RHOSP but limit the support? We can update documentation or create KCS article on 'Installing and configuring spice in RHOSP'. The documentation will help customers to integrate spice and prevent cases like this in the future.