Page History

...

• Admin decides what are the affinity/anti-affinity types available to the users.
• This depends on which AffinityGroupProcessor plugins are included in the deployment. Each AffinityGroupProcessor plugin implements a certain affinity/anti-affinity and exposes the type it implements.
• If admin does not want certain type of affinity/anti-affininity then the plugin implementing that type should simply be excluded in the deployment.

User

• User can list the affinity /anti-affinity types available using listAffinityTypes API (This in turn invokes the chain of AffinityGroupProcessor plugins and adds the type each implements to the list response.)
• User creates affinity /anti-affinity group using a type available
• During VM deployment, user can specify affinity/anti-affinity group Ids or names to be associated with the VM. Looking at the affinity group, the corresponding plugin that can handle this type will then process to set the deployment scope.
• User can list the affinity /anti-affinity groups of a VM
• User can delete/update the affinity /anti-affinity groups a VM is associated to.
• User can delete the affinity /anti-affinity group only if there are no VM's associated with it.

...