I think there is some movement forming around a common orchestration like library with all of this, It might make sense to work together and achieve the biggest bang for the buck? Some links: * https://wiki.openstack.org/wiki/StructuredStateManagement * https://wiki.openstack.org/wiki/StructuredStateManagementDetails * https://wiki.openstack.org/wiki/StructuredWorkflows * https://wiki.openstack.org/wiki/StructuredWorkflowPrimitives Some stuff I did at the summit @ http://lists.openstack.org/pipermail/openstack-dev/2013-April/008024.html I'd love to have a unified front to work on this (so that something happens, instead of nothing). So please feel free to reach out. The orchestration meeting we had was IMHO very fruitful: http://eavesdrop.openstack.org/meetings/openstack_orchestration_group/2013/ openstack_orchestration_group.2013-05-02-19.59.txt Thoughts? On 5/2/13 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