Is the expectation here that the update policy for the auto-scaling group is enforced only when either the launch configuration or subnet group membership is changed in the auto-scaling group? The LaunchConfigurationName is not currently listed as an update_allowed_properties in the AutoScalingGroup. Update handling is not implemented in LaunchConfiguration either. Also, VPCZoneIdentifier for listing subnet group membership is not implemented in the AutoScalingGroup either. Should there be blueprints to handle these before working on the update policy?
Thx. Winson _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
