> On Aug 12, 2015, at 12:49 PM, Joshua Harlow wrote:
>
> possibly submit some kind of oslo-spec or
> blueprint for 'selective persistence' (or other better named thing); if
> u want to work on said code, that's even better :)
Cheers, will do.. Once I get legal approval from work to contribute.
On Wed, 12 Aug 2015 10:31:03 -0700
Demian Brecht wrote:
>
> > On Aug 10, 2015, at 1:18 PM, Joshua Harlow
> > wrote:
> >
> > Is that what u are looking for? (or possibly something else?),
>
> Hi Josh,
>
> Thanks for the reply. I haven’t had time to dig into it much further,
> but I’m not sure
> On Aug 10, 2015, at 1:18 PM, Joshua Harlow wrote:
>
> Is that what u are looking for? (or possibly something else?),
Hi Josh,
Thanks for the reply. I haven’t had time to dig into it much further, but I’m
not sure that’s what I’m looking for (unless I’m missing something in initial
configur
Hmmm,
I'm pretty sure what u want exists,
For example:
https://github.com/openstack/taskflow/blob/master/taskflow/examples/persistence_example.py
That uses sqlite (or a file) to store information,
U just have to decide what backend is best for u,
Is that what u are looking for? (or possibly
Hi all,
As I understand it, the persistence and related backends are intended to store
atom and flow state. This will only persist until the end of an entirely
successful run (unless explicitly configured to not purge for auditing and
other such reasons). My question is: Is there a way to confi