Bug 1680498 - [RFE] Implement priorities for soft affinity groups
Summary: [RFE] Implement priorities for soft affinity groups
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.2.8-2
Hardware: x86_64
OS: Linux
high
unspecified
Target Milestone: ovirt-4.3.6
: 4.3.6
Assignee: Andrej Krejcir
QA Contact: Polina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-25 08:06 UTC by Steffen Froemer
Modified: 2024-12-20 18:48 UTC (History)
5 users (show)

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.
Clone Of:
Environment:
Last Closed: 2019-10-10 15:36:58 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3010 0 None None None 2019-10-10 15:37:11 UTC
oVirt gerrit 101002 0 master MERGED core: Add priorities to affinity groups 2021-02-08 20:59:11 UTC
oVirt gerrit 101024 0 master MERGED webadmin: Add priority to affinity group dialog and list 2021-02-08 20:59:11 UTC
oVirt gerrit 101027 0 master MERGED Add priority to AffinityGroup type 2021-02-08 20:59:11 UTC
oVirt gerrit 101028 0 master MERGED restapi: Add priority to AffinityGroupMapper 2021-02-08 20:59:11 UTC
oVirt gerrit 101246 0 model_4.3 MERGED Add priority to AffinityGroup type 2021-02-08 20:59:11 UTC
oVirt gerrit 101391 0 master MERGED scheduling: Move affinity code to derived policy units 2021-02-08 20:59:12 UTC
oVirt gerrit 101439 0 master MERGED restapi: Update to model 4.4.3 2021-02-08 20:59:12 UTC
oVirt gerrit 101833 0 master MERGED core: Add more logging to AffinityRulesEnforcer 2021-02-08 20:59:12 UTC
oVirt gerrit 101836 0 ovirt-engine-4.3 MERGED core: Add priorities to affinity groups 2021-02-08 20:59:12 UTC
oVirt gerrit 101837 0 ovirt-engine-4.3 MERGED webadmin: Add priority to affinity group dialog and list 2021-02-08 20:59:12 UTC
oVirt gerrit 101838 0 ovirt-engine-4.3 MERGED restapi: Add priority to AffinityGroupMapper 2021-02-08 20:59:13 UTC
oVirt gerrit 101839 0 ovirt-engine-4.3 MERGED scheduling: Move affinity code to derived policy units 2021-02-08 20:59:13 UTC
oVirt gerrit 101840 0 ovirt-engine-4.3 MERGED core: Add more logging to AffinityRulesEnforcer 2021-02-08 20:59:13 UTC
oVirt gerrit 101863 0 ovirt-engine-4.3 ABANDONED restapi: Update to model 4.3.27 2021-02-08 20:59:13 UTC
oVirt gerrit 101864 0 ovirt-engine-4.3 MERGED restapi: Update to model 4.3.27 2021-02-08 20:59:13 UTC

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


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