Support for Nested/Hierarchical ETSI SOL001 compliant Network Service Descriptor (ETSI Package Management)
Enhancement to AR-002-R7-052020 & AR-003-R7-052020
Enable an ONAP user to Onboard or 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) that references other Network Service Descriptors for deployment as an ONAP Service or deployment using an ETSI compliant NFVO.
Support for Designing an ETSI NFV SOL001 v2.7.1 compliant Nested/Hierarchical Network Service Descriptor (NSD) (Link to ETSI SOL001 v2.7.1) that references other NSD using SDC
Support for Cataloging, Preserving and Distributing the NSD in an ETSI NFV SOL007 v2.7.1 package
Support for mapping the ETSI v2.7.1 SOL001 v2.7.1 Nested/Hierarchical Network Service Descriptor into SDC AID Data Model
Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Nested/Hierarchical Network Service using an ONAP internal NFVO
Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Nested/Hierarchical Network Service using an external NFVO
New component capabilities for Guilin, i.e. the functional enhancements, if applicable
- Enables an ONAP user to use SDC to design an ETSI NFV SOL001 v2.7.1 compliant Nested/Hierarchical Network Service that can be packaged into an ETSI NFV SOL007 v2.7.1 compliant package
- Enables those 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.
- Enables the ETSI NFV Nested/Hierarchical Network Service package to be distributed as an ONAP Service CSAR from SDC to other ONAP components (A&AI, DCAE, SO, ETSI Catalog, ...)
- Enables the Nested/Hierarchical Network Service instances to be Inventoried, Configured, Monitored and LifeCycle Managed
New or modified interfaces
- No interface changes expected
If they are modified, are they backwards compatible?
Interface naming (point to an example)
Consumed API from other projects
Project | API Dependency | Notes |
|---|---|---|
Published API
Project | API | Notes |
|---|---|---|
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 SOL007 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)