Page History

...

• Affinity group tab that lists the affinity  groups created by this user - this could either should be a separate tab or as part of VM detailson the left hand side menu.
• Ability to create a new Affinity group based on globally available affinity types
• As part of VM creation/update wizards, users should be provided with the following:
  • Choice to associate affinity and/or anti-affinity groups
  • If chosen, users should be provided with a list of affinity groups available or define a new affinity group

FAQ

• EC2 API fidelity?* Yes, confirmed that the CS API’s around affinity groups are in line with the EC2 placementgroup API’s.
• However we are not adding support to awsapi yet as part of this feature. *  Is the AWS workflow of placementgroups and VM deployment similar?* Yes confirmed that the workflow is compatible.
•  EC2 VM deployment RunInstances API takes in the Placement.GroupName parameter.  Similarly CS deployVirtualMachine API will accept List<affinity_group_ids> or List<affinity_group_names>
• EC2 workflow mentioned here http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using_cluster_computing.html#create_cluster is similar to our design for affinity groups in the VM deployment wizard:* _ _Auto-scaling support?
  •  This not supported by the feature.

• Supports Projects?
  • The affinity groups are created by an individual user account and available to that account only. We are not including any support for CloudStack Projects feature.

• DRS? 
  • This is applicable only for placement operations through CloudStack. This implementation is to only support scenarios where the HV does not do HA or DRS.

Appendix

Appendix A:

Appendix B: