Brief Project Overview
- A schema update in relation to a xNFsoftware upgrades is a routine for network upgrade to support new xNF features, improve efficiency or increase xNF capacity on the field, and to eliminate bugs. This use case provides to ONAP an advantage in orchestrating and managing the Life Cycle of a Network Services in-line with business and service objectives.
- Deployment and orchestration of new services over CNFs, VNFs and PNFs in a model and software driven way simplifies the network management. Enables operators and service providers to manage the Life Cycle of a Network Service. Assuring continuity of operation of services is crucial for production and carrier grade environments. The actualization or upgrades of software and in consequence required changes in the service model is a natural part of service instance life cycle. Without the support of ONAP service update with schema change, service life cycle management by ONAP can be very difficult which can impact the quality and continuity of services.
New component capabilities for Guilin, i.e. the functional enhancements, if applicable
- Enables SDC to allow updating a resource template from a new onbaording package
- Enables SO to allow service level workflow to update a service instance with schema updates (with new xNF descriptor and new artifacts)
New schema update procedure:
1.A vendor shall provide
- a new VNF / PNF package with updated artifacts, and
- the new VNF/ PNF software image to the operator.
2.At receiving of the new package, the operator shall
- onboard the new package and create a new resource template or update the existing resource template (PNF / VNF)
- update the existing service template with the new or updated resource template
- distribute the updated service template to run time.
3.At run time, the operator shall, based on the updated service template,
- upgrade a service instance and its resource instances, and
- update the AAI entry accordingly
New or modified interfaces
Service model retrieving API |
Service level workflow retrieving API |
Service level workflow execution API |
If they are modified, are they backwards compatible?
N/A
Interface naming (point to an example)
above
Consumed API from other projects
Project | API Dependency | Notes |
---|---|---|
Published API
Project | API | Notes |
---|---|---|
AAI | ||
Reference to the interfaces.
(Reference to the the swagger.json file(s) whenever possible)
What are the system limits?
.
Involved use cases, architectural capabilities or functional requirements.
Listing of new or impacted models used by the project (for information only).
N/A