Bug 1468742 - [RFE] Allow Satellite user to choose between VNC, SPICE for Display type on RHEV compute resources
[RFE] Allow Satellite user to choose between VNC, SPICE for Display type on R...
Status: NEW
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Compute Resources - RHEV (Show other bugs)
Unspecified All
unspecified Severity low (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
Katello QA List
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-07-07 15:33 EDT by Pablo Hess
Modified: 2018-01-30 08:57 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pablo Hess 2017-07-07 15:33:50 EDT
1. Proposed title of this feature request:
Offer Display type choice between SPICE and VNC for RHEV compute resources

2. Who is the customer behind the request?

This information will be provided as a private comment.

3. What is the nature and description of the request?

With RHEV registered on Satellite 6.2.10 as a compute resource, SPICE is used as Display type. No questions asked, no other options offered.

Customer uses VNC by default on their RHV infrastructure, but Satellite will always set new RHV guests to SPICE.

Customer would like to be able to choose VNC instead of SPICE.

For comparison purposes, libvirt compute resource allows the user to choose between VNC and SPICE.

4. Why does the customer need this?

Customer uses VNC by default as Display type on RHV when spinning new VMs on this RHV. This is a requirement for their standard environment.

5. How would the customer like to achieve this?

On the webUI, navigate to Infrastructure > Compute resources.
Click "Edit" next to a RHEV compute resource and change Display type from SPICE to VNC.

This is precisely what libvirt compute resources offer as of today.

With hammer this would be accomplished the same way as libvirt offers this switch:
# hammer compute-resource update --id <ID> --display-type VNC

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Both webUI and hammer can be tested by the customer.
Customer has a sandbox environment where they can test new things before going to production.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
This looks like an extension of this 5 year old upstream RFE: http://projects.theforeman.org/issues/1637

8. Does the customer have any specific timeline dependencies and which release would they like to target?
As soon as possible but this is not critical. This is significantly convenient.
While this new setting is not available the customer must go to RHEV and set the display type of each individual guest to VNC when the guest is provisioned.

9. Is the sales team involved in this request and do they have any additional input?


10. List any affected packages or components.

Foreman, hammer, RHEV compute resources.

11. Would the customer be able to assist in testing this functionality if implemented?


Note You need to log in before you can comment on or make changes to this bug.