...
| TASK | VNF SDK S/W FUNCTION - DESCRIPTION | Release Priority | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| MANIFEST FILE (VNF SDK) vs FILE CHECK | Verifies the MANIFEST file (MainServiceTemplate.mf) and checks that the defined directories of the PNF package against the manifest file. for example the manifest file might say a files should exist: "Measurements: source: Artifacts/Deployment/Measurements/PM_Dictionary.yaml", the VNF SDK would check that the file PM_Dictionary.yaml exists in the actual PNF package. ASSOCIATED DEVELOPMENT:
| R4 HIGH | ||||||||||
| SOL004 PNF TAGS | Check keywords. needs VNF SDK to check the PNF keywords. in the MainServiceTemplate.mf there are new tags, pnf_product_name and pnf_provider_id, pnf_package_version, pnf_release_date_time and non_mano_artifact_sets; and the NON ETSI MANO artifact tags public tags. These public tags are under the "non_mano_artifact_sets". This would be NEW development in VNF SDK. ASSOCIATED DEVELOPMENT:
| R4 HIGH | ||||||||||
| TOSCA MetaFile LICENSE File Exists Check (VNF SDK) | VNF SDK may/will(?) check a License Check in the PNF package. TOSCA meta file points to a License. Just a check that the file exists no content check at all ASSOCIATED DEVELOPMENT: (Already Supported) | R4 HIGH | ||||||||||
| TOSCA MetaFile CERTIFICATE Check (VNF SDK) | CERTIFICATE check. In the PNF package it is expected that there will be MainServiceTemplate.cert. This is mentioned in the TOSCA MetaFile. For example, in the TOSCA MetaFile, it could be mentioned "Entry-Certificate: Artifacts/resource-gnodeb-template.cert". And VNF SDK would check to make sure that the resource-gnodeb-template.cert file exists in the mentioned directory, the Artifacts in this case. VNF SDK does not look inside this file. SOL004 has option 1 (sign each artifact individually) and option 2 (sign entire package). It would be nice if VNF SDK supported both Option 1 and Option 2. ASSOCIATED DEVELOPMENT:
| R4 HIGH | ||||||||||
| VALIDATION FOR META DATA CHECK (SOL004) | Following SOL004 Validation for Meta-Data file (ETSI) and Manufacturer file, this is the TOSCA.meta file that is part of the PNF Package. both VNF SDK implementing only meta-data option, in the package there is a meta file. Check TOSCA.meta, while this file is not mandatory, when it is included that it follows the SOL004 standard (ETSI). We expect that "TOSCA-Meta-Version" and "CSAR-Version" and "created by" are already supported, and new checks for "Entry definition, Entry-manifest, Entry-change-log, Entry-tests, Entry-certificates" would be new VNF SDK development work (needs to be verified) ASSOCIATED DEVELOPMENT:
| R4 HIGH | ||||||||||
| DESCRIPTOR | The descriptor. There is validation of the VNFD. PNF Descriptor: TOSCA descriptor, and validate the node type. Validation of TOSCA PNFD. Following TOSCA rules. Components required are there. (NEEDS INVESTIGATION) ASSOCIATED DEVELOPMENT:
| R4 HIGH | ||||||||||
| PNF PACKAGE TESTING | Enhancement of Package Testing. A item to make sure that integration testing is performed and that VNF-SDK supports the functions as will be described in the Requirements work. ASSOCIATED DEVELOPMENT:
| R4 HIGH | ||||||||||
| LOW PRIORITY / PUSHED TO R5 EL ALTO | ||||||||||||
| CREATE PACKAGE FUNCTION FOR PNF | The create package function creates the metadata files, and CSAR files. This needs to be modified to support SOL004. (NEEDS INVESTIGATION) [Low Priority] | R5 EL ALTO LOW PRI | ||||||||||
| TOSCA Metafile License Content Check | SDC license model check. Potential ARTIFACTS: Vendor license model & agrement, features. VNF can have >1 features, entitlement pool, license key pools, actual keys. [Low Priority] PUSH TO R5 EL ALTO. | R5 EL ALTO LOW PRI | ||||||||||
...