@ariatosca.incubator.apache.org
> Subject: Re: Support for extension point during service execution
>
> We half do. :) Actually, this has become a major topic of discussion
> recently on other lists. There's some room to discuss exactly what and how
> is available to the ctx proxy. Ri
@ariatosca.incubator.apache.org
Subject: Re: Support for extension point during service execution
We half do. :) Actually, this has become a major topic of discussion recently
on other lists. There's some room to discuss exactly what and how is available
to the ctx proxy. Right now it's both too unrestricted and too
@ariatosca.incubator.apache.org
Subject: Re: Support for extension point during service execution
Hi DJ,
The question here is why use ARIA's orchestrator at all? It sounds like you
have your own orchestration engine. This is an intended use case for ARIA (and
indeed was used in the OPEN-O project
Hi DJ,
The question here is why use ARIA's orchestrator at all? It sounds like you
have your own orchestration engine. This is an intended use case for ARIA
(and indeed was used in the OPEN-O project).
There are a few ways to use ARIA here:
1) You can use the ARIA's Python API and access all
Hi Team,
We are looking at an execution point during a service execution through a
plugin. With this the execution will not go through the workflow runner
(install/uninstall) defined by the orchestrator but the services instance
context object will be provided to the plugin which will take
