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] contradiction between clause 3.7 and 6.1 for CSAR


Hi Shitao,

 

The 3.7 chapter is a new section (appearing in the latest TOSCA 2.0 revisions) providing a high-level explanations of the core concepts, and still under review. Yes this is a misstatement, great you spotted it. We should change the last paragraph to: âEach CSAR may contain a file called TOSCA.meta that describes the organization of the CSARâ.

The rest of the details will be explained in chapter 6.

 

BR/C

 

 

From: <tosca@lists.oasis-open.org> on behalf of Lishitao <lishitao@huawei.com>
Date: Wednesday, 9 September 2020 at 10:37
To: "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
Subject: [tosca] contradiction between clause 3.7 and 6.1 for CSAR

 

Hi Chris and all,

 

In the latest TOSCA 2.0 draft, it seems that clause 3.7 and 6.1 are not aligned with each other,

In 3.7, it says that

âEach CSAR MUST contain a file called TOSCA.meta (either in the top-level directory of the archive or in a subdirectory called TOSCA-Metadata).â

 

While in 6.1, it still indicates that CSAR without TOSCA.meta file is allowed.

 

Which one is correct?

Since ETSI NFV spec supports both CSAR options as described in tosca-simple-profile-yaml v1.2, such change for CSAR may also impact the ETSI NFV specs.

 

Regards

shitao



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