OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: Artifacts for Node Interfaces


Excellent, thanks. Looking forward to it.

 

Chris

 

From: paul.m.jordan@bt.com <paul.m.jordan@bt.com>
Sent: Friday, December 4, 2020 9:51 AM
To: Chris Lauwers <lauwers@ubicity.com>; tosca-comment@lists.oasis-open.org
Subject: RE: Artifacts for Node Interfaces

 

I do have ideas on how to do that which I will be presenting to TMForum on Tuesday and can share with you at a convenient time.

 

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

 

 

 

From: Chris Lauwers <lauwers@ubicity.com>
Sent: 04 December 2020 05:04
To: Jordan,PM,Paul,TNK6 R <paul.m.jordan@bt.com>; tosca-comment@lists.oasis-open.org
Subject: RE: Artifacts for Node Interfaces

 

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

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]