...

The following things are still under discussion and investigation:

PACKAGE DELIVERY: PNF PACKAGE LICENSING

The PNF package "shall" have a Licensing.term (file)

This is also still under discussion (driven from the standards)

This section will be updated with what is contained in the actual PNF package.

PNF PRE-ONBOARDING: VNF-SDK ENHANCEMENTS

...

The work-flows are created by SDC DS.

...

DESIGN TIME ACTIVITIES:

...

LICENSING MANAGEMENT & SCHEMA

DEFINITION: The licensing schema could vary and be dependent upon the service provider. Licensing schema is expected to be used to identify or authorize the existence a particular PNF into the network of the service provider. It might also be possible that multiple licenses are needed for different functions or authentication. It may also be important to provide a license during PNF Plug and Play. This implies that the Service Provider has defined a licensing schema or has licensing management software to manage licenses.

R4 DUBLIN: For Dublin, it is to be determined what will be done (maybe nothing). This is likely to be FUTURE work (El Alto and beyond)

Note: SDC adds files related to Licensing AFTER Onboarding.

RUN TIME ACTIVITIES: CSAR INGESTION TO ONAP RT PLATFORM COMPONENTS

Inclusion of PNF artifacts into CSAR package, and ingestion of CSAR package by ONAP Run-Time Components and verification of reception and use.

Before it was assumed that VNFs are distributed, in Dublin PNF artifacts are distributed. So for example SO looked for Heat Templates (which were only applicable for VNFs). We need to insure that the distribution of PNF artifacts does not break the ONAP platform components. Some ONAP RT assume that any package notification only have VNF artifacts. In practice, there is only the subscription of artifacts (listeners) and the distribution of the PNF package, we need to make sure this behaves correctly and that there are no errors. Pre-integration checks and validation that the distribution of PNF artifacts will not cause side effects. Want to insure that FM & PM artifacts are distributed properly. PM dictionary would be used in DCAE & PM Mapper. FM Meta Data is new, and from the start (what is new in Dublin) is that it is being used for both VNFs and PNF.

The NF Package is composed of Artifacts, Definitions, TOSCA-MetaData.

Image Added

SDC CSAR Package Structure

Csar Structure

SDC Support Artifacts:

SDC supported artifact types

Inclusion of PNF artifacts into CSAR package, and ingestion of CSAR package by ONAP Run-Time Components and verification of reception and use.

Before it was assumed that VNFs are distributed, in Dublin PNF artifacts are distributed. So for example SO looked for Heat Templates (which were only applicable for VNFs). We need to insure that the distribution of PNF artifacts does not break the ONAP platform components. Some ONAP RT assume that any package notification only have VNF artifacts. In practice, there is only the subscription of artifacts (listeners) and the distribution of the PNF package, we need to make sure this behaves correctly and that there are no errors. Pre-integration checks and validation that the distribution of PNF artifacts will not cause side effects. Want to insure that FM & PM artifacts are distributed properly. PM dictionary would be used in DCAE & PM Mapper. FM Meta Data is new, and from the start (what is new in Dublin) is that it is being used for both VNFs and PNF.

The NF Package is composed of Artifacts, Definitions, TOSCA-MetaData.

Image Removed

SDC CSAR Package Structure

Csar Structure

SDC Support Artifacts:

SDC supported artifact types

PNF PRE-ONBOARDING: LICENSING MANAGEMENT

PNF PACKAGE LICENSING

The PNF package "shall" have a Licensing.term (file)

This is also still under discussion (driven from the standards)

This section will be updated with what is contained in the actual PNF package.

LICENSING MANAGEMENT & SCHEMA

DEFINITION: The licensing schema could vary and be dependent upon the service provider. Licensing schema is expected to be used to identify or authorize the existence a particular PNF into the network of the service provider. It might also be possible that multiple licenses are needed for different functions or authentication. It may also be important to provide a license during PNF Plug and Play. This implies that the Service Provider has defined a licensing schema or has licensing management software to manage licenses.

R4 DUBLIN: For Dublin, it is to be determined what will be done (maybe nothing). This is likely to be FUTURE work (El Alto and beyond)

Note: SDC adds files related to Licensing AFTER Onboarding.

STANDARDS & LICENSING (ETSI SOL004)

In ETSI SOL004 requires a "License.term", but it is still being defined & under discussion.

(this section will be updated when the standards have been finalized)

TESTING

Test Environment: TBD

...

Supporting documents related to PNF Onboarding

ETSI SOL Standards

The following has the ETSI SOL standards for your convenience

STANDARDS & LICENSING (ETSI SOL004)

In ETSI SOL004 requires a "License.term", but it is still being defined & under discussion.

(this section will be updated when the standards have been finalized)

APPENDIX: PNF Onboarding Artifacts

...