Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1694191 - Add ability to allow affinity to include custom checks
Summary: Add ability to allow affinity to include custom checks
Keywords:
Status: NEW
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 4.2.8.1
Hardware: All
OS: Linux
unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: Rob Young
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-29 18:12 UTC by Sam Mingo
Modified: 2019-04-03 14:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Virt
pm-rhel: planning_ack?
pm-rhel: devel_ack?
pm-rhel: testing_ack?


Attachments (Terms of Use)

Description Sam Mingo 2019-03-29 18:12:29 UTC
Description of problem:
We currently have ~20 HV's on RHV, several of which are running on UCS chassises. Several of the HV's are located on the same UCS chassis. This leads to issues where we have anti-affinity rules in place in RHV which force our Openshift masters & infra nodes to never be on the same HV, but we have no anti-affinity rules which guard against the HV's being on the same UCS chassis.

It would be nice if we could enrich the anti-affinity logic that RHV uses with a script to also take additional concerns around our fault domains into the considerations when RHV places VMs on a specific HV. 

Version-Release number of selected component (if applicable):
4.2.8.1

How reproducible:
Always

Steps to Reproduce:
1. Put 2 HV's on same UCS chassis
2. Setup anti-affinity rules to keep nodes away from each other
3. Disable UCS node where 2 of the HV's reside

Actual results:
Leads to outages where we lose quorum on our Openshift master nodes or infra nodes, for example.

Expected results:
Would like the anti-affinity logic to take into account HV's which are on the same underlying H/W and move VMs to satisfy anti-affinity taking this external requirements into account as well.

Additional info:


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