...
Feature | Description |
---|---|
Epic and User Story
Epic | User Story | Task | Description | Honolulu Plan? | JIRA | Size | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Support Onboard ETSI 3.3.1 SOL004 compliant VNF / CNF packages |
| Yes |
| |||||||||||
Support for onboarding ETSI v3.3.1 SOL004 VNF CSAR Packages with minimum CNF enhancements from 4.1.1 |
source: Artifacts/helm/helm_charts.yaml
| Yes |
| |||||||||||
Determine the onboarding path based on manifest metadata |
| |||||||||||||
Create a new onboarding path for SOL004 3.3.1 VNF package |
| |||||||||||||
Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptors |
| Yes |
| |||||||||||
Determine the onboarding path based on metadata |
| |||||||||||||
Create a new onboarding path for SOL001 VNFD 3.3.1 |
| |||||||||||||
Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptors with minimum CNF enhancements from 4.1.1 | SDC users need to onboard ETSI 3.3.1 with minimum CNF enhancements from 4.1.1
| Yes |
| |||||||||||
Support minimum CNF enhancements from 4.1.1 | Support the vnfd_type with CNF attributes from 4.1.1:
| |||||||||||||
Extend the 3.3.1 VNFD onboarding path for CNF attributes | Extend the 3.3.1 VNFD onboarding logic for CNF attribute handling | |||||||||||||
Support for mapping of ETSI v3.3.1 SOL001 VNF Descriptor into SDC AID Data Model | Once SDC onboards an ETSI v3.3.1 SOL001 VNF Descriptor, SDC needs to map the ETSI v3.3.1 SOL001 VNF Descriptor into SDC AID Data Model
VNF Mapping:
VDU Mapping:
VF-Module Mapping:
SDC supports Interface mapping to SDC AID DM for creating Service and connect VNF to external networking, etc |
. |
Capacity and requirement mapping won't be necessary in this release | Yes |
| |||||||||
Map VNF data type to SDC AID DM VF | Map VNF data type to SDC AID DM VF | ||||||||||
Map VDU data type to SDC AID DM VFC | Map VDU data type to SDC AID DM VFC | ||||||||||
Deduce VF-Module from VNFD Policies | Deduce VF-Module from VNFD Policies | ||||||||||
Map VNF Interfaces to SDC AID DM | Map VNF Interfaces to SDC AID DM | ||||||||||
Support for mapping of ETSI v3.3.1 SOL001 VNF Descriptor with minimum CNF enhancements from 4.1.1 into SDC AID Data Model | Once SDC onboards an ETSI v3.3.1 SOL001 VNF Descriptor with CNF enhancements, SDC needs to map the ETSI v3.3.1 SOL001 VNF Descriptor with minimum CNF enhancements from 4.1.1 into SDC AID Data Model
|
| Yes |
|
| ||||||
Map VNF with CNF properties to SDC AID DM | ||||||
Map VDU with CNF properties to SDC AID DM | ||||||
Map virtualCPD to SDC AID DM | ||||||
Map MCIOP to SDC AID DM |
Support for editing ETSI v3.3.1 SOL001 VNF / CNF Descriptor | SDC users should be able to edit onboarded ETSI v3.3.1 SOL001 VNF Descriptors
Note: should we reflect the changes to original vendor packages in ETSI_PACKAGE directory??? need to think about impact... SDC generates a new digital signature for the package and distributes it to ETSI Catalog Manager. | Yes |
| |||||||||||
Enhance SDC UI for editing SOL001 VNF / CNF descriptor properties | Enhance SDC UI for editing SOL001 VNF / CNF descriptor properties | |||||||||||||
Design ETSI SOL007 compliant Network Service Descriptor packages |
| Yes |
| |||||||||||
Support for designing an ETSI SOL001 v3.3.1 compliant Network Service that can be deployed with an ETSI compliant NFVO | SDC users need to design an ETSI SOL001 v3.3.1 compliant Network Service that can be deployed with an ETSI compliant NFVO
| Yes |
| |||||||||||
Enhance SDC design for creating v3.3.1 NS | Enhance SDC design for creating v3.3.1 NS | |||||||||||||
Generate v3.3.1 SOL007 NS package | Generate v3.3.1 SOL007 NS package
| |||||||||||||
Compose of one or more VNFs and the Virtual Links that connect them | SDC users need to compose one or more VNFs and the Virtual Links that connect them in NS
Note: cover the VNF version validation... SAP descriptor has |
Jira | ||||||
---|---|---|---|---|---|---|
|
a version... | Yes |
| |||||||||
Enhance SDC to compose v3.3.1 VNFs and VLs for v3.3.1 NS | Enhance SDC to allow compose v3.3.1 VNFs and VLs for v3.3.1 NS | ||||||||||
Validate NSD and VNFD version match | Validate NSD and VNFD version match
| ||||||||||
Support for compose |
VNFs with CNF enhancements | SDC users need to |
compose VNFs with CNF enhancements
| Yes |
| ||||||||||||
Enhance SDC to compose v3.3.1 VNFs with CNF enhancements | Enhance SDC to compose v3.3.1 VNFs with CNF enhancements | |||||||||||||
Support for mapping of ETSI v3.3.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model | SDC needs to support for mapping of ETSI SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
| Yes |
| |||||||||||
Map v3.3.1 NSD to SDC AID DM | Map v3.3.1 NSD to SDC AID DM | |||||||||||||
Suport Interfaces | Suport NS Interfaces to SDC AID DM | |||||||||||||
Support design of Service templates, leveraging NSDs | SDC users need to support design of Service templates, leveraging NSDs ONAP service references NSDs... | Yes |
| |||||||||||
Compose Service Templates referencing NSDs | Compose Service Templates referencing NSDs | |||||||||||||
Design Nested/Hierarchical ETSI SOL001 v3.3.1 Network Service Descriptor package |
| No |
| |||||||||||
Compose of zero or more VNFs and one or more nested Network Services and the Virtual Links that connect them | SDC users need to compose zero or more VNFs and one or more nested Network Services and the Virtual Links that connect them | No |
| |||||||||||
Support for using VNFs with CNF enhancements | Support design of Service templates, leveraging NSDs | No |
| |||||||||||
Onboard Prototype Package based on ETSI IFA011 v4.1.1 supporting containerized VNF (CNF) packages |
| No |
| |||||||||||
Support for onboarding Prototype v4.1.1 CSAR Packages | SDC needs to support onboarding prototype v4.1.1 CSAR packages with CNF artifacts and metadata | No |
| |||||||||||
Support for onboarding Prototype v4.1.1 VNF/CNF Descriptor | SDC needs to support onboarding prototype v4.1.1 VNF/CNF descriptor | No |
| |||||||||||
Support for mapping of Prototype v4.1.1 VNF/CNF Descriptor into SDC AID Data Model | SDC needs to support mapping of prototype v4.1.1 VNF/CNF Descriptor into SDC AID Data Model | No |
| |||||||||||
Support for using a Prototype v4.1.1 VNF in an ETSI Network Service | SDC needs to support for a prototype v4.1.1 VNF/CNF in an ETSI network Service | No |
| |||||||||||
Onboard ETSI 3.3.1 SOL004 compliant PNF packages | Executive Summary - Enable a vendor provided ETSI 3.3.1 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. | No |
| |||||||||||
SDC supports onboarding of the 3.3.1 SOL004 PNF package includes SOL001 PNFD |
| No |
| |||||||||||
Support for mapping of ETSI v3.3.1 SOL001 PNF Descriptor into SDC AID Data Model | SDC needs to support 3.3.1 SOL001 PNFD Mapping to SDC AID DM | No |
| |||||||||||
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. | No |
| |||||||||||
Support onboarding for Cataloging and Preserving the original SOL007 package | SDC users need to support onboarding for Cataloging and Preserving the original SOL007 package (Link to ETSI SOL001 v3.3.1) | No |
| |||||||||||
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 | SDC users need to 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 | No |
| |||||||||||
Support ETSI Package Security and validation | ONAP supports vendor ETSI 3.3.1Package Security and validation
| Yes |
| |||||||||||
| ONAP SDC supports ETSI 3.3.1 SOL004 VNF/PNF Package security | Yes | ||||||||||||
| ONAP SDC supports ETSI 3.3.1 SOL007 NS Package security | 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 |
ETSI Package Management Architecture
...