On 01/12/14 18:34, Angus Salkeld wrote:
I'd suggest a combination between A and B.
We may not be as far apart as I thought.
1) Separate some of the autoscaling logic into libraries in Heat
2) Get the separated REST service in place and working (using the above
heat library)
3) Add an environm
On Tue, Dec 2, 2014 at 8:15 AM, Zane Bitter wrote:
> On 28/11/14 02:33, Qiming Teng wrote:
>
>> Dear all,
>>
>> Auto-Scaling is an important feature supported by Heat and needed by
>> many users we talked to. There are two flavors of AutoScalingGroup
>> resources in Heat today: the AWS-based one
On 28/11/14 02:33, Qiming Teng wrote:
Dear all,
Auto-Scaling is an important feature supported by Heat and needed by
many users we talked to. There are two flavors of AutoScalingGroup
resources in Heat today: the AWS-based one and the Heat native one. As
more requests coming in, the team has p
On Fri, Nov 28, 2014 at 02:33:10PM +, Jastrzebski, Michal wrote:
>
>
> > -Original Message-
> > From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com]
> > Sent: Friday, November 28, 2014 8:33 AM
> > To: openstack-dev@lists.openstack.org
> > Subject
On Fri, Nov 28, 2014 at 5:33 PM, Qiming Teng
wrote:
> Dear all,
>
> Auto-Scaling is an important feature supported by Heat and needed by
> many users we talked to. There are two flavors of AutoScalingGroup
> resources in Heat today: the AWS-based one and the Heat native one. As
> more requests
Per our discussion in Paris, I'm partial to Option B. I think a separate API
endpoint is a lower priority at this point compared to cleaning up and
normalizing the autoscale code on the back-end. Once we've refactored the
engine code and solidified the RPC interface, it would be trivial to add a
> -Original Message-
> From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com]
> Sent: Friday, November 28, 2014 8:33 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [Heat] Rework auto-scaling support in Heat
>
> Dear all,
>
> Auto-Scal
Dear all,
Auto-Scaling is an important feature supported by Heat and needed by
many users we talked to. There are two flavors of AutoScalingGroup
resources in Heat today: the AWS-based one and the Heat native one. As
more requests coming in, the team has proposed to separate auto-scaling
support