[openstack-dev] [trove][mistral] scheduled tasks

Georgy Okrokvertskhov gokrokvertskhov at mirantis.com
Mon Dec 30 21:08:03 UTC 2013


I would suggest to talk with Mistral team about scheduling. As I know right
now thay are writing a PoC code which will have scheduling functionality.
Mistral in contrary to Qonos does not require worker process. In Mistral
you can create a task with scheduler and API call back so that Mistral can
call some API endpoint with some specific parameters in predefined time. I
suspect that it covers your use case.

Security concerns can be addressed and it will be great if you submit
specific BP to Mistral with all security requirements and scheduling
features required by Trove.


On Mon, Dec 30, 2013 at 12:26 PM, Brian Rosmaita <
brian.rosmaita at rackspace.com> wrote:

>  Greg,
> This might be useful:
> https://wiki.openstack.org/wiki/Qonos-scheduling-service
> There's a link to the code repository at the bottom of the document.  It
> might be kind of overkill for what you want, though.
> cheers,
> brian
>  ------------------------------
> *From:* Greg Hill [greg.hill at RACKSPACE.COM]
> *Sent:* Monday, December 30, 2013 12:59 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [trove][mistral] scheduled tasks
>  I've begun working on the scheduled tasks feature that will allow
> automated backups (and other things) in trove.
>  Here's the blueprint:
> https://wiki.openstack.org/wiki/Trove/scheduled-tasks
>  I've heard some mention that mistral might be an option rather than
> building something into trove.  I did some research and it seems like it
> *might* be a good fit, but it also seems like a bit of overkill for
> something that could be built in to trove itself pretty easily.  There's
> also the security concern of having to give mistral access to the trove
> management API in order to allow it to fire off backups and other tasks on
> behalf of users, but maybe that's just my personal paranoia and it's really
> not much of a concern.
>  My current plan is to not use mistral, at least for the original
> implementation, because it's not yet ready and we have a fairly urgent need
> for the functionality.  We could make it an optional feature later for
> people who are running mistral and want to use it for this purpose.
>  I'd appreciate any and all feedback before I get too far along.
>  Greg
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131230/f0c2b1f6/attachment.html>

More information about the OpenStack-dev mailing list