...
The following things are still under discussion and investigation:
PNF PRE-ONBOARDING:
...
VNF-SDK DEVELOPMENT
VNF SDK is responsible to validate the PNF package provided by the vendor.
Today, optionally, the VNF SDK is also able to provide
We expect the VNF SDK development to be able to reuse much of the functionality from VNF SDK, format delivery, processing are all the same except HEAT deployments templates are not used (as they do not apply to PNFs).
The VNF SDK will be used to VALIDATE the PNF Onboarding Package
It is possible for a user to bring in the PNF Onboarding Package (provided by a vendor) without the use of the PNF SDK tools.
Some of the NF artifacts are created by the SDC tool.
[INVESTIGATE] What are artifacts that SDC adds during the Onboarding process, looking at SDC supported artifact types, possibly VENDOR LICENSE and MODEL INVENTORY (are there others?)
PNF ONBOARDING: PNF ONBOARDING PACKAGE LOADED
PNF Onboarding Package (vendor provided) is successfully loaded into ONAP.
In Dublin timeframe, the focus is the onboarding package mapping in the internal package and AID model.
PNF ONBOARDING: SDC ONBOARDING PACKAGE MAPPING INTO INTERNAL PACKAGE
SDC is used to map the Vendor provided onboarding package & PNF descriptor into the Internal Package & Internal (Platform) Data Model
PNF ONBOARDING: SDC ONBOARDING PACKAGE INTO SDC CATALOG
SDC Design Studio is then used to define a Service, and the output of that is a CSAR package which defines the Service.
Enhancements to SDC to take PNF Onboarding Package into the SDC Catalog
SDC distributes services
NF CSAR package includes the artifacts and information for the resources for a service.
There is one CSAR file which includes all of the definition for that service.
The work-flows are created by SDC DS.
PNF ONBOARDING: CSAR INGESTION TO ONAP RT COMPONENTS
Inclusion of PNF artifacts into CSAR package, and ingestion of CSAR package by ONAP Run-Time Components and verification of reception and use.
The NF Package is composed of Artifacts, Definitions, TOSCA-MetaData.
SDC CSAR Package Structure
SDC Support Artifacts:
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)
...
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)
PNF PRE-ONBOARDING: VNF-SDK DEVELOPMENT
VNF SDK is responsible to validate the PNF package provided by the vendor.
Today, optionally, the VNF SDK is also able to provide
We expect the VNF SDK development to be able to reuse much of the functionality from VNF SDK, format delivery, processing are all the same except HEAT deployments templates are not used (as they do not apply to PNFs).
The VNF SDK will be used to VALIDATE the PNF Onboarding Package
It is possible for a user to bring in the PNF Onboarding Package (provided by a vendor) without the use of the PNF SDK tools.
Some of the NF artifacts are created by the SDC tool.
[INVESTIGATE] What are artifacts that SDC adds during the Onboarding process, looking at SDC supported artifact types, possibly VENDOR LICENSE and MODEL INVENTORY (are there others?)
PNF ONBOARDING: PNF ONBOARDING PACKAGE LOADED
PNF Onboarding Package (vendor provided) is successfully loaded into ONAP.
In Dublin timeframe, the focus is the onboarding package mapping in the internal package and AID model.
PNF ONBOARDING: SDC ONBOARDING PACKAGE MAPPING INTO INTERNAL PACKAGE
SDC is used to map the Vendor provided onboarding package & PNF descriptor into the Internal Package & Internal (Platform) Data Model
PNF ONBOARDING: SDC ONBOARDING PACKAGE INTO SDC CATALOG
SDC Design Studio is then used to define a Service, and the output of that is a CSAR package which defines the Service.
Enhancements to SDC to take PNF Onboarding Package into the SDC Catalog
SDC distributes services
NF CSAR package includes the artifacts and information for the resources for a service.
There is one CSAR file which includes all of the definition for that service.
The work-flows are created by SDC DS.
PNF ONBOARDING: CSAR INGESTION TO ONAP RT COMPONENTS
Inclusion of PNF artifacts into CSAR package, and ingestion of CSAR package by ONAP Run-Time Components and verification of reception and use.
The NF Package is composed of Artifacts, Definitions, TOSCA-MetaData.
SDC CSAR Package Structure
SDC Support Artifacts:
TESTING
Test Environment: TBD
...