Open Stack

Do we need a new api for this?

We should look at using something like: http://airbnb.github.io/chronos/#API

or simply using Qonos directly instead of layering something on top of it.

Vish

On May 2, 2013, at 12:31 PM, Adrian Otto <adrian.otto at rackspace.com> wrote:

> Stackers,
> 
> In this prior thread, is clear that multiple projects could make use of a utility service for the purpose of scheduling task-flows (workflows) or possibly Heat orchestrations to occur on regular intervals.
> 
> http://lists.openstack.org/pipermail/openstack-dev/2013-April/008307.html
> http://lists.openstack.org/pipermail/openstack-dev/2013-May/008332.html
> 
> Russel Bryant from the Nova team would like to use something to trigger capturing snapshots, and the auto-scale Heat developers would like something that allows them to trigger the scaling up and down of compute servers on a pre-determined schedule. There is potential value in offering an API service (integrated with Horizon) that can be exposed to end-users to trigger events to start on a schedule. Some discussion about the design of such a service has begun, and needs to be conducted in the open.
> 
> I'd like to ask for your input on how the ideal solution would be designed. I have started a Wiki Page here as a starting point for the discussion:
> 
> https://wiki.openstack.org/wiki/EventScheduler
> 
> Questions to answer:
> 
> 1) What features should be included?
> 2) Where should the service be incubated, and if/how it should be integrated with Oslo? The answer to this should indicate where the blueprints should be filed.
> 3) Are there volunteers to work on this?
> 
> This solution will be designed primarily for simplicity and scalability. We can iterate on it to add features as use cases materialize for this.
> 
> Thanks,
> 
> Adrian
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev