Re: [tosca-comment] RE: Artifacts for Node Interfaces

[Tal Liron <tliron@redhat.com>]

One suggested solution --

We should have Operation Types, and remove the concept of Interfaces entirely. I have yet to see a use of Interfaces in TOSCA that is in any way similar to how the concept works in other languages. You would still need to declare Operations in node types and relationship types. And that set declarations is itself the "interface".

We could then dive into Operation Types and allow artifacts to be attached and see how we can better support RPC, REST, and other patterns.

Just having an "implementation" string (plus "dependencies") is insufficient, and it's awkward to attach the relevant artifact at the node rather than at the operation.

On Thu, Dec 3, 2020 at 11:05 PM Chris Lauwers <lauwers@ubicity.com> wrote:

Hi Paul, this is an interesting idea, but if this were supported, we would still need syntax to specify how a specific operation in the interface maps to a specific API call in the OpenAPI definition. BTW, I believe there are parallels with Java JAR files or Python packages. One may have a JAR or Package that implements a specific API, but each operation must somehow map to a specific âentry pointâ in the JAR or Package. It would be nice to have a general solution for this type of situation.

Â

Thanks,

Â

Chris

Â

From: tosca-comment@lists.oasis-open.org <tosca-comment@lists.oasis-open.org> On Behalf Of paul.m.jordan@bt.com
Sent: Tuesday, December 1, 2020 5:46 AM
To: tosca-comment@lists.oasis-open.org
Subject: [tosca-comment] Artifacts for Node Interfaces

Â

The TOSCA standard includes the definition of lifecycle operations which may be performed on nodes or relationships. Such operation definitions are grouped into TOSCA interface definitions. Node templates may include such interfaces.

Â

A common pattern for servers to expose operations is via a RESTful API. The contract between a client and a server using a RESTful API is often described using common file format, either swagger or its successor OpenAPI.

Â

When a node template relates to a node which implements a REST API it may be desirable to supply the relevant OpenAPI file as an artifact. Â

With the current grammar an artefact can be supplied with a node template and also with an interface operation. However while OpenAPI describes the operation of the whole interface, TOSCA does not allow an artefact to be supplied at the level of node:interface.

Â

Would it be possible to add keyname artefact to the definition of Interface Assignment?

Â

Paul Jordan
OSS Specialist
BT Technology | Tel +44 (0) 3316252643 Â| paul.m.jordan@bt.com

This email contains information from BT that might be privileged or confidential. And it's only meant for the person above.ÂIf that's not you, we're sorry - we must have sent it to you by mistake. Please email us to let us know, and don't copy or forward it to anyone else. Thanks.

We monitor our email systems and may record all our emails.
British Telecommunications plc
R/O : 81 Newgate Street, London EC1A 7AJ
Registered in England: No 1800000

Â