Bug 1680498

Summary: [RFE] Implement priorities for soft affinity groups
Product: Red Hat Enterprise Virtualization Manager Reporter: Steffen Froemer <sfroemer>
Component: ovirt-engineAssignee: Andrej Krejcir <akrejcir>
Status: CLOSED ERRATA QA Contact: Polina <pagranat>
Severity: unspecified Docs Contact:
Priority: high    
Version: 4.2.8-2CC: akrejcir, emarcus, pelauter, rbarry, Rhev-m-bugs
Target Milestone: ovirt-4.3.6Keywords: FutureFeature, ZStream
Target Release: 4.3.6   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.6 Doc Type: Enhancement
Doc Text:
A new text field has been added to the affinity group dialog to set priority. It can contain any real number, not just integers. Priority can also be set using a new parameter in the REST API. When a Virtual Machine is started or migrated, a host is selected, with the broken affinity groups having the lowest priority. If not all affinity groups can be satisfied, the groups with lower priority are broken first.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-10 15:36:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Steffen Froemer 2019-02-25 08:06:48 UTC 
1. Proposed title of this feature request
Implement priorities for soft affinity groups


3. What is the nature and description of the request?
In large environments, there is the requirement to have more than a single affinity group configured for VMs. 


4. Why does the customer need this? (List the business requirements here)
Customer require to create more complex affinity rule set. 

5. How would the customer like to achieve this? (List the functional requirements here)
Set priority of a affinity group


6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
If affinity group priority is set and a VM is assigned to both, the one with higher priority will be applied.


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


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


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


10. List any affected packages or components.
ovirt-engine


11. Would the customer be able to assist in testing this functionality if implemented?
sure
Comment 4 Polina 2019-08-08 17:07:03 UTC 
verified according to the attached polarion cases on ovirt-engine-4.3.6-0.1.el7.noarch
Comment 8 errata-xmlrpc 2019-10-10 15:36:58 UTC 
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-2019:3010