[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Draft text for NFV Profile convention
|
I should also say that I think the vote on CSD03 can be made without the last slide. Thanks! John From: John Crandall
Thinh, We should discuss whether this statement is still needed. But if we do, could you provide text for the how you would like bullets 1-3.
Also, I think you want bullet 4 removed and the editor comment removed? John From: Nguyenphu, Thinh (Nokia - US/Irving) [mailto:thinh.nguyenphu@nokia.com]
Hi, I am resending my comment for slide 3 of Publish Profile for NFV based on phase 1 implementation.pptx. Regards, Thinh From: Nguyenphu, Thinh (Nokia - US/Irving)
Hi, My comments are following: This architecture encompasses support of the ETSI VNF Packaging Specification and Network Service Template Specification. To that end, the following conventions are followed:
・
Express the ETSI IFA specification using existing TOSCA normative types
in the TOSCA Simple Profile 1.2
[Thinh] a)For data structures or node types, if TOSCA had a type that covered an ETSI concept but did not match it perfectly, then a new TOSCA type has been introduced based on the ETSI data content. As a result, almost all types
have been derived from the corresponding root type.
b) As I recalled from last week call, it was suggested by Matt to use TOSCA Simple Profile 1.1 because all of the 1.1. features are completed and document is out for CSDPR. My general comment is that if the ETSI IFA requirements
which requires either add or modify existing types in the Simple Profile YAML 1.1, would this take into effect of version 1.2 or later. It is not clear to me when version 1.2 will be CSD status or CSDPR. What is version 1.2 timeline?
・
Express the subset of ETSI IFA information required for correct orchestration. #
comments
[Thinh] it is not clear what is the intent of above bullet point. What is “for correct orchestration”. My understanding from the scope of work in ETSI SOL001 is that it only cover the development of VNFD and NSD template only. These
templates will be used by NFVO and VNFM as defined in ETSI NFV IFA specifications.
・
It is not required that the TOSCA NFV profile match ETSI IFA information model entities with the same names
[Thinh] Name is not a problem. The challenges are in the structure and association with other attributes. See my comment on bullet 1a.
・
The TOSCA NFV Profile will clearly identify the information from ESTI IFA that it will express and the mapping between the TOSCA and ESTI IF information models.
[Thinh] my understanding is that the proposal solution includes the mapping of IFA IE and attributes to TOSCA types, properties, requirements, etc. At least Nokia proposals mapping tables are included as discussion part of the proposal.
・
TOSCA types created to support ETSI IFA for each version of the TOSCA NFV profile must evolve in a manner that support combining older and newer
types in the same service template (i.e. you don’t have to change old templates or parts of a template to support the new types).
[Thinh] What is the purpose or intent of this bullet? My understanding is that [TOSCA Simple Profile for NFV 1.0] is the first profile based on ETSI NFV IFA011 and IFA014. So, there is older service template.
Editor note: It was expressed on the AdHoc call that inheritance and artifacts should be used to incorporate the IFA additions.
Should this be explicitly stated?
[Thinh] No. my recommendation is to remove editor note. Thinh From:
tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
On Behalf Of Lishitao From NFv&SDN adhoc 10.19 发件人:
tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
代表 John Crandall Sorry for the delay… I had it my drafts from Thursday but forgot to send it. Best! John This architecture encompasses support of the ETSI VNF Packaging Specification and Network Service Template Specification. To that end, the following conventions are followed:
・
Express the ETSI IFA specification using existing TOSCA normative types
in the TOSCA Simple Profile 1.2
・
Express the subset of ETSI IFA information required for correct orchestration. #
comments
・
It is not required that the TOSCA NFV profile match ETSI IFA information model entities with the same names
・
The TOSCA NFV Profile will clearly identify the information from ESTI IFA that it will express and the mapping between the TOSCA and ESTI IF information models.
・
TOSCA types created to support ETSI IFA for each version of the TOSCA NFV profile must evolve in a manner that support combining older and newer types in the same service template (i.e. you don’t have to change
old templates or parts of a template to support the new types).
Editor note: It was expressed on the AdHoc call that inheritance and artifacts should be used to incorporate the IFA additions.
Should this be explicitly stated? |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]