However, note that since each process creates its own workflow_runner (and consequently a new engine), starting and ending the workflow_runner should be done from the same process.
On Thu, Jul 13, 2017 at 11:39 AM Maxim Orlov <ma...@gigaspaces.com> wrote: > The execution id is indeed the linking factor between all execution > related operations. ARIA doesn't provide asynchronous execution based > operations. However, here > <https://github.com/apache/incubator-ariatosca/blob/master/aria/cli/commands/executions.py#L204> > you can see how ARIA runs executions in an asynchronous manner. > > On Wed, Jul 12, 2017 at 9:54 PM DeWayne Filppi <dewa...@gigaspaces.com> > wrote: > >> I need to: >> >> 1. Launch an execution asynchronously >> 2. View the execution status asynchronously >> 3. Cancel the execution asynchronously >> >> I'm assuming the execution id is the key linking these. Is this kind of >> operation supported by the library, or is it assumed that the caller will >> manage such ( e.g. by calling synchronous library calls in their own >> threads and managing the thread externally)? If possible with the >> library, >> is there an example? >> >> -- DeWayne >> >
