<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 6:39, Angus Salkeld <<a href="mailto:asalkeld@redhat.com">asalkeld@redhat.com</a>> wrote:</div><br><blockquote type="cite"><div style="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;">Your work mates;)<span class="Apple-converted-space"> </span><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></div></blockquote><br></div><div>Just got to looking at qonos. It actually looks similar in some ways to Mistral but with some differences: no actually workflows but rather individual job scheduling, no configurable transports, no webhooks, dedicated workers. And in some ways it’s related to EvenScheduler API but it’s not generic enough (not based anything like webhooks). I think we could definitely reuse some ideas from Qonos in Mistral, but I’m not sure at this point if it could be just merged in as is, the philosophy of the projects are a little bit different. Worth considering though. It would be cool to get Adrian involved into this discussion since he participated in both things.</div><br></body></html>