Versions Compared

Old Version 37

changes.mady.by.user Byung-Woo Jun

Saved on

compared with

New Version 38

changes.mady.by.user Byung-Woo Jun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Epic

User Story

Task

Description

Honolulu Plan?

JIRA

Size

(S/M/L/XL)

Priority

Support Onboard ETSI 3.3.1 SOL004 compliant VNF / CNF packages



  • Executive Summary- Enable a vendor provided ETSI SOL004 v3.3.1 compliant VNF package including an ETSI SOL001 VNF / CNF Descriptor to  be onboarded into ONAP for composition into an ONAP Network Service
    • Support for onboarding ETSI v3.3.1SOL004 VNF CSAR Packages with minimum CNF enhancements from 4.1.1
    • Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptor with minimum CNF enhancements from 4.1.1
    • 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.

Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2610

4 weeks for one designerHigh

Support for onboarding ETSI v3.3.1 SOL004 VNF CSAR Packages with minimum CNF enhancements from 4.1.1


  • SDC users need to onboard ETSI v3.3.1 SOL004 VNF CSAR Packages with minimum CNF enhancements from 4.1.1
    • Manifest File (e.g., MainServiceTemplate.mf): a new non-MANO artifact set identifier "onap_cnf_helm" - This would identify the "top-level" helm chart that can be used to deploy the CNF directly, i.e., without utilizing the LCM info the VNF Descriptor
      • e.g., onap_cnf_helm:

                            source: Artifacts/helm/helm_charts.yaml

  • note: to support the direct path, the VNFD could be optional (under discussion with ETSI NFV and ONAP Direct Path team)
  • SDC users should be also able to onboard the existing ETSI v2.6.1 SOL004 CSAR packages - one level backward compatibility needs to be supported
  • For backward compatibility support, SDC needs to check the package manifest file and metadata such as "compatible_specifcation_versions".
    • If it is 3.3.1+, SDC needs to follow a new onboarding path for the ETSI 3.3.1 version package.
    • If the version is prior to 3.3.1, SDC follows the existing 2.x onboarding path. 
  • The package version and its descriptor version should match.
Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3337


High


Determine the onboarding path based on manifest metadata
  • Determine the onboarding path based on the manifest file and metadata "compatible_specification_versions"
  • If the version is prior to 3.3.1, invoke the existing 2.x SOL004 VNF package onboarding path
  • Otherwise, invoke a new SOL004 VNF package onboarding path
  • SDC users should be able to choose the onboarding package version from SDC UI Category selection...to be discussed...



High


Create a new onboarding path for SOL004  3.3.1 VNF package
  • Create a new onboarding path for 3.3.1
    • Check the CSAR structure differences between 2.7.1 and 3.3.1
  • Handle additional artifacts for CNF, such as Helm Charts, Container Image file(s)
    • For the Non-ETSI CNF, handle an optional VNFD case
    • Handle container image files with the limited file size (up to 2MB); larger files will not be handled in this release; support of larger files requires huge effort (AMDOC's help is needed)



High

Support the SOL001 vnf_profile properties

SDC needs to support the SOL001 vnf_profile (toaca.databypes.nfv.VnfProfile) properties

Image Added


Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3380


High

















Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptors 


  • SDC users need to onboard ETSI v3.3.1 SOL001 VNF Descriptors
  • SDC users should be also able to onboard the existing ETSI v2.6.1/v2.5.1 SOL001 VNF Descriptors - one level backward compatibility needs to be supported
  • For backward compatibility support, SDC needs to recognize the properties changes (e.g., use the VNF package version) for the Version indication. 
  • SDC uses a separate onboarding process depending on the version.
Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2611



High


Determine the onboarding path based on metadata
  • Determine the onboarding path based on the VNFD package version "compatible_specifcation_versions"
  • If the version is v2.6.1/v2.5.1, invoke the existing SOL001 VNF onboarding
  • Otherwise, invoke a new SOL001 VNFD onboarding path






Create a new onboarding path for SOL001 VNFD 3.3.1
  • Create a new onboarding path for 3.3.1 VNFD
    • Check the VNFD differences between 2.5.1/2.7.1 and 3.3.1
    • Share the common/base SDC data type and node type to represent both 3.3.1 and 2.x; i.e., merge two structures for minimum impact
    • Note: This is the current SDC limitation without versioning, and it will be handled separately in the future.













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

  1. Add tosca.nodes.nfv.VDU.OsContainer type to vnfd_types - aligned with the IFA011 v4.1.1 specification
  2. Add mciopProfile type vnfd_types - aligned with the IFA011 v4.1.1 specification
  3. Allow OsContainerDesc to be in the VDU section - only one of tosca.nodes.nfv.VDU.osContainer or  tosca.nodes.nfv.VDU.compute in a VNFD
  4. Allow mciopProfile in VNF Descriptor


  • SDC needs to support new CNF properties / classes / schema / data models based on defined Information Models
  • SDC may use a separate onboarding process for CNF
  • No backward compatibility for CNF support is necessary
Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3351


High


Support minimum CNF enhancements from 4.1.1

Support the vnfd_type with CNF attributes from 4.1.1:

  1. Add tosca.nodes.nfv.VDU.OsContainer type to vnfd_types - aligned with the IFA011 v4.1.1 specification
  2. Add mciopProfile type vnfd_types - aligned with the IFA011 v4.1.1 specification
  3. Allow OsContainerDesc to be in the VDU section - only one of tosca.nodes.nfv.VDU.osContainer or  tosca.nodes.nfv.VDU.compute in a VNFD
  4. Allow mciopProfile in VNF Descriptor






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

  • No backward compatibility ; SDC supports only ETSI 3.3.1 VNFD mapping to SDC AID DM

VNF Mapping:

  • Define a new data type based on the org.openecomp.resource.abstract.nodes.VF with ETSI SOL001 VNF data type attributes.

    • Make the org.openecomp.resource.abstract.nodes.ETSI.VNF a superset of both tosca.nodes.nfv.VNF and org.openecomp.resource.abstract.node.VF
    • During VNF onboarding, SDC copies SOL001 VNF attribute contents to the corresponding attributes in the org.openecomp.resource.abstract.nodes.ETSI.VNF
      • In Guilin, SO NFVO, VFC and SVNFM get those SOL001 VNF attributes from the descriptor, not from AAI. So, AAI schema changes are not expected in Guilin.
    • SOL001 VNF attributes in SDC AID DM VNF will be visible to SDC UI, so SDC UI can change the attributes.
      • But the onboarded vendor ETSI package will note be changed by the SDC UI users in Guilin.
      • Since SO NFVO, VFC and SVNFM use only the original ETSI package, those changes will not be used in Guilin;
      • For the Honolulu release, it is under consideration
        • to sync up between those modified SOL001 VNF attributes and the vendor ETSI Package attributes 
        • to reflect those modified SOL001 VNF attributes in the orchestration
    • ONAP specific attributes that are inherited from the org.openecomp.resource.abstract.nodes.VF will be filled up by SDC (design time)
      • Those attribute contents will not be mapped back into the SOL001 VNF (reverse mapping). For that case, only the SOL001 VNF corresponding attributes will be copied

VDU Mapping:

  • Make the org.openecomp.resource.abstract.nodes.ETSI.VFC a superset of both tosca.nodes.nfv.Vdu and org.openecomp.resource.abstract.nodes.VFC
  • Note: the org.openecomp.resource.abstract.nodes.VFC represents design-time VFC, not VFC instances
  • During VNF onboarding, SDC copies SOL001 VDU attribute contents to the corresponding attributes in the org.openecomp.resource.abstract.nodes.ETSI.VFC
    • In Guilin, SO NFVO, VFC and SVNFM get those SOL001 VDU attributes from the descriptor, not from AAI. So, AAI schema changes are not expected in Guilin.
  • SOL001 VDU attributes in SDC AID DM VNF will be visible to SDC UI, so SDC UI can change the attributes.
    • But the onboarded vendor ETSI package will note be changed by the SDC UI users in Guilin.
    • Since SO NFVO, VFC and SVNFM use only the original ETSI package, those changes will not be used in Guilin;
    • For the Honolulu release, it is under consideration
      • to sync up between those modified SOL001 VDU attributes and the vendor ETSI Package attributes 
      • to reflect those modified SOL001 VDU / VFC attributes in the orchestration

VF-Module Mapping (Stretch goal)

  • SDC deduces the VF-Module from the SOL001 VNFD Policies>scaling_aspects>properties>aspects
  • Additional VF-Module attributes are deduced as the following table
  • SOL003 Adapter may need to transform the VF-Module back to the SOL001 VNFD policies for the scaling and healing requests from VNFM(s)

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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2617


Medium

(VF-Module mapping is a stretch goal)



Map VNF data type to SDC AID DM VFMap VNF data type to SDC AID DM VF





Map VDU data type to SDC AID DM VFCMap VDU data type to SDC AID DM VFC





Deduce VF-Module from VNFD PoliciesDeduce 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

  • SDC supports VDU mapping for osContainer to SDC AID DM
    • create a new NF type for CNF
  • SDC supports virtualCPD, MCIOP ...
  • note: need to discuss with the non-ETSI team for compatibility
    • try to have unified modeling between non-ETSI and ETS-based CNF modeling... To discuss with SO team...
    • Thinking about optional VNFD. If there is no VNFD, no mapping is necessary
Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3352


medium


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

  • no backward compatibility is necessary
  • SDC supports value changes and also adding properties

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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2881


medium


Enhance SDC UI for editing SOL001 VNF / CNF descriptor propertiesEnhance SDC UI for editing SOL001 VNF / CNF descriptor properties



























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
    • Compose 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.

Yes


Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3338

1 week for one designerHigh

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

  • SDC needs to support backward compatibility for 2.5.1/2.6.1?
  • SDC users need to create NS 
  • SDC users need to generate SOL007 NS package
Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3339


High


Enhance SDC design for creating v3.3.1 NSEnhance SDC design for creating v3.3.1 NS





Generate v3.3.1 SOL007 NS package

Generate v3.3.1 SOL007 NS package

  • No backward compatibility is necessary





















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

  • The NSD and its referenced VNF / CNF versions should be matched. 
  • During SDC references VNFs, SDC needs to validate the version of VNFs / CNF, based on the VNF / CNF descriptor metadata (version indicator in the metadata)
    • After 2.6.1, there is a version indicator in the metadata

Note:  cover the VNF version validation... SAP descriptor has a version...


Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3340


High


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

  • The versions of NS and sub models should be matched  













Support for compose VNFs with CNF enhancements


SDC users need to compose VNFs with CNF enhancements

note: virtual CPD ... version... TBD

Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3341


High


Enhance SDC to compose v3.3.1 VNFs with CNF enhancementsEnhance 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

  • map SOL001 NSD to SDC AID DM
  • support ETSI NS and NsVirtualLink only.. maybe more... TBD
  • support Interfaces

Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3342


Medium


Map v3.3.1 NSD to SDC AID DMMap v3.3.1 NSD to SDC AID DM





Suport InterfacesSuport 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


Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2882


Medium


Compose Service Templates referencing NSDsCompose Service Templates referencing NSDs



















Design Nested/Hierarchical ETSI SOL001 v3.3.1 Network Service Descriptor 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.
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2803


N/A

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 themNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3343


N/A

Support for using VNFs with CNF enhancements


Support design of Service templates, leveraging NSDsNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3344


N/A








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.
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3353


N/A

Support for onboarding Prototype v4.1.1 CSAR Packages


SDC needs to support onboarding prototype v4.1.1 CSAR packages with CNF artifacts and metadataNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3354




Support for onboarding Prototype v4.1.1 VNF/CNF Descriptor


SDC needs to support onboarding prototype v4.1.1 VNF/CNF descriptorNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3355




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 ModelNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3356




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 ServiceNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3357



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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2805


N/A

SDC supports onboarding of the 3.3.1 SOL004 PNF package includes SOL001 PNFD


  • SDC user needs to onboard ETSI 3.3.1 SOL004 PNF packages 
  • SDC needs to update onboarding procedure for v3.3.1
No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2837



N/A

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 DMNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2836


N/A

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.

  • Support for Cataloging and Preserving the original SOL007 package

  • Support for mapping of ETSI v3.3.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model

  • 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

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. 

No

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2801


N/A

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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2806


N/A

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 ServiceNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2811


N/A








Support ETSI Package Security and validation

ONAP supports vendor ETSI 3.3.1Package Security and validation

  • If the vendor package includes signature and certificate, ONAP supports the package security
Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2613

4 weeks for one designerHigh

  • SOL004 VNF/PNF Package security will be supported by SDC, based on the ETSI 3.3.1 package signature and certificate

ONAP SDC supports ETSI 3.3.1 SOL004 VNF/PNF Package security

Yes



  • SOL007 NS Package security will be supported by SDC, based on the ETSI 3.3.1 package signature and certificate

ONAP SDC supports ETSI 3.3.1 SOL007 NS Package security 

Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2614


High
Support of ETSI Package Validation

VNF SDK will support ETSI package validation for VNF and NSTBD

N/A

VNF SDK will support ETSI VNF package pre-onboarding for validation
VNF SDK will support ETSI VNF package pre-onboarding for validationTBD

N/A

VNF SDK will support ETSI NS package pre-onboarding for validation
VNF SDK will support ETSI NS package pre-onboarding for validationTBD

N/A

...