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: Draft text for NFV Profile convention


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 and TOSCA NFV Profile Committee Specification Draft 03 as much as possible. New types will be created expressing ETSI IFA concepts and information not already available in TOSCA.

·         Express the subset of ETSI IFA information required for correct orchestration.

·         It is not required that the TOSCA NFV profile match ETSI IFA information model entities with the same names or representation.

·         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]