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

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

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


Subject: RE: [tosca] Proposal for TOSCA repositories grammar


Thanks Tal and Adam, this is a very good discussion. Iâd love to see proposals for how to make repositories âfirst class objectsâ in TOSCA.

 

Thanks,

 

Chris

 

From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org> On Behalf Of Tal Liron
Sent: Wednesday, October 28, 2020 10:11 PM
To: adam souzis <adam@souzis.com>
Cc: tosca@lists.oasis-open.org
Subject: Re: [tosca] Proposal for TOSCA repositories grammar

 

On Wed, Oct 28, 2020 at 11:56 PM adam souzis <adam@souzis.com> wrote:

Could you use a internal URI scheme as the repository URL, like "turandot:"?

 

Sure, if I extend my whole URL handling library. :) I actually can do that in my specific case, but I'm sure that many orchestrators cannot, and in any case I think it should be supported by TOSCA grammar rather than requiring orchestrators to implement difficult workarounds.

 

it really would like to know what type of repository it is and have properties or at least metadata. 

 

Metadata is the ultimate workaround! In the case of artifacts -- they are typed, so we can use actually modeled data: TOSCA properties (but because TOSCA is object-oriented you would need all artifact types to import from that base type, which is not always possible). These are all workarounds. I think that because artifact management and import management are so intrinsic to TOSCA it should be well-defined in the grammar itself.

 

I'm sure we all agree that TOSCA repositories are quite ineffective right now and can use some of our attention.



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