...
The following requirements are defined in the Guilin Honolulu release - functional requirements proposed list, Guilin release - functional requirements proposed list.
Onboard ETSI SOL004 compliant VNF
...
packages
- Executive Summary- Enable a vendor provided ETSI SOL004
...
- v3.3.1
...
- compliant VNF package including an ETSI SOL001 VNF Descriptor to be onboarded into ONAP for composition into an ONAP Network Service
- Support for onboarding ETSI
...
- v3.3.
...
- 1SOL004 CSAR Packages with CNF enhancements
- Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptor
...
- with CNF enhancements
- Support for mapping of ETSI v3.3.1 SOL001 VNF Descriptor with CNF enhancements into SDC AID Data Model
...
- Business Impact- Enables operators and service providers to use same ETSI compliant VNF packages with ONAP and existing NFVO. Industry compatibility.
- Business Markets- All operators that are currently using ETSI packages to deploy VNFs
- Funding/Financial Impacts- Reduction in operations expense from using industry standard VNF packaging. Reduction in capital expense from vendors using a single packaging methodology.
- Organization Mgmt, Sales Strategies-There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Design ETSI SOL007 compliant Network Service Descriptor packages
- Executive Summary- Design, catalog and distribute an ETSI SOL007
...
- v3.3.1
...
- compliant Network Service Descriptor
...
- package including an ETSI
...
- v3.3.1
...
- SOL001 Network Service
...
- Descriptor (NSD) for deployment using an ETSI compliant NFVO.
- Support for
...
- designing an ETSI SOL001 v3.3.1 compliant Network Service
...
- that can be deployed with an ETSI compliant NFVO
- Composed of one or more VNFs and the Virtual Links that connect them.
- Support for using VNFs with CNF enhancements
- Business Impact- Enables operators and service providers to use internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.
- Business Markets- All operators and service providers that are developing and deploying ETSI compatible Network Services
- Funding/Financial Impacts- Reduction in operations expense from using industry standard NSD packaging.
- Organization Mgmt, Sales Strategies-There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Design Nested/Hierarchical ETSI SOL001 v3.
...
- Support for deploying a service that contains an ETSI SOL001 v3.3.1 compliant Network Service using VF-C as the NFVO
- Support for deploying a service that contains an ETSI SOL001 v3.3.1 compliant Network Service using an external NFVO
...
3.1 Network Service Descriptor
...
- Support Service templates including NSDs
Feature Descriptions
...
Feature
...
Description
...
- SOL004 VNF/PNF Package includes SOL001 VNFD/PNFD with the original vendor package will be onboarded into SDC and distributed from SDC to SVNFM/External NFVO.
- SOL007 NS Package includes SOL001 NSD with the original vendor package will be onboarded into SDC and distributed from SDC to SVNFM/External NFVO.
- SDC supports design of ETSI SOL007 compliant NSD packages and distribute them to SVNFM/External NFVO
- SDC supports Nested/Hierarchical ETSI SOL001 v3.3.1 NSD onboarding and distribution to ONAP runtime components.
...
If the vendor package includes signature and certificate, ONAP supports the package security.
- SOL004 VNF/PNF Package security is supported by the package signature and certificate
- SOL007 NS Package security is supported by the package signature and certificate
- SDC will store the vendor package with signature and certificate in a zip format in the ETSI_PACKAGE directory
- ETSI Catalog Manager stores the vendor package zip files from the ETSI_PACKAGE directory
- SVNFM/NFVO extracts the vendor package zip/CSAR files with package validation
...
- VNF SDK will support SOL004 VNF package pre-onboarding for validation - optional
- VNF SDK will support SOL007 NS package pre-onboarding for validation - optional
package
- Executive Summary- Design an ETSI SOL007 v3.3.1 compliant Network Service Descriptor package including an ETSI v3.3.1 SOL001 Network Service Descriptor (NSD) that includes references to other Network Service Descriptors for deployment using an ETSI compliant NFVO.
- Composed of zero or more VNFs and one or more nested Network Services and the Virtual Links that connect them.
- Support for using VNFs with CNF enhancements
- Business Impact- Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.
- Business Markets- All operators and service providers that are developing ETSI compatible Network Services especially for 5G Slicing where each Slice Subnet is associated with a Network Service
- Funding/Financial Impacts- Reduction in operations expense from using industry standard NSD packaging.
- Organization Mgmt, Sales Strategies-There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Onboard Prototype Package based on ETSI IFA011 v4.1.1 supporting containerized VNF (CNF) packages
- Executive Summary- Enable a vendor provided ETSI SOL004 compliant containerized VNF package including an ETSI SOL001 VNF Descriptor with container enhancements to be onboarded into ONAP for composition into an ETSI Network Service
- Support for onboarding Prototype v4.1.1 CSAR Packages
- Support for onboarding Prototype v4.1.1 VNF Descriptor
- Support for mapping of Prototype v4.1.1 VNF Descriptor into SDC AID Data Model
- Support for using a Prototype v4.1.1 VNF in an ETSI Network Service
- Business Impact- Enables operators and service providers to use same ETSI aligned containerized VNF (CNF) packages with ONAP and existing NFVO. Industry compatibility.
- Business Markets- All operators that are currently using ETSI packages to deploy containerized VNFs (CNFs)
- Funding/Financial Impacts- Reduction in operations expense from using industry standard containerized VNF (CNF) packaging. Reduction in capital expense from vendors using a single packaging methodology.
- Organization Mgmt, Sales Strategies-There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Feature Descriptions
Feature | Description |
---|---|
Epic and User Story
Epic | User Story | Description | Honolulu Plan? | JIRA | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Onboard and DesignETSI SOL004 compliant VNF packages |
| Yes |
| |||||||||||||||||||||||
Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v3.3.1) | Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v3.3.1)
| Yes |
| |||||||||||||||||||||||
Support for mapping of ETSI v3.3.1 SOL001 VNF Descriptor into SDC AID Data Model | Support for mapping of ETSI v3.3.1 SOL001 VNF Descriptor into SDC AID Data Model VNF Mapping:
VDU Mapping:
VF-Module Mapping:
| Yes |
| |||||||||||||||||||||||
Support for editing ETSI v3.3.1 SOL001 VNF Descriptor |
| Yes |
| |||||||||||||||||||||||
Support for using an ETSI v3.3.1 VNF in an ONAP Service |
| TBD | ||||||||||||||||||||||||
Onboard ETSI SOL007 compliant Network Service Descriptor packages | Executive Summary - Onboard an ETSI SOL007 v3.3.1 compliant (Link to ETSI SOL007 v3.3.1) Network Service Descriptor package including an ETSI version 3.3.1 SOL001 Network Service Descriptor (NSD) to be onboarded into ONAP for composition into an ONAP Service or deployment using an ETSI compliant NFVO.
Business Markets - All operators and service providers that are developing ETSI compatible Network Services Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging. Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. | YesNo |
| |||||||||||||||||||||||
Support onboarding for Cataloging and Preserving the original SOL007 package | Support onboarding for Cataloging and Preserving the original SOL007 package (Link to ETSI SOL001 v3.3.1) | YesNo |
| |||||||||||||||||||||||
Design ETSI SOL007 compliant Network Service Descriptor packages |
| Yes (enhancements) |
Note: there is a PoC for this. Soon, the PoC design could be shared as initial input for discussions | |||||||||||||||||||||||
Design ETSI SOL001 NSD and generate | Design ETSI SOL007 compliant Network Service Descriptor & packages | Executive Summary - Design, catalog and distribute an ETSI SOL007 v3.3.1 compliant (Link to ETSI SOL007 v3.3.1) Network Service Descriptor package including an ETSI version 3.3.1 SOL001 Network Service Descriptor (NSD) for deployment using an ETSI compliant NFVO. Support for deploying a service that contains an ETSI SOL001 v3.3.1 compliant Network Service using an external NFVO Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility. Business Markets - All operators and service providers that are developing ETSI compatible Network Services Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging. Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. Descriptor & package | Design ETSI SOL001 NSD and generate ETSI SOL007 compliant Network Service package
| Yes (enhancement Yes (enhancements) |
Note: there is a PoC for this. Soon, the PoC design could be shared as initial input for discussions
| |||||||||||||||||||||
Support for mapping of ETSI Design ETSI SOL001 NSD and generate an ETSI SOL001 v3.3.1 compliant SOL001 Network Service Descriptor & package Design ETSI SOL001 NSD and generate ETSI SOL007 compliant Network Service package
| Support for mapping of ETSI SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
| Yes (enhancement) |
| |||||||||||||||||||||||
Support design of Service templates, leveraging NSDs | Support design of Service templates, leveraging NSDs | Yes |
| |||||||||||||||||||||||
Change the ONBOARDED_PACKAGE directory to ETSI_PACKAGE directory | Change the ONBOARDED_PACKAGE directory to ETSI_PACKAGE directory | Yes (enhancement) |
| |||||||||||||||||||||||
Design Nested/Hierarchical ETSI SOL001 v3.3.1 Network Service Descriptor package |
| Support for mapping of ETSI SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
| Yes (enhancement) |
|
| Support design of Service templates, leveraging NSDs | Support design of Service templates, leveraging NSDs | Yes |
| |||||||||||||||||
Support for onboarding of the SOL007 v3.3.1 compliant NSD package including SOL001 NSD that includes references to other NSDs for composition into ONAP Service | Support for onboarding of the SOL007 v3.3.1 compliant NSD package including SOL001 NSD that includes references to other NSDs for composition into ONAP Service | Yes | Change the ONBOARDED_PACKAGE directory to ETSI_PACKAGE directory | Change the ONBOARDED_PACKAGE directory to ETSI_PACKAGE directory | Yes (enhancement) |
| ||||||||||||||||||||
Onboard Prototype Package based on ETSI IFA011 v4.1.1 supporting containerized VNF (CNF) packages Support for Nested/Hierarchical ETSI SOL001 v3.3.1 Network Service Descriptor |
Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging.
| Yes | Jira | | ||||||||||||||||||||||
server | ONAP JIRA | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb||||||||||||||||||||||||
key | SDC-2803 | |||||||||||||||||||||||||
Support for onboarding of the SOL007 v3.3.1 compliant NSD package including SOL001 NSD that includes references to other NSDs for composition into ONAP Service | Support for onboarding of the SOL007 v3.3.1 compliant NSD package including SOL001 NSD that includes references to other NSDs for composition into ONAP Service | Yes |
| Onboard ETSI SOL004 compliant PNF packages | Executive Summary - Enable a vendor provided ETSI SOL004 compliant PNF package including an ETSI SOL001 PNF Descriptor to be onboarded into ONAP for composition into an ONAP Service Business Impact - Enables operators and service providers to use same ETSI compliant PNF packages with ONAP and existing NFVO. Industry compatibility. Business Markets - All operators that are currently using ETSI packages to deploy PNFs Funding/Financial Impacts - Reduction in operations expense from using industry standard PNF packaging. Reduction in capital expense from vendors using a single packaging methodology. Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. | Yes |
| |||||||||||||||||||
SDC supports onboarding of the SOL004 PNF package includes SOL001 PNFD
|
| Yes |
| |||||||||||||||||||||||
Support for mapping of ETSI v3.3.1 SOL001 PNF Descriptor into SDC AID Data Model | SOL001 PNFD 3.3.1 Mapping to SDC AID DM | Yes |
| |||||||||||||||||||||||
Support additional package artifact Indicators for ETSI packages and Non-ETSI packages | SDC supports additional package artifact types to split ETSI packages from other non-ETSI TOSCA packages
| Yes |
| |||||||||||||||||||||||
SDC Notification supports additional package artifact types to split ETSI package from other non-ETSI TOSCA packages | SDC (Notification) supports additional package artifact types to split ETSI package from other non-ETSI TOSCA packages
| Yes |
| |||||||||||||||||||||||
SDC client supports additional filtering on the artifact types for distinguishing between ETSI packages and Non-ETSI packages | SDC client supports additional filtering on the artifact types for distinguishing between ETSI packages and Non-ETSI packages
| Yes |
| |||||||||||||||||||||||
Support ETSI Package Security and validation |
| Yes |
| |||||||||||||||||||||||
|
| Done | ||||||||||||||||||||||||
|
| Yes |
| |||||||||||||||||||||||
Support of ETSI Package Validation | VNF SDK will support ETSI package validation for VNF and NS | TBD | ||||||||||||||||||||||||
VNF SDK will support ETSI VNF package pre-onboarding for validation | VNF SDK will support ETSI VNF package pre-onboarding for validation | TBD | ||||||||||||||||||||||||
VNF SDK will support ETSI NS package pre-onboarding for validation | VNF SDK will support ETSI NS package pre-onboarding for validation | TBD |
...
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
- SOL004 VNF/PNF and SOL007 NS Packages are onboarded to SDC.
- SDC creates its Resource CSAR by adding ONAP-specific files and metadata according to SDC procedure.
- For VNF onboarding, SOL001 VNFD is mapped to SDC Data Model.
- For NS onboarding, SOL001 NSD is mapped to SDC Data Model. Note: the SDC NS Data Model would be SOL001 NSD-based.
- For PNF onboarding, SOL001 PNFD is mapped to SDC Data Model.
- The original SOL004 VNF/PNF and SOL007 NS packages will be stored in the ETSI_PACKAGE directory.
- SDC shall have a capability to design SOL007 NSDs and generates SOL007 NS packages
- Since SDC does not have a proper NS Model, it will follow SOL001 NSD.
- SDC embeds the Resource CSAR into its Service CSAR for distribution.
- After SDC validates the onboarded packages, the Service CSAR is distributed.
- SDC sends the package notification to DMaaP for its package notification subscribers.
- ETSI Catalog Manager receives the package notification from SDC.
- ETSI Catalog Manager queries SDC for the SDC CSAR.
- ETSI Catalog Managers examines the SDC CSAR. If the SDC CSAR contains the ETSI_PACKAGE directory, it extracts the SOL004/SOL007 packages from the directory.
- ETSI Catalog Manager stores the SOL004/SOL007 packages to its Catalog Database.
- ETSI Catalog Manager provides APIs for the SOL003/SOL005 Adapters to distribute the packages to SVNFM/NFVO.
- ETSI Catalog Manager queries SDC for the SDC CSAR.
...