On 08/04/15 21:51, Miguel Grinberg wrote:
Hi Angus,
Regarding this:
As Zane suggested, you should think of autoscaling as been in a
different service.
It's not that I can't see your point of view. I can imagine an
autoscaling service. I agree with you guys that if we had that, then
none of
Hi,
Response inline.
Hi,
The OS::Heat::AutoScalingGroup resource is somewhat limited at this time,
because when a scaling even occurs it does not notify dependent resources,
such as a load balancer, that the pool of instances has changed.
That's technically not true. If you use a neutron
Thomas,
I stand corrected. If you use Neutron's LBAAS plugin you do get the correct
autoscaling behavior because Neutron updates the loadbalancer when pool
members are added or removed (Heat does not seem to participate in this
update, as far as I can see). Still my #1 issue still exists,
On 07/04/15 22:02, Miguel Grinberg wrote:
Hi,
The OS::Heat::AutoScalingGroup resource is somewhat limited at this
time, because when a scaling even occurs it does not notify dependent
resources, such as a load balancer, that the pool of instances has changed.
As Thomas mentioned, the
On 08/04/15 18:03, Miguel Grinberg wrote:
Here is where we disagree. In my opinion this is broken functionality.
It's not broken functionality, it's functionality that never existed.
Spontaneous stack updates are just not part of the CloudFormation model,
and they've never been a part of
On Thu, Apr 9, 2015 at 8:03 AM, Miguel Grinberg miguel.s.grinb...@gmail.com
wrote:
Zane, replies inline.
On Wed, Apr 8, 2015 at 3:46 PM, Zane Bitter zbit...@redhat.com wrote:
On 07/04/15 22:02, Miguel Grinberg wrote:
Hi,
The OS::Heat::AutoScalingGroup resource is somewhat limited at
Zane, replies inline.
On Wed, Apr 8, 2015 at 3:46 PM, Zane Bitter zbit...@redhat.com wrote:
On 07/04/15 22:02, Miguel Grinberg wrote:
Hi,
The OS::Heat::AutoScalingGroup resource is somewhat limited at this
time, because when a scaling even occurs it does not notify dependent
resources,
Hi Angus,
Regarding this:
As Zane suggested, you should think of autoscaling as been in a different
service.
It's not that I can't see your point of view. I can imagine an autoscaling
service. I agree with you guys that if we had that, then none of this would
be Heat's concern.
When I think
Hi,
The OS::Heat::AutoScalingGroup resource is somewhat limited at this time,
because when a scaling even occurs it does not notify dependent resources,
such as a load balancer, that the pool of instances has changed.
The AWS::AutoScaling::AutoScalingGroup resource, on the other side, has a
