Page History

...

Epic

User Story

Description

Guilin Plan?

JIRA

Maintenance

Support the substitution_mappings in the VNFD.

Currently, the substitution_mappings is not supported by SDC. Lack of this support blocks SOL004 VNF package management and ETSI Catalog Manager:

Prior to Frankfurt, as a workaround, the operator creates a dummy VNF without the substitution_mappings or node_types in the MainServiceTemplate.yaml and added a real VNF package with the substitution_mappings and user-define nodes in its Artifacts>DEPLOYMENT>OTHER directory.
It is to trick the current SDC onboarding issues because SDC does not check the OTHER directory.
In the Frankfurt/Dublin release, SDC was enhanced to support the vendor VNF package in the ETSI_PACKAGE directory.
In the Guilin release, the ONBOARDED_PACKAGE directory is changed to the ETSI_PACKAGE.
Since SDC Frankfurt/Dublin, we don't have to use the secondary VNF package unnecessary, but we still needs to follow an old way because of lack of substitution_mappings and user-defined node_types.
When SDC supports the subscription_mappings user-defined node types, the vendor VNF package does not have to add another VNF package in the Artifacts>DEPLOYMENT>OTHER directory, and the ETSI Catalog Manager will support the VNF package in the ETSI_PACKAGE directory.
- ETSI Catalog Manager will depend on this SDC support.

Support of the substitution_mappings and user-defined node_types will remove the issues and support ETSI package management and others.

Support of the user-defined node types is handled by another task. This task needs to handle the substitution_mappings only.

For the testing, use the vgw6.csar

For the Frankfurt release workaround, we added the following to the MainServiceTemplate.yaml, so the ETSI Catalog Manager can retrieve the descriptor_id from the metadata, instead of from the node_type. Once the substitution_mapping is supported by SDC, we don't have to use the descriptor_id in the metadata section.

descriptor_id: b1bb0ce7-2222-4fa7-95ed-4840d70a1177

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2957

Onboard and Design ETSI SOL004 compliant VNF packages

Executive Summary - Enable a vendor provided ETSI SOL004 compliant VNF package including an ETSI SOL001 VNF Descriptor to be onboarded into ONAP for composition into an ONAP Service

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.

No

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2610

Support for onboarding ETSI v2.7.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v2.7.1)

Support SDC AID DM VF descriptor (see the
79200568 section)

No

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2611

Support for mapping of ETSI v2.7.1 SOL001 VNF Descriptor into SDC AID Data Model

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

Onboard and Design ETSI SOL004 compliant VNF packages

Executive Summary - Enable a vendor provided ETSI SOL004 compliant VNF package including an ETSI SOL001 VNF Descriptor to be onboarded into ONAP for composition into an ONAP Service

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

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2610

Support for onboarding ETSI v2.7.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v2.7.1)

Support SDC AID DM VF descriptor (see the
SOL0012.7.1VNFDMappingfrom/toSDCAIDDMVNFD section)

Yes

Image RemovedSDC-2611 - SDC supports onboarding of the SOL004 VNF Package includes SOL001 VNFD OPEN

Support for mapping of ETSI v2.7.1 SOL001 VNF Descriptor into SDC AID Data Model

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
- VNF
  - In Guilin, SO NFVO, VFC and SVNFM get those SOL001
  VDU
  - VNF attributes from the descriptor, not from AAI. So, AAI schema changes are not expected in Guilin.
- SOL001
VDU
- 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
    VDU
    - VNF attributes and the vendor ETSI Package attributes
    - to reflect those modified SOL001
    VDU / VFC
    - VNF attributes in the orchestration

VF-Module Mapping:

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) – not part of Guilin

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2617

- 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:

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) – not part of Guilin

No

Support for editing ETSI v2.7.1 SOL001 VNF Descriptor

Support for editing ETSI v2.7.1 SOL001 VNF Descriptor

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2881

Support for using an ETSI v2.7.1 VNF in an ONAP Service

Support for using an ETSI v2.7.1 VNF in an ONAP Service

TBD

Support the substitution_mappings in the VNFD.

Currently, the substitution_mappings is not supported by SDC. Lack of this support blocks SOL004 VNF package management and ETSI Catalog Manager:

Prior to Frankfurt, as a workaround, the operator creates a dummy VNF without the substitution_mappings or node_types in the MainServiceTemplate.yaml and added a real VNF package with the substitution_mappings and user-define nodes in its Artifacts>DEPLOYMENT>OTHER directory.
It is to trick the current SDC onboarding issues because SDC does not check the OTHER directory.
In the Frankfurt/Dublin release, SDC was enhanced to support the vendor VNF package in the ETSI_PACKAGE directory.
In the Guilin release, the ONBOARDED_PACKAGE directory is changed to the ETSI_PACKAGE.
Since SDC Frankfurt/Dublin, we don't have to use the secondary VNF package unnecessary, but we still needs to follow an old way because of lack of substitution_mappings and user-defined node_types.
When SDC supports the subscription_mappings user-defined node types, the vendor VNF package does not have to add another VNF package in the Artifacts>DEPLOYMENT>OTHER directory, and the ETSI Catalog Manager will support the VNF package in the ETSI_PACKAGE directory.
- ETSI Catalog Manager will depend on this SDC support.

Support of the substitution_mappings and user-defined node_types will remove the issues and support ETSI package management and others.

Support of the user-defined node types is handled by another task. This task needs to handle the substitution_mappings only.

For the testing, use the vgw6.csar

For the Frankfurt release workaround, we added the following to the MainServiceTemplate.yaml, so the ETSI Catalog Manager can retrieve the descriptor_id from the metadata, instead of from the node_type. Once the substitution_mapping is supported by SDC, we don't have to use the descriptor_id in the metadata section.

descriptor_id: b1bb0ce7-2222-4fa7-95ed-4840d70a1177

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-29572617

Support for editing ETSI

Onboard ETSI SOL007 compliant Network Service Descriptor packages

Executive Summary - Onboard an ETSI SOL007 v2.7.1 compliant (Link SOL001 VNF Descriptor

Support for editing ETSI

to ETSI SOL007

v2.7.1 SOL001 VNF Descriptor

No

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2881

Support for using an ETSI v2.7.1 VNF in an ONAP Service

Support for using an ETSI v2.7.1 VNF in an ONAP Service

TBD

Onboard ETSI SOL007 compliant Network Service Descriptor packages

Executive Summary - Onboard an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1) Network Service Descriptor package including an ETSI version 2.7.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 v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO
Support for deploying a service that contains an ETSI SOL001 v2.7.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.

stretch goalNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2801

Support onboarding for Cataloging and Preserving the original SOL007 package

Support onboarding for Cataloging and Preserving the original SOL007 package (Link to ETSI SOL001 v2.7.1)

stretch goalNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2806

Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model

use SOL001 NSD as SDC AID DM

stretch goal

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2618

Design ETSI SOL007 compliant Network Service Descriptor & packages

Executive Summary - Design, catalog and distribute an ETSI SOL007 v2.7.1 compliant

Design ETSI SOL007 compliant Network Service Descriptor & packages

Executive Summary - Design, catalog and distribute an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1) Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) for deployment using an ETSI compliant NFVO.

Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO
Support for deploying a service that contains an ETSI SOL001 v2.7.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.

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2802

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 an ETSI SOL001 v2.7.1 compliant Network Service Descriptor & package

Design ETSI SOL001 NSD and generate ETSI SOL007 v2.7.1 compliant Network Service package

Create NS and compose NS with its sub components, such as VNFs, VLs, ~~VNF-FG~~ and dependencies between VNFs, etc. - final support scope will be defined
Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
- use SOL001 NSD as SDC AID DM
Generate SOL007 NS package

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2808

Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model

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

use SOL001 NSD as SDC AID DM
support only ETSI NS and NsVirtualLink only

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2618

Support design of Service templates, leveraging design of Service templates, leveraging NSDs

Support design of Service templates, leveraging NSDs

YesNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2882

Change the ONBOARDED_PACKAGE directory to ETSI_PACKAGE directory

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-3244

Support for Nested/Hierarchical ETSI SOL001 v2.7.1 Network Service Descriptor

Executive Summary - Onboard an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1) Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) that includes references to other Network Service Descriptors for composition into an ONAP Service or deployment using an ETSI compliant 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 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

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2803

Support for onboarding of the SOL007 v2.7.1 compliant NSD package including SOL001 NSD that includes references to other NSDs for composition into ONAP Service

No

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2811

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.

YesNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2805

SDC supports onboarding of the SOL004 PNF package includes SOL001 PNFD

PNFD onboarding is done and its regression testing will be done

SOL004 PNF package onboarding is done in Dublin but support v2.7.1
Update onboarding procedure for v2.7.1

YesNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2837

Support for mapping of ETSI v2.7.1 SOL001 PNF Descriptor into SDC AID Data Model

SOL001 PNFD 2.7.1 Mapping to SDC AID DM

YesNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2836

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

SDC (notification) generates additional artifact types
SDC client filters on the additional artifact types

YesNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2813

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

for SOL004 and SOL007 packages, artifact type = ONBOARDED_ETSI_PACKAGE
for non-ETSI TOSCA package, artifact type = ONBOARDED_ONAP_PACKAGE

YesNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2814

SDC client supports additional filtering on the artifact types for distinguishing between ETSI packages and Non-ETSI packages

for SOL004 and SOL007 packages, filtering for artifact type = ONBOARDED_ETSI_PACKAGE
for non-ETSI TOSCA package, filtering for artifact type = ONBOARDED_ONAP_PACKAGE

YesNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2815

Support ETSI Package Security and validation

ONAP supports vendor ETSI Package Security and validation
- If the vendor package includes signature and certificate, ONAP supports the package security

YesNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2613

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

ONAP SDC supports the package security

Done

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

ONAP SDC supports the package security

YesNo

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2614

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

TBD

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

TBD

...

Among the SOL004/SOL007 VNF package security options, the SDC supports the option2 as depicted below. In the option 2, there are two ways to zip the VNF packages, and SDC supports both.

SDC validates the VNF packages based on the embedded signature and certificate by leveraging CA.

Vendor SOL004/SOL007 VNF Package with certificate and signature is onboarded into SDC
- ZIP-format VNF package includes CSAR, Signature and Certificate
SDC validates VNF package based on the certificate and signature
SDC generates SDC internal model plus the vendor SOL004/SOL007 package CSAR and ZIP (with certificate and signature) – the supported format is TBD based on the security requirement

Image Removed

Package Security

A VNF package uses the signature and certificate to ensure package integrity and validity. A CSAR file is digitally signed with the VNF provider private key. During the VNF package onboarding to SDC, SDC validates the package and then does the following:

Transform SOL001-based VNFD into SDC internal models
Store the original Vendor package into the ETSI_PACKAGE directory
- If the original vendor package is a zip file with signature and certificate, the ETSI_PACKAGE directory will contain the zip file.
VNFM and VF-C will receive the zip-format file.
For Frankfurt, the SVNFM and external NFVO will receive a zip-format package with signature and certificate if the original vendor package contains signature and certificate.
- SVNFM and NFVO will unzip the incoming zip package files and extract CSAR files from the zip package files without validation.
- After the Frankfurt release, it is assumed that SVNFM and NFVO validate the incoming packages based on signature and certificate.

SOL001 Mapping to SDC AID DM

The following diagram depicts SOL001 Mapping to SDC AID DM.

Gliffy Diagram

macroId	c3089f5b-d8cc-4e90-8303-ad2808852d65
name	SOL001 Mapping to SDC AID DM - Guilin
pagePin	2

Current Mapping Support (as of Frankfurt)

Image Removed

Note: AAI impacts are under discussion.

Presentation Slide (as a summary)

The following is a presentation slide that summarizes the Mapping.

zip the VNF packages, and SDC supports both.

SDC validates the VNF packages based on the embedded signature and certificate by leveraging CA.

Vendor SOL004/SOL007 VNF Package with certificate and signature is onboarded into SDC
- ZIP-format VNF package includes CSAR, Signature and Certificate
SDC validates VNF package based on the certificate and signature
SDC generates SDC internal model plus the vendor SOL004/SOL007 package CSAR and ZIP (with certificate and signature) – the supported format is TBD based on the security requirement

Image Added

Package Security

A VNF package uses the signature and certificate to ensure package integrity and validity. A CSAR file is digitally signed with the VNF provider private key. During the VNF package onboarding to SDC, SDC validates the package and then does the following:

Transform SOL001-based VNFD into SDC internal models
Store the original Vendor package into the ETSI_PACKAGE directory
- If the original vendor package is a zip file with signature and certificate, the ETSI_PACKAGE directory will contain the zip file.
VNFM and VF-C will receive the zip-format file.
For Frankfurt, the SVNFM and external NFVO will receive a zip-format package with signature and certificate if the original vendor package contains signature and certificate.
- SVNFM and NFVO will unzip the incoming zip package files and extract CSAR files from the zip package files without validation.
- After the Frankfurt release, it is assumed that SVNFM and NFVO validate the incoming packages based on signature and certificate.

SOL001 Mapping to SDC AID DM

The following diagram depicts SOL001 Mapping to SDC AID DM.

Gliffy Diagram

macroId	c3089f5b-d8cc-4e90-8303-ad2808852d65
name	SOL001 Mapping to SDC AID DM - Guilin
pagePin	4

Current Mapping Support (as of Frankfurt)

Image Added

Note: AAI impacts are under discussion.

Presentation Slide (as a summary)

The following is a presentation slide that summarizes the Mapping.

Note:

The following is being implemented for the Guilin release:

SOL007 Design and SOL004 Onboarding
ONAP ETSI-Alignment Modeling Hierarchy (partially)
- NS Mapping
- NS-Level VirtualLink (between VNFs) Mapping

The following mapping will be implemented in the Honolulu release:

VNF Mapping
VDU and VFC Mapping
PNF Mapping
SOL001 VNFD and SDC AID DM VF Template Mapping
- VF-Module Deduction from SOL001 VNFD

View file

name	SDCEnhancementMapping-2020-9-4.pptx
height	250

SOL007 Design and SOL004 Onboarding

SDC takes the vendor provided package and adds some files or changes files and meta data according to SDC procedure.
SDC NS/VNF/PNF Onboarding Procedure and Original Vendor VNF/PNF Package Handling
- SDC onboarding enhancement was made to the SDC Dublin to support SOL004 PNF/VNF onboarding with .zip and .csar file extensions. We continue to support the current onboarding mechanism with some enhancements.
- SOL007 NS onboarding (stretch goal for Guilin) will follow the same procedure; i.e., storing the vendor SOL007 NS package into the “ETSI_PACKAGE” directory.
- SOL007 NS design will allow users to build SOL007 NS package including SOL001 NSD from scratch
- SDC VSP and Resource csar files have the “ETSI_PACKAGE” directory, which will contain the original vendor VNF/NS/PNF package.
  - The “ONBOARDED_PACKAGE” directory name will be changed to “ETSI_PACKAGE” as a common ETSI directory name. This change is necessary to support design of SOL007 package
  - ONAP-ETSI Catalog Manager will be extracted the ETSI packages from the “ETSI_PACKAGE” directory.
  - The VNFM and external NFVO use the original vendor VNF/NS/PNF packages through ETSI Catalog Manager.
SDC provides mapping from ETSI SOL001 NSD/VNFD/PNFD (PNF in the future) to SDC AID DM
- See the subsequent slides for mapping.
Note: ETSI 2.7.1 handling will be discussed separately.

SDC CSAR for NS structure

Mapping of ETSI Information NS-related Elements with TOSCA types

...

The following diagram depicts ONAP ETSI-Alignment Modeling hierarchy.
Note: the ONAP VFC model represents the design time VFC, not runtime VFC instance(s).
Note: VNF, VFC and PNF node types continue to be discussed for the Honolulu release.

Gliffy Diagram

size	1200
name	ONAP ETSI-Alignment Models
pagePin	4

...

SOL001 Data Model	SDC AID DM	Comments	Release
N/A	org.openecomp.resource.abstracts.nodes.service	represents OSS Service models
tosca.nodes.nfv.NS	tosca.nodes.nfv.NS	NS; use of SOL001 as SDC AID DM NS	Guilin
tosca.nodes.nfv.NsVirtualLink	tosca.nodes.nfv.NsVirtualLink	NS VirtualLink; use of SOL001 as SDC AID DM VL	Guilin
tosca.nodes.nfv.Vnf	org.openecomp.resource.abstract.nodes.ETSI.VNF	VNF	Plan for Honolulu
tosca.nodes.nfv.vdu	org.openecomp.resource.abstract.nodes.ETSI.VFC	VDU and SDC VFC	Plan for Honolulu
tosca.nodes.nfv.VirtualLink	org.openecomp.resources.vl	VNF VL	Plan for Honolulu
tosca.nodes.nfv.VduCp	org.openecomp.resources.cp	VDU CP	Plan for Honolulu
N/A	org.openecomp.resource.allottedResource	allotted resource; could not find any from SOL001
tosca.nodes.nfv.Pnf	org.openecomp.resource.abstract.nodes.ETSI.PNF	PNF	Plan for Honolulu (PNF support is under discussion for Honolulu

Current SDC Resource Models

...

SOL001 VNF (tosca.nodes.nfv.VNF)			Mapping	New SDC AID DM VNF (org.openecomp.resource.abstract.nodes.ETSI.VNF) derived from org.openecomp.resource.abstract.nodes.VF
name	required	type		name	required	type
<SOL001 tosca.nodes.nfv.VNF attributes >				<SOL001 tosca.nodes.nfv.VNF attributes >
descriptor_id	yes	string	<-->	descriptor_id	yes	string
descriptor_version	yes	string	<-->	descriptor_version	yes	string
provider	yes	string	<-->	provider	yes	string
product_name	yes	string	<-->	product_name	yes	string
software_version	yes	string	<-->	software_version	yes	string
product_info_name	no	string	<-->	product_info_name	no	string
vnfm_info	yes	list of string	<-->	vnfm_info	yes	list of string
localization_languages	no	list of string	<-->	localization_languages	no	list of string
default_localization_language	no	string	<-->	default_localization_language	no	string
configurable_properties	no	tosca.datatypes.nfv.VnfconfigurableProperties	<-->	configurable_properties	no	tosca.datatypes.nfv.VnfconfigurableProperties
modifiable_attributes	no	tosca.datatypes.nfv.VnfInfoModifiableAttributes	<-->	modifiable_attributes	no	tosca.datatypes.nfv.VnfInfoModifiableAttributes
lcm_operations_configuration	no	tosca.datatypes.nfv.VnfLcmOperationsConfiguration	<-->	lcm_operations_configuration	no	tosca.datatypes.nfv.VnfLcmOperationsConfiguration
monitoring_parameters	no	list of tosca.datatypes.nfv.VnfMonitoringParameter	<-->	monitoring_parameters	no	list of tosca.datatypes.nfv.VnfMonitoringParameter
flavour_id	yes	string	<-->	flavour_id	yes	string
flavour_description	yes	string	<-->	flavour_description	yes	string
vnf_profile	no	tosca.datatypes.nfv.VnfProfile	<-->	vnf_profile	no	tosca.datatypes.nfv.VnfProfile
				<SDC AID DM VF attributes that are inherited from org.openecomp.resource.abstract.nodes.VF>
<the followings are being considered>				nf_function	no	string
requirements	Yes			nf_role	no	string
interfaces	yes	tosca.interfaces.nfv.VnfLcm		nf_type	no	string
				nf_naming_code	no	string
				nf_naming	no	org.openecomp.datatypes.Naming
				availability_zone_max_count	no	integer
				min_instances	no	integer
				max_instances	no	integer
				multi_stage_design	no	boolean
				sdnc_model_name	no	string
				sdnc_artifact_name	no	string
				skip_post_instantiation_configuration	no	boolean (default true) constraints: true, false
				controller_actor	no	string (default: SO-REF-DATA) constraints: SO-REF-DATA, CDS, SDNC, APPC

...

Space shortcuts

Page tree

Versions Compared

Old Version 144

New Version Current

Key

Package Security

SOL001 Mapping to SDC AID DM

Current Mapping Support (as of Frankfurt)

Presentation Slide (as a summary)

Package Security

SOL001 Mapping to SDC AID DM

Current Mapping Support (as of Frankfurt)

Presentation Slide (as a summary)

SOL007 Design and SOL004 Onboarding

SDC CSAR for NS structure

Mapping of ETSI Information NS-related Elements with TOSCA types

Current SDC Resource Models