Onboard ETSI SOL004 compliant CNF/VNF packages (ETSI Package Management)
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
Support for onboarding ETSI v3.3.1 + CNF enhancements from IFA011 v4.1.1 SOL004 CSAR Packages (Link to ETSI SOL004)
Support for onboarding ETSI v3.3.1 + CNF enhancements from IFA011 v4.1.1 SOL001 CNF/VNF Descriptor (Link to ETSI SOL001)
Support for mapping of ETSI v3.3.1 + CNF enhancements from IFA011 v4.1.1 SOL001 CNF/VNF Descriptor into SDC AID Data Model
Support for using an ETSI v3.3.1 + CNF enhancements from IFA011 v4.1.1 CNF/VNF in an ONAP Service
New component capabilities for Honolulu, i.e. the functional enhancements, if applicable
- Enables ONAP to onboard ETSI NFV SOL004 compliant CNF/VNF packages to be onboarded into ONAP through SDC.
- Enables those onboarded VNF packages to be composed into an ONAP Service that can be deployed directly by SO using the SOL003 VNFM Adapter or an ETSI Network Service (NS) that can be deployed via VF-C or an external NFVO.
- Enables the VNF packages to be distributed inside an ONAP resource CSAR from SDC to other ONAP components (A&AI, DCAE, SO, ETSI Catalog, ...)
- Enables the VNF instances to be inventoried, 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 v3.3.1 of the ETSI NFV SOL004 and SOL001 specifications + CNF enhancements from IFA011 v4.1.1
Support 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 R8 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-2617 - Getting issue details... STATUS
SDC-2881 - Getting issue details... STATUS