Modelling

Definition of Platform Info & Data model continues

Introduce/Refine PNF S/W version (get it review & approved)

Resource Data Model

Onboarding PNFD to Platform PNFD mapping development & enhancement

VNF-SDK (PNF-SDK)

Package Validation enhancements notable Package security (option 2 per artifact), SOL004 alignment, License Model Check.

PNF Onboarding Package

Further carry-over development from R4/Dublin for PNF onboarding process.

VNF Onboarding

VNF onboarding, same procedure, same function, but testing/integration was not completed in R4/Dublin.

Additional validation of security package.

VNFD Modeling transformation (PNFD was completed in R4)

VNF requirements document / Read the docs. DOCS project

VNF-RQTS project requirements update.

#8: PNF PACKAGE TESTING

(Test Only)

#6: PACKAGE SECURITY

(finished in R5 maybe some bug fixing in R6)

Driven from SOL004: Option 1 (Supported in R4 Dublin): TOSCA.meta (exists) Meta-directory based, XML based approach. Option 2 (NOT support in R4 Dublin): CSAR without TOSCA.meta. Manifest (.mf) file that has everything (so the TOSCA.meta is redundant). Yaml-based approach.

The Public Key a key to open the package. SOL004 Option 1, 2 and use key to open the package - X.509 certificates public key, private key to sign the package and private key correspond to the private key of the package also delivered with the package. a package, a signature, and public key certificate delivered together. There may be more than one signature. Option 1 there is a digest for every file. All of those digests are listed in the manifest file. The manifest file is signed, one signature on the manifest. One signature and one key/pair & 1 certificate. Still optional to sign other files. The signature is a file beside. myimage.iso myimage.xyz but the same file/directory. Every file signed should have a signature files. CSAR file signed in a .sm file, package signature. The public key is signed can be signed by a root certificate.

An X.509 certificate is a digital certificate that uses the widely accepted international X.509 public key infrastructure (PKI) standard to verify that a public key belongs to the user, computer or service identity contained within the certificate.

(investigate) if VNF-SDK would like to use AAF as the CA. Can AAF perform the CA functions.

To open the package need: (1) Public Key (to open the manifest file) (2) file input (3) certificate input. create a hash, the hash is verified against the signature. SHA-256

R5 (El Alto). Implemented Option 1 per artifact security (R4 had only Option 2 per package security). Had to fix a bug. No more is needed in R6.

R4

HIGH

The create package function creates the metadata files, and CSAR files. This needs to be modified to support SOL004. (NEEDS INVESTIGATION)

[Low Priority] - Likely to be pushed to R7 Guilin

R7 LOW PRI

SDC license model check. Potential ARTIFACTS: Vendor license model & agreement, features. VNF can have >1 features, entitlement pool, license key pools, actual keys.

[Low Priority] - Licensing Management Use Case is introduced in R6, so License content check will for POB/OB will happen in NEXT release R7 Guilin (at earliest)

R7

LOW PRI