On Jan 23, 2014, at 3:41 PM, Michael Basnight wrote:
>
> Will we be doing more complex things than "every day at some time"? ie, does
> the user base see value in configuring backups every 12th day of every other
> month? I think this is easy to write the schedule code, but i fear that it
>
>
>Will we be doing more complex things than "every day at some time"? ie,
>does the user base see value in configuring backups every 12th day of
>every other month? I think this is easy to write the schedule code, but i
>fear that it will be hard to build a smarter scheduler that would only
>allow
s seems easier to schedule
and would enable an operator to change things in a pinch.
From: Michael Basnight [mbasni...@gmail.com]
Sent: Thursday, January 23, 2014 3:41 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [trove] scheduled tasks redux
On Jan 23, 2014, at
On Jan 23, 2014, at 12:20 PM, Greg Hill wrote:
> The blueprint is here:
>
> https://wiki.openstack.org/wiki/Trove/scheduled-tasks
>
> So I have basically two questions:
>
> 1. Does anyone see a problem with defining the repeating options as a single
> field rather than multiple fields?
Im fin
The blueprint is here:
https://wiki.openstack.org/wiki/Trove/scheduled-tasks
I've been working on the REST API portion of this project, and as I was working
on the client, a part of it didn't sit quite right. As it is specified, it
calls for two fields to define when and how often to run the t
