[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tosca] YAML v1.2: CSAR zip without TOSCA-Metadata directory clarification
Hi Calin My comments from yesterday was that in the second case without TOSCA.meta, why CSAR-version is required? In another words, why we need to handle CSAR version with tosca_definitions_version?
There is no difference for the CSAR structure in the case without TOSCA.meta between v1.1, v1.2 ,v1.3 and v2.0 , right? Why a TOSCA orchestrator needs to know the CSAR-version is this case? Regards shitao åää: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
äè Calin Curescu 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> Hello, I may discover an inconsistence within TOSCA YAML v1.2 and v1.3 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.
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
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 +1 817-313-5189 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]