<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;"><br><div><div>On 13 нояб. 2013 г., at 18:12, Renat Akhmerov <<a href="mailto:rakhmerov@mirantis.com">rakhmerov@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div><br class="Apple-interchange-newline">On 13 нояб. 2013 г., at 6:39, Angus Salkeld <<a href="mailto:asalkeld@redhat.com">asalkeld@redhat.com</a>> wrote:</div></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><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></div></blockquote><br></div><div>Hey, misunderstood you here. Sorry. I thought you meant Mistral rather than EventScheduler for some reason :) I’m not aware of someone working on it actively yet. Actually we were planning to work on a similar thing but in a scope of Mistral. I think that is a good API. Using webhooks looks like a reasonable approach to make this service generic. Just one thing I’m not sure about there is state transitions. For example, if a scheduler calls a webhook then the request will require some time to be processed and get a corresponding response. Is this a period when we consider a task in “RUNNING” state?</div><br></body></html>