Actually the proposal is quite vague. What does affinity mean to the end-user? What guarantees are being asked for? - the vms are on the same hypervisor (affinity) - the vms are not on the same hypervisor (anti) - the vms are interconnected by a high-speed interconnect (affinity) - the vms are in different failure domains (host/cluster/pod)
I find the concept of affinity groups useful. A possible workflow would be 1. Create an affinity group of type 'Foo' 1a. Group type indicates the guarantee 2. Create a VM in the group VMs can only leave groups on vm destruction. But without the specific type of guarantee, it is hard to discuss this proposal. On 1/3/13 4:23 PM, "Manan Shah" <manan.s...@citrix.com> wrote: >Hi, > >I would like to propose a new feature for enabling Affinity / >Anti-affinity rules in CS 4.1. I have created a JIRA ticket and provided >the requirements at the following location. Please provide feedback on >the requirements. > >JIRA Ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-739 >Requirements: >https://cwiki.apache.org/confluence/display/CLOUDSTACK/Affinity+-+Anti-aff >i >nity+rules > > >Regards, >Manan Shah >
