On 03 Jul 2015, at 12:14, Lingxian Kong anlin.k...@gmail.com wrote:
What do you think if we add a script(may be under tools or cmd package) to
help doing this?
What script do you mean? To launch a separate clean-up component.
I see that, first of all, it’s a subsystem of Mistral
will discuss the details in the spec.
Thanks.
*From:* Renat Akhmerov [mailto:rakhme...@mirantis.com]
*Sent:* יום ה 02 יולי 2015 12:34
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [mistral] Best practices for the DB
maintanence
OK, Renat, I see, thanks for clarification. Let's discuss it together
after the blueprint is proposed.
On Fri, Jul 3, 2015 at 4:41 PM, Renat Akhmerov rakhme...@mirantis.com
wrote:
On 03 Jul 2015, at 12:14, Lingxian Kong anlin.k...@gmail.com wrote:
What do you think if we add a script(may be
Hi Elisha,
Currently Mistral doesn’t support any expiration policies for
workflow/task/action runtime objects. It keeps them forever until someone
deletes them manually.
I see the following ways of addressing your need:
Implement some cleanup component within Mistral (how to call it?) using
questions)
Subject: Re: [openstack-dev] [mistral] Best practices for the DB maintanence in
production
Hi Elisha,
Currently Mistral doesn’t support any expiration policies for
workflow/task/action runtime objects. It keeps them forever until someone
deletes them manually.
I see the following ways
