Greetings users and developers, The feature I'm developing "Affinity Rules Enforcement Service" has been updated and is now called "Affinity Rules Enforcement Manager". It's a small change that now reflects the way AREM should be used. Also, The wiki page itself has been updated.
You may see it in: http://www.ovirt.org/Affinity_Rules_Enforcement_Manager The feature page is a respond to RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1112332 Your comments appreciated. ----- Original Message ----- From: "Tomer Saban" <[email protected]> To: [email protected], [email protected] Sent: Wednesday, April 22, 2015 3:22:29 PM Subject: [ovirt-users] oVirt 3.6 new feature: Affinity Group Enforcement Service Greetings users and developers, I'm developing a new feature "Affinity Rules Enforcement Service"; In summary, =========== If an anti-affinity policy is applied to VMs that are currently running on the same hypervisor, the engine will not automatically migrate one of them off once the policy is applied. The Affinity Rules Enforcement Service will periodically check that affinity rules are being enforced and will migrate VMs if necessary in order to comply with those rules. You're welcome to review the feature page: http://www.ovirt.org/Affinity_Group_Enforcement_Service The feature page is responding to RFE https://bugzilla.redhat.com/show_bug.cgi?id=1112332 Your comments appreciated. Thanks, Tomer _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
