Re: [tosca] YAML v1.2: CSAR zip without TOSCA-Metadata directory clarification

[Calin Curescu <calin.curescu@ericsson.com>]

Just wanted to reinforce that the Examples are not normative anyway as specified in the first paragraph of chapter 6: âTOSCA Cloud Service Archive (CSAR) formatâ, so this can be used as an argument on why it does not require an additional public review process.

 

BR,

/Calin

 

From: <tosca@lists.oasis-open.org> on behalf of "Nguyenphu, Thinh (Nokia - US/Dallas)" <thinh.nguyenphu@nokia.com>
Date: Tuesday, 9 July 2019 at 17:25
To: Calin Curescu <calin.curescu@ericsson.com>, "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
Subject: RE: [tosca] YAML v1.2: CSAR zip without TOSCA-Metadata directory clarification

 

Calin and et al,

Thanks for the clarification on the topic. Per our call discussion, it is confirmed that the value of template_version is 1.1. based on this normative statement from YAML v1.3 or v1.2 Section 6.3: ââThe CSAR-Version is defined by the template_version metadata section.â

 

Therefore, the example should illustrated as follow, in the case of YAML v1.1, 1.2, and 1.3:

 

tosca_definitions_version: tosca_simple_yaml_1_2

 

metadata:

  template_name: MyCompany

  template_author: Nokia

  template_version: 1.1

 

Also, it was suggested and agreed to update the example in section 6.3.1, as long as this change does not requires additional public review process. Chris will bring this topic up during next TC meeting.

 

6.3.1  Example

The following represents a valid TOSCA template file acting as the CSAR Entry-Definitions file in an archive without TOSCA-Metadata directory.

tosca_definitions_version: tosca_simple_yaml_1_3

 

metadata:

  template_name: my_template

  template_author: OASIS TOSCA TC

  template_version: 1.01.1

 

Regards,

Thinh

 

From: Calin Curescu <calin.curescu@ericsson.com>
Sent: Tuesday, July 9, 2019 8:51 AM
To: Nguyenphu, Thinh (Nokia - US/Dallas) <thinh.nguyenphu@nokia.com>; tosca@lists.oasis-open.org
Subject: Re: [tosca] YAML v1.2: CSAR zip without TOSCA-Metadata directory clarification

 

Hi Thinh,

 

You are right, this is an inherited problem for versions up to v1.3 that has been corrected in v2.0.

 

In v2.0 we use for the version of the CSAR structure and TOSCA.meta file to be the following:

• If there exists a TOSCA.meta then we use the keyword CSAR-Version inside the TOSCA.meta file
• If there is no TOSCA.meta then we infer the CSAR version from the tosca_definitions_version keyword in the Entry-Definitions file (not from the metadata). For tosca_definitions_version: tosca_2_0 and onwards, the corresponding CSAR-version is 2.0 unless further defined.

 

BR,

/Calin

 

From: <tosca@lists.oasis-open.org> on behalf of "Nguyenphu, Thinh (Nokia - US/Dallas)" <thinh.nguyenphu@nokia.com>
Date: Monday, 8 July 2019 at 23:51
To: "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
Subject: [tosca] YAML v1.2: CSAR zip without TOSCA-Metadata directory clarification

 

Hello,

I may discover an inconsistence within TOSCA YAML v1.2 and v1.3

 

https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/os/TOSCA-Simple-Profile-YAML-v1.2-os.html#_Toc528072962

 

states The CSAR-Version is defined by the template_version metadata section. In 6.3

 

6.3 Archive without TOSCA-Metadata

In case the archive doesnât contains a TOSCA-Metadata directory the archive is required to contains a single YAML file at the root of the archive (other templates may exits in sub-directories).

This file must be a valid TOSCA definitions YAML file with the additional restriction that the metadata section (as defined in 3.9.3.2) is required and template_name and template_version metadata are also required.

TOSCA processors should recognized this file as being the CSAR Entry-Definitions file. The CSAR-Version is defined by the template_version metadata section. The Created-By value is defined by the template_author metadata.

6.3.1 Example

The following represents a valid TOSCA template file acting as the CSAR Entry-Definitions file in an archive without TOSCA-Metadata directory.

tosca_definitions_version: tosca_simple_yaml_1_1

 

metadata:

  template_name: my_template

  template_author: OASIS TOSCA TC

  template_version: 1.0

 

but in 3.10.3.5 template_version

This optional metadata keyname can be used to declare a domain specific version of the service template as a single-line string value.

3.10.3.5.3 Example

template_version: 2.0.17

 

 

In YAML v1.2 or 1.3, there is two different version numbers. For the case of Archive without TOSCA-Metadata, the template_version: 1.0. Whereas, CSAR with TOSCA-Metadata directory, the CSAR-Version: 1.1

 

So, what is template_version the CSAR version for both type of CSAR structure?  What is normative requirement and value for template_version?

 

Regards,

Thinh

 

 

Thinh Nguyenphu

Bell Labs CTO

Nokia

thinh.nguyenphu@nokia.com

+1 817-313-5189