Open Stack

Hi Kevin,

The design of OS::Heat::AutoScalingGroup should not require explicit support for load balancers. The design is meant to allow you to create a resource that wraps up both a OS::Heat::Server and a PoolMember in a template and use it via a Stack resource.

(Note that Mike was talking about the new OS::Heat::AutoScalingGroup resource, not AWS::AutoScaling::AutoScalingGroup).

So, while I haven’t tested this case with PoolMember specifically, and there may still be bugs, no more feature implementation should be necessary (I hope).

--
Christopher Armstrong
IRC: radix



On March 12, 2014 at 1:52:53 PM, Fox, Kevin M (kevin.fox at pnnl.gov<mailto:kevin.fox at pnnl.gov>) wrote:

I submitted a blueprint a while back that I think is relevant:

https://blueprints.launchpad.net/heat/+spec/elasticloadbalancing-lbaas

Currently heat autoscaling doesn't interact with Neutron lbaas and the configurable bits aren't configurable enough to allow it without code changes as far as I can tell.

I think its only a few days of work, but the OpenStack CLA is preventing me from contributing. :/

Thanks,
Kevin

________________________________
From: Mike Spreitzer [mspreitz at us.ibm.com]
Sent: Wednesday, March 12, 2014 11:34 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [heat][neutron] OS::Heat::AutoScalingGroup and OS::Neutron::PoolMember?

Has anybody exercised the case of OS::Heat::AutoScalingGroup scaling a nested stack that includes a OS::Neutron::PoolMember?  Should I expect this to work?

Thanks,
Mike
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140312/79d5371b/attachment.html>