Bug 1577992 - [RFE] Satellite 6.3 add "Hypervisor type = Red Hat Enterprise Linux Hypervisor (vdsm)" to generate configuration for "type=vdsm"
Summary: [RFE] Satellite 6.3 add "Hypervisor type = Red Hat Enterprise Linux Hyperviso...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Katello QA List
satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-14 14:55 UTC by vijsingh
Modified: 2021-06-10 16:14 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-15 18:29:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1579677 0 medium CLOSED vsdm config missing for virt-who 2021-02-22 00:41:40 UTC

Internal Links: 1579677

Description vijsingh 2018-05-14 14:55:05 UTC
1. Proposed title of this feature request

  - On Satellite 6.3 add "Hypervisor type = Red Hat Enterprise Linux Hypervisor (vdsm)" to generate configuration for "type=vdsm" 
  - Currently there in no option to select the "Hypervisor type = Red Hat Enterprise Linux Hypervisor (vdsm)" under below path in order to generate the configuration for "type=vdsm" and configure the "virt-who" in "vdsm" mode.

   on Satellite GUI: Infrastructure => 'Virt-who Configurations' => Create Config => Select "Hypervisor type"

   - Unable to create/generate the configuration under Satellite GUI similar type => 'https://access.redhat.com/solutions/2025503' 

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

   Add "Hypervisor type = Red Hat Enterprise Linux Hypervisor (vdsm)" to generate configuration for "type=vdsm" under below:

   on Satellite GUI: Infrastructure => 'Virt-who Configurations' => Create Config => Select "Hypervisor type"

4. Why does the customer need this? (List the business requirements here)

   Currently there in no option to select the "Hypervisor type = Red Hat Enterprise Linux Hypervisor (vdsm)" in order to generate the configuration for "VDSM" type configuration.

5. How would the customer like to achieve this? (List the functional requirements here)

  Add "Hypervisor type = Red Hat Enterprise Linux Hypervisor (vdsm)" to generate configuration for "type=vdsm"

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

   "Hypervisor type = Red Hat Enterprise Linux Hypervisor (vdsm)" should be available under 

      on Satellite GUI: Infrastructure => 'Virt-who Configurations' => Create Config => Select "Hypervisor type = Red Hat Enterprise Linux Hypervisor (vdsm)"

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

    No

8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

   No

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

   No

10. List any affected packages or components.

   virt-who 

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

   yes

Comment 4 Marek Hulan 2018-05-15 07:02:25 UTC
Why vdsm is reqiested if there's rhevm provider? Can't that be used instead?

Comment 11 Bryan Kearney 2018-11-15 18:29:11 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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