On 13 нояб. 2013 г., at 6:39, Angus Salkeld <asalk...@redhat.com> wrote:
> On 12/11/13 15:13 -0800, Christopher Armstrong wrote: >> Given the recent discussion of scheduled autoscaling at the summit session >> on autoscaling, I looked into the state of scheduling-as-a-service in and >> around OpenStack. I found two relevant wiki pages: >> >> https://wiki.openstack.org/wiki/EventScheduler >> >> https://wiki.openstack.org/wiki/Mistral/Cloud_Cron_details >> >> The first one proposes and describes in some detail a new service and API >> strictly for scheduling the invocation of webhooks. >> >> The second one describes a part of Mistral (in less detail) to basically do >> the same, except executing taskflows directly. >> >> Here's the first question: should scalable cloud scheduling exist strictly >> as a feature of Mistral, or should it be a separate API that only does >> event scheduling? Mistral could potentially make use of the event >> scheduling API (or just rely on users using that API directly to get it to >> execute their task flows). >> Good point. We changed our opinion on that several times by now. We need to have a closer look at this API in order to understand what would be the best responsibility distribution here. But basically yes, Mistral might not contain that if this API makes a value of using it somewhere else. >> Second question: if the proposed "EventScheduler" becomes a real project, >> which OpenStack Program should it live under? >> >> Third question: Is anyone actively working on this stuff? :) > Yes, we started actively working on this. And you’re very welcome to join :) https://etherpad.openstack.org/p/TaskServiceDesign https://etherpad.openstack.org/p/TaskFlowAndMistral https://etherpad.openstack.org/p/MistralQuestionsBeforeImplementation https://etherpad.openstack.org/p/MistralRoadmap https://etherpad.openstack.org/p/MistralAPISpecification https://etherpad.openstack.org/p/MistralDSLSpecification And we have a meeting at #openstack-meeting on Mondays at 16.00 UTC. > Your work mates;) https://github.com/rackerlabs/qonos > > how about merge qonos into mistral, or at lest put it into stack forge? Worth considering, we need to think it over. > -Angus >> >> >> -- >> IRC: radix >> Christopher Armstrong >> Rackspace > >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev