[openstack-dev] [heat][mistral] EventScheduler vs Mistral scheduling

Renat Akhmerov rakhmerov at mirantis.com
Thu Nov 14 11:26:44 UTC 2013

On 14 Nov 2013, at 18:03, Zane Bitter <zbitter at redhat.com> wrote:

> What might be a downside is that sharing a back-end may not be technically convenient - one thing we have been reminded of in Heat is that a service with timed tasks has to be scaled out in a completely different way to a service that avoids them. This may or may not be an issue for Mistral, but it could be resolved by having different back-end services that communicate over RPC. The front-end API can remain shared though.

Not sure I’m 100% following here. Could you please provide more details on this? Seems to be an important topic to me. Particularly, what did you mean when you said “sharing a back-end”? Sharing by which components?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131114/b5516c3e/attachment.html>

More information about the OpenStack-dev mailing list