Open Stack

I accidentally sent this reply to Josh directly.

Greg

On Dec 30, 2013, at 12:17 PM, Greg Hill <greg.hill at RACKSPACE.COM<mailto:greg.hill at RACKSPACE.COM>> wrote:

Taskflow seems like it would be a good fit for implementation or re-implementation of some of the tasks we hope to automate, but the first set of desired tasks are already built.  We're simply building the scheduling logic to automate them, so I don't see what taskflow would buy us there.

Greg

On Dec 30, 2013, at 12:14 PM, Joshua Harlow <harlowja at yahoo-inc.com<mailto:harlowja at yahoo-inc.com>>
 wrote:

Any reason to not use taskflow (https://wiki.openstack.org/wiki/TaskFlow) to help u here??

I think it could be easily adapted to do what u want, and would save u from having to recreate the same task execution logic that everyone seems to rebuild…

-Josh

From: Greg Hill <greg.hill at RACKSPACE.COM<mailto:greg.hill at RACKSPACE.COM>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Monday, December 30, 2013 at 9:59 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
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


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