AutoScalingGroup missing VPCZoneIdentifier property

[Steven Hardy]

Now we have the quantum-based network resources, and an implementation of AWS::EC2::VPC, we can/should implement the VPCZoneIdentifier property for AWS::AutoScaling::AutoScalingGroup

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/24504

[Steven Dake (sdake)]

Quantum does not provide a mechanism to attach a SubNet to an AZ.

Our subnet driver:
https://github.com/openstack/heat/blob/master/heat/engine/resources/quantum/subnet.py#L30

Quantum's subnet features:
https://github.com/openstack/python-quantumclient/blob/master/quantumclient/quantum/v2_0/subnet.py#L75

As a result of missing dependency functionality, bouncing this bug to a later time when quantum provides AZ assignment of subnets.

[Jeff Peeler (jpeeler-z)]

https://blueprints.launchpad.net/quantum/+spec/subnet-az

[Simon Pasquier (simon-pasquier)]

A partial fix for this bug has been implemented [1]. It only allows one item in the VPCZoneIdentifier list if that property is defined.

[1] https://review.openstack.org/#/c/43082/

[Dave Johnston (dave-johnston)]

I'm trying to understand this feature.
My use-case I want to assign multiple subnets to an instance when it is created i.e. there is a management subnet , and data subnet.

With this fix, does one subnet still get assigned to the instance, depending on the AZ? Would it be possible to attached multiple subnets to an instance within the same AZ

[huangtianhua (huangtianhua)]

I believe we should and can assign subnets to the instances in asg, as AWS::EC2::Instance does.
I will propose a patch to support assign subnets to the instance in asg.