Juju Actions - Use Cases

[Stuart Bishop]

On 11 September 2014 00:14, Richard Harding <rick.harding at canonical.com> wrote:
> On Wed, 10 Sep 2014, Stuart Bishop wrote:
>
>> On 10 September 2014 19:49, Richard Harding <rick.harding at canonical.com> wrote:
>>
>> > I think most of the use cases presented so far line up with ours. One I
>> > want to call out as interesting and I hadn't thought about is killing a
>> > long running action in progress. The example of a database backup. I don't
>> > see anything along those lines in the current api doc. You can cancel
>> > something from the queue, but can you cancel something running.
>>
>> I don't think this one impacts the design. The cancel action can kill
>> the process being run by the backup action easily enough, and that
>> still meets my use case.
>
> Right, but my understanding is that actions are a single queue. If you want
> to cancel something in progress you need to jump outside of the queue to
> do that.

I see. So if only one action can run at a time, then my backup action
must trigger the backup process to be run in the background and return
quicky. This would stop it streaming the backup back to the client,
and require it to streaming to remote remote storage and retrieved by
the client once it is completed.


-- 
Stuart Bishop <stuart.bishop at canonical.com>