[openstack-dev] [Heat] Autoscaling and the Rackspace Otter project

Mark McLoughlin markmc at redhat.com
Thu Jun 13 10:13:02 UTC 2013


On Thu, 2013-06-13 at 10:45 +0100, Steven Hardy wrote:
> On Wed, Jun 12, 2013 at 05:06:31PM -0500, Christopher Armstrong wrote:

> > I believe the consensus is that the work on the new HOT format and
> > underlying design changes is a prerequisite for the autoscaling work that
> > Thomas and I are to do, so we'll definitely help with that. I'll let
> > someone with a better understanding chime in about that.
> 
> As others have mentioned, I'm not clear on this coupling between template
> and Autoscaling, it seems like this superset of AS functionality will just
> require a new resource/resources to provide the interface, and as
> previously discussed, probably an API which allows AS functionality to be
> consumed without directly creating a Heat template (we may do that behind
> the scenes though..)

Is there any reason for the non-template based autoscaling API to be
part of Heat at all? Why would it not be a separate standalone
autoscaling service?

Heat exposing any non-template based API seems odd to me

Cheers,
Mark.




More information about the OpenStack-dev mailing list