<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div><div><div><div>On 13 нояб. 2013 г., at 6:39, Angus Salkeld <<a href="mailto:asalkeld@redhat.com">asalkeld@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On 12/11/13 15:13 -0800, Christopher Armstrong wrote:<br><blockquote type="cite">Given the recent discussion of scheduled autoscaling at the summit session<br>on autoscaling, I looked into the state of scheduling-as-a-service in and<br>around OpenStack. I found two relevant wiki pages:<br><br><a href="https://wiki.openstack.org/wiki/EventScheduler">https://wiki.openstack.org/wiki/EventScheduler</a><br><br>https://wiki.openstack.org/wiki/Mistral/Cloud_Cron_details<br><br>The first one proposes and describes in some detail a new service and API<br>strictly for scheduling the invocation of webhooks.<br><br>The second one describes a part of Mistral (in less detail) to basically do<br>the same, except executing taskflows directly.<br><br>Here's the first question: should scalable cloud scheduling exist strictly<br>as a feature of Mistral, or should it be a separate API that only does<br>event scheduling? Mistral could potentially make use of the event<br>scheduling API (or just rely on users using that API directly to get it to<br>execute their task flows).<br><br></blockquote></blockquote><div><br></div>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.</div><div><br></div><div><br><blockquote type="cite"><blockquote type="cite">Second question: if the proposed "EventScheduler" becomes a real project,<br>which OpenStack Program should it live under?<br><br>Third question: Is anyone actively working on this stuff? :)<br></blockquote><br></blockquote><div><br></div><div>Yes, we started actively working on this. And you’re very welcome to join :)</div><div><br></div><div><a href="https://etherpad.openstack.org/p/TaskServiceDesign">https://etherpad.openstack.org/p/TaskServiceDesign</a></div><div><a href="https://etherpad.openstack.org/p/TaskFlowAndMistral">https://etherpad.openstack.org/p/TaskFlowAndMistral</a></div><div><a href="https://etherpad.openstack.org/p/MistralQuestionsBeforeImplementation">https://etherpad.openstack.org/p/MistralQuestionsBeforeImplementation</a></div><div><a href="https://etherpad.openstack.org/p/MistralRoadmap">https://etherpad.openstack.org/p/MistralRoadmap</a></div><div><a href="https://etherpad.openstack.org/p/MistralAPISpecification">https://etherpad.openstack.org/p/MistralAPISpecification</a></div><div><a href="https://etherpad.openstack.org/p/MistralDSLSpecification">https://etherpad.openstack.org/p/MistralDSLSpecification</a></div><div><br></div><div>And we have a meeting at #openstack-meeting on Mondays at 16.00 UTC.</div><br><blockquote type="cite">Your work mates;) <a href="https://github.com/rackerlabs/qonos">https://github.com/rackerlabs/qonos</a><br><br>how about merge qonos into mistral, or at lest put it into stack forge?<br></blockquote><div><br></div>Worth considering, we need to think it over.<br><br><blockquote type="cite">-Angus<br><blockquote type="cite"><br><br>-- <br>IRC: radix<br>Christopher Armstrong<br>Rackspace<br></blockquote><br><blockquote type="cite">_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><br><br>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></div></body></html>