Onboard ETSI SOL007  compliant Network Service Descriptor packages  (ETSI Package Management-Guilin)

Enable a vendor provided 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

New component capabilities for Guilin, i.e. the functional enhancements, if applicable

1. Enables ONAP to onboard ETSI NFV SOL007 compliant Network Service packages to be onboarded into ONAP through SDC.

2. Enables those onboarded SOL007 packages to be cataloged and transformed into an ONAP Service that can be deployed directly by SO using the SOL005 NFVO Adapter or directly deployed via VF-C or an external NFVO.

3. Enables the ETSI NFV Network Service package to be distributed as an ONAP Service CSAR from SDC to other ONAP components (A&AI, DCAE, SO, ETSI Catalog, ...)

4. Enables the Network Service instances to be inventoried, monitored and LifeCycle Managed

New or modified interfaces

1. No interface changes expected

If they are modified, are they backwards compatible?

Interface naming (point to an example)

Consumed API from other projects

Published API

Reference to the interfaces.

(Reference to the the swagger.json file(s) whenever possible)

What are the system limits?

Support for packages compliant with version 2.7.1 of the ETSI NFV SOL004 and SOL001 specifications

Supoort for backwards compatibility with version 2.5.1 of the ETSI NFV SOL004 and SOL001 specifications

Involved use cases, architectural capabilities or functional requirements.

Listing of new or impacted models used by the project (for information only).

• Identify any High Level Information Model Requirements.   See: ONAP R7 Modeling High Level Requirements

  • Models based on information exchanges from Use Cases

  • Models documenting existing implementations

  • Forward looking models that may be implemented in future releases

• Describe how exposed APIs are mapped to information models

(list all the relevant Jira tickets)

SDC-2618: Mapping between SOL001 NSD and SDC AID DM/SDC Internal TOSCAClosed

Any other details that are specific to this functional enhancement or UseCase.