Versions Compared

Old Version 90

changes.mady.by.user Byung-Woo Jun

Saved on

compared with

New Version 91

changes.mady.by.user Byung-Woo Jun

Saved on

Key

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

...

  • Onboard ETSI SOL004 compliant VNF packages 
    • Support for onboarding ETSI v2.7.1 SOL004 CSAR Packages (Link to ETSI SOL004 v2.7.1 )
    • Support for onboarding ETSI v2.7.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v2.7.1)
    • Support for mapping of ETSI v2.7.1 SOL001 VNF Descriptor into SDC AID Data Model
    • Support for using an ETSI v2.7.1 VNF in an ONAP Service
  • Onboard ETSI SOL007 compliant Network Service Descriptor packages (stretch goal for Guilin)
    • 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
  • Design ETSI SOL007 compliant Network Service Descriptor packages
    • 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
  • Support for Nested/Hierarchical ETSI SOL001 v2.7.1 Network Service Descriptor (not for Guilin)
  • Design Service templates, leveraging NSDs
    • Support Service templates including NSDs

...

Epic

User Story

Description

Guilin Plan?

JIRA

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
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2610


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

Yes

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

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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2617


Support for editing ETSI v2.7.1 SOL001 VNF Descriptor
  • Support for editing ETSI v2.7.1 SOL001 VNF Descriptor
Yes

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-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 ONBOARDED_PACKAGE directory.
  • 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 ONBOARDED_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
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2957

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. 

Yesstretch goal

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-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)

Yesstretch goal

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2806


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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2618


Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVOSupport for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVONo

Close this, expect the current SDC distribution is sufficient


Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVOSupport for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVONo

Close this, expect the current SDC distribution is sufficient

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
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-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
  • Generate SOL007 NS package
Yes

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2808


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 VF-C as the NFVO

  • Wrap the NS package in the Service for VF-C
Yes

Close this, expect the current SDC distribution is sufficient


Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO

Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO

  • Wrap the NS package in the Service for an external NFVO
Yes

Close this, expect the current SDC distribution is sufficient

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. 

YesNo

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-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 ServiceSupport for onboarding of the SOL007 v2.7.1 compliant NSD package including SOL001 NSD that includes references to other NSDs for composition into ONAP ServiceYesNo

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-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. 

Yes

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-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
Yes

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-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 DMYes

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2836

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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2882


Support design of Service templates, includingNSDsSupport design of Service templates, including NSDsYes

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2883

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
Yes

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-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
Yes

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2814


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

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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-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
Yes

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-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
Yes

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-2614

Support of ETSI Package Validation
VNF SDK will support ETSI package validation for VNF and NSTBD

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

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

...

  1. At onboarding, SDC checks the file extension and performs the following procedures
    1. If the file is .zip, SDC unzips
      1. If it has .cert & .cms, it is a package with security and security validation will be performed.
      2. If it does not include .cert & .cms, it is an existing Heat template onboarding, and SDC follows the Heat template onboarding procedure
  2. If the file is .csar, it is a package without security.
  3. Next, SDC will check the TOSCA.meta file.
  4. If it contains SOL004v2.x.1 keywords, the package will be handled as SOL004v2.x.1. In the Guilin release, v2.7.1 will be supported.
  5. Otherwise, it will be handled as existing TOSCA (non-SOL004) package onboarding which will not have the ONBOARDED_PACKAGE artifact.


NS Onboarding Design
  • extend OrchestrationTemplateProcessCsarHandler.java to handle SOL007
  • create ToscaSolModelDrivenConverterNS class
    • create NSdNodeTemplateTransformationEngine class
      • transform() to SDC AID DM NS
  • generate the SDC package for NS with the original vendor SOL007 NS package


VNF Onboarding Design
  • leverage the existing SOL004 VNF onboarding mechanism
  • create a transform class to transform to SDC AID DM VNF
  • generate the SDC package for VNF with the original vendor SOL004 VNF package


PNF Onboarding Design
  • leverage the existing SOL004 PNF onboarding mechanism
  • the transformation to SDC AID DM is already done
  • It is already done: generate the SDC package for PNF with the original vendor SOL004 VNF package

...

  1. SOL004 VNF/PNF and SOL007 NS Packages are onboarded to SDC.
  2. SDC creates its Resource CSAR by adding ONAP-specific files and metadata according to SDC procedure.
    1. For VNF onboarding, SOL001 VNFD is mapped to SDC Data Model.
    2. For NS onboarding, SOL001 NSD is mapped to SDC Data Model. Note: the SDC NS Data Model would be SOL001 NSD-based.
    3. For PNF onboarding, SOL001 PNFD is mapped to SDC Data Model.
    4. The original SOL004 VNF/PNF and SOL007 NS packages will be stored in the ONBOARDED_PACKAGE directory.
    5. SDC shall have a capability to design SOL007 NSDs and generates SOL007 NS packages
      1. Since SDC does not have a proper NS Model, it will follow SOL001 NSD.
    6. SDC embeds the Resource CSAR into its Service CSAR for distribution.
      1. After SDC validates the onboarded packages, the Service CSAR is distributed.
      2. SDC sends the package notification to DMaaP for its package notification subscribers.
  3. ETSI Catalog Manager receives the package notification from SDC.
    1. ETSI Catalog Manager queries SDC for the SDC CSAR.
      1. ETSI Catalog Managers examines the SDC CSAR. If the SDC CSAR contains the ONBOARDED_PACKAGE directory, it extracts the SOL004/SOL007 packages from the directory.
      2. ETSI Catalog Manager stores the SOL004/SOL007 packages to its Catalog Database.
    2. ETSI Catalog Manager provides APIs for the SOL003/SOL005 Adapters to distribute the packages to SVNFM/NFVO.


Design NS


NSD Structure


SDC supports NSD design that meets the following requirements.
  • The NSD shall reference the VNFDs applicable to its constituent VNFs.
  • The NSD shall include the VLDs applicable to the VLs used by the NS to interconnect its constituent NFs.
  • The NSD shall reference the PNFDs applicable to its constituent PNFs.
  • The NSD shall include the descriptors of the VNFFGs applicable to the NS (stretch goal).
  • The NSD shall support the capability to include or reference NS LCM scripts.
  • The NSD shall support the capability to providing monitoring parameters to be tracked during the lifetime of a NS instance (stretch goal).
  • The NSD shall support the capability to describe auto scale rules, associating criteria to scaling actions (stretch goal).
  • The NSD shall include package security information enabling validating its authenticity and integrity.
  • The NSD shall include a globally unique identifier for identifying each descriptor instance.
  • The NSD shall include an identifier to select to controller compatible with the NSD.
  • A VLD shall enable specifying the type of connectivity provided by the link between VNFs.
NSD Information Element
  • SDC supports the following NSD Information Elements.
  • SDC supports the netestedNsdId(s) for nested NSDs. (not for Guilin)
  • SDC UI should be able to manage the NSD attributes.
  • SDC supports the virtualLinkDesc(s) to define constituent VLs.

...

  • SDC should be able to reference the vCPE NSD from the E2E Service model.
  • SDC should be able to reference all the constituent VNFs and VL(s).

Last

Latest vCPE CSARs

The latest (Frankfurt) vCPE CSARs can be retrieved from the https://git.onap.org/demo/tree/tosca/vCPE_F. There are one NS CSAR and five VNF CSARs:

...

NSD Design Process in SDC

VNF Composition

The following diagram depicts how SDC

...

Gliffy Diagram
macroId14dfe481-db49-4ccf-b9cc-f79f02ca930e
nameDesign SOL007 NS package
pagePin4

VL Composition
  • SDC supports NSVLDs that are defined in the ETSI IFA 014, as part of NS design.
  • SDC UI should be able to handle the following VLD attributes.



VNFD Composition

The NSD references the VNFD of a constituent VNFs.

...

The following depicts the VNFD information element.

SapD Composition

SapD fulfills the following information element.

...

<tosca.datatypes.nfv.NsProfile>

Current SDC NSD

SDC TOSCA repository: /catalog-be/src/main/resources/import/tosca/nfv-types/NSD/

  • need to update to tosca_simple_yaml_1.2

<nodes.yml: org.openecomp.resource.vfc.NSD>

...