Excerpts from Mike Spreitzer's message of 2013-10-17 17:19:58 -0700: > What is the rationale for this new feature? Since there is already an > autoscaling group implemented by Heat, what is the added benefit here? And > why is it being done as another heat-native thing rather than as an > independent service (e.g., as outlined in > https://wiki.openstack.org/wiki/Heat/AutoScaling for an autoscaling group > service)?
This supports that design quite well. The point is to be able to group and clone any resource, not just server/instance. So autoscaling might be configured to manage a group of Trove database instances which are then fed as a list to a group of separately autoscaled webservers. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
