Open Stack

On 30/04/13 21:23, Russell Bryant wrote:
> Greetings,
>
> The following blueprint was proposed for the havana series:
>
>      https://blueprints.launchpad.net/nova/+spec/scheduled-images
>
> Based on the current design, I think the nova part of this needs to be
> deferred.  It does not seem appropriate to add an API extension that
> talks to a service that is not an integrated project, or at least incubated.
>
> Beyond that, I'm curious about the choice to implement this as a new
> service.  I definitely agree that this is not something that should be
> implemented inside of Nova.  However, I wonder if it makes sense as a
> feature in Heat.  It seems like an orchestration feature.
>
> Thoughts?

This is a workflow (not orchestration) feature and would be solidly 
in-scope for a WFaaS API (e.g. the proposed 
https://wiki.openstack.org/wiki/Convection mentioned several times in 
this thread) in the form of a much more generic "cloud cron" type feature.

It certainly *could* be implemented in either Heat or Horizon, but there 
are pretty strong arguments for not doing so. We already have one 
example - Autoscaling - of something like this being too-tightly coupled 
into Heat, and we have a bunch of work ahead to try to tease the two 
apart so that everybody can get the benefits of Autoscaling, not just 
Heat template users. I wouldn't be in favour of creating another 
situation like that at this stage.

cheers,
Zane.