Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

During the 4 August 2017 virtual meeting, the VNF SDK Models sub-project reached consensus on the following recommendations with respect to the VNF Package Model and the VNF Descriptor Model for ONAP Release 1 (Amsterdam):

Decision revisited and amended on 25 August 2017, as part of the VNF SDK Project Meeting.

VNF Package Model Proposal for Release 1

  • Keep 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 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://wiki.onap.org/download/attachments/8226078/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.

VNF Descriptor Model Proposal for Release 1

  • VNF Descriptor be based on OASIS TOSCA NFV YAML Profile v1.0 CSD04 
  • For release 1 use of OASIS TOSCA NFV YAML Profile WD04-rev6 may be acceptable for the current implementations to help aid with backward compatibility
  • It is desirable to include Approved IFA011 Change Requests - VDU restructuring (i.e. key-value pair arrays)
  • (Optionally consider VNF Descriptor model draft requirements in VNFRQTS-28 for beyond Release 1)

  • Note: Team will continue to evolve the models beyond this recommendation.

----------------------------------------------------------------------------------------------------------------------------------------------------------


VNF Descriptor Model Starting Points (with public document links)...

  • Approved IFA011 Change Requests - VDU restructuring
    • Create pointers to opaque key/value pair arrays to specify EPA requirements
  • No labels