Implement "availabilityzones" in AutoScalingGroup

Registered by huangtianhua on 2014-04-25

'AvailabilityZones' is required but not implemented on AWS::AutoScaling::AutoScalingGroup and 'OS::Heat::InstanceGroup.
In AWS autoscaling, the instances are created/deleted in 'AvailabilityZones' averagely.
Heat should support the same function and make sure the 'AvailabilityZones' useful.

Blueprint information

Status:
Started
Approver:
None
Priority:
Low
Drafter:
huangtianhua
Direction:
Needs approval
Assignee:
None
Definition:
Pending Approval
Series goal:
None
Implementation:
Needs Code Review
Milestone target:
None
Started by
Zane Bitter on 2014-08-27

Related branches

Sprints

Whiteboard

See if you like the spec in https://review.openstack.org/#/c/105907

Gerrit topic: https://review.openstack.org/#q,topic:bp/implement-autoscalinggroup-availabilityzones,n,z

Addressed by: https://review.openstack.org/116139
    Implement AZ spanning for ASGs

Addressed by: https://review.openstack.org/105907
    Spec for balancing scaling groups across AZs

Addressed by: https://review.openstack.org/117987
    AZ spanning for OS::Heat::AutoScalingGroup

stevebaker: I'll move this to rc-1 for now but I think it is highly likely that this will be deferred until Kilo. The spec and the changes need more review attention, and the changes to the unit test are likely to clash badly with blueprint decouple-nested, which is a higher priority for a Feature Freeze Exception.

stevebaker: I think the spec and the change need some more review attention before this can land. I'm going to defer to Kilo. If you'd like to apply for a FFE then mail openstack-dev so we can discuss. The intention is to refactor the auto scaling unit tests during juno-rc1 so that it is less painful to add changes like this and blueprint decouple-nested.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.