Page Comparison

During the 4 August 2017 virtual meeting, the VNF SDK Models sub-project reached consensus on the

...

recommendations with respect to the VNF Package Model and the VNF Descriptor Model for ONAP Release 1 (Amsterdam): specifically the VNF package model should endorse the ETSI NFV SOL004 v2.3.1 based CSAR Option 2 with focus on Manifest file.

Decision revisited and amended on 25 August 2017, as part of the VNF SDK Project Meeting based on time constraints driven by VF-C and VNF-vendors supplying the VNF's for ONAP R1.

Discussed revised references during 1 September 2017 call

TOSCA version spec: TOSCA Simple Profile in YAML Version 1.1 TOSCA CSAR-Version: 1.1 With option 1 (a TOSCA-Metadata directory ): Manifest file: CSAR package support with and without manifest file

VNF Package Model Proposal for Release 1

TOSCA Simple Profile in YAML Version 1.1 (updated 1

...

Keep
SEP 2017)
TOSCA CSAR-Version: 1.1 With option 1 (a TOSCA-Metadata directory ): Manifest file: CSAR package may optionally support with manifest file (for integrity check) (updated 1 SEP 2017)
~~CSAR format compatible with what is used by the VF-C project (25 AUG 2017)~~
~~CSAR format for R1 is to be based on TOSCA 1.~~0 ~~1 CSAR format with Metadata Files (25 AUG 2017)~~
~~ETSI NFV SOL004 v2.3.1 focus on Manifest~~
~~(Optionally consider VNF Package model draft requirements in VNFRQTS-28 for beyond Release 1)~~
Proposal for ONAP CSAR R1 are uploaded in the modeling contribution files directory https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/822607816231987/ONAP_CSAR.pptx?api=v2
With a focus on the VNF Package Structure (Option 2): TOSCA YAML CSAR without Metadata File
Note: Team will continue to evolve the models beyond this recommendation.