...
1) In FRANKFURT timeframe SDC is going to implement the PNF package onboarding in line with the agreed non-MANO artifact set identifiers. (JIRA TICKET)
2) Register the NON-MANO artifact set identifiers in ETSI and update the reference ONAP page (add the reference)
3) Document the ONAP non-MANO artifact set identifiers in the VNF RQT as new ONAP requirements.
...
5) Is CMCC going to test Onboarding Package for VNF in ElAlto ? Can we extend the onboarding package support to VNF ? (Jira ticket ?)
PNF ONBOARDING PACKAGE EXAMPLE WITH USING NON-MANO ARTIFACTS in FRANKFURT
...
A reference PNF CSAR PACKAGE as example is available dummyPnfv2.csar (TO BE UPDATED) to review directories structure and new .meta and .mf files format.
...
Files related to example signed packages here
ACTIONS
1) ACTION: finalize the list public identifiers to be proposed in ETSI and analyze further ETSI process - COMPLETED
2) ACTION: VNF SDK is going to implement package security according to ETSI SOL004. TO be further verified if option 1 and/or 2 will be supported.
3) SDC has a Jira ticket tracing the Security introduction support in the package. Certification Certification files as they could differ according to the type of security option provided by the vendor (NOT PROVIDED IN THE EXAMPLE )
4) How to map the non-MANO artifact files to the SDC artifacts type?
5) ChangeLog.txt, a human readable text file at the root or in a location identified in the .meta file. (NOT PROVIDED IN THE EXAMPLE BELOW)
6) A license term file for the xNF located in a directory named Licences located at the root or in a location identified in the .meta file (NOT PROVIDED IN THE EXAMPLE BELOW)