Bug 1082189 - [RFE] Implement update manager for RHEV
Summary: [RFE] Implement update manager for RHEV
Keywords:
Status: CLOSED DUPLICATE of bug 1016839
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-29 00:03 UTC by Bryan Yount
Modified: 2019-10-10 09:18 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-30 06:26:22 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 770493 0 None None None Never

Description Bryan Yount 2014-03-29 00:03:37 UTC
3. What is the nature and description of the request?  

A RHEV admin needs the ability to schedule maintenance/upgrade cycles for RHEV hypervisors or RHEL-based hosts.


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

Currently, upgrading a hypervisor is a very manual process where the host needs to be placed into maintenance, wait for all VMs to migrate off, then click the "Upgrade" button, then repeat the process for the other hosts.


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

Implement an update manager tab or functionality in the Admin Portal or as a separate page.


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

RHEV 3.6

  
10. List any affected packages or components.  

ovirt-engine-webadmin-portal
ovirt-engine-backend


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

Yes

Comment 2 Itamar Heim 2014-03-30 06:26:22 UTC

*** This bug has been marked as a duplicate of bug 1016839 ***


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