[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tosca] operation implementations
Do you have ideas in mind of how a TOSCA orchestrator could be made aware of a REST API (presumably defined using a swagger file)? This discussion could benefit from some examples. Thanks, Chris From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org>
On Behalf Of Tal Liron On Mon, Mar 15, 2021 at 10:43 PM Chris Lauwers <lauwers@ubicity.com> wrote:
How is an RPC call (JSON-RPC, REST, etc.) to be implemented as an artifact? I don't see the relation. The idea is that exactly an operation type would define the structure of "implementation", which right now is a string or list of strings,
which not only is very limited but also has no obvious semantic meaning. E.g. you are assuming that the implementation string represents an attached artifact name, but ... I very often use it for entirely different things for the various operations that I
use.
Right! But what if you want to run the operation on the remote machine? And if you do, what would be the execution mechanism? Agin, I can see an operation type as a way to clarify exactly how you want this operation to be evaluated and
executed. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]