R8 PNF Software Upgrade enhancement
Table of Contents
Use Case Overview & Description
A schema update in relation to a xNF software 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. In Rel 8, the feature will be enhanced with PNF sw version management during sw upgrade procedure.
Use Case Key Information
TOPIC | DESCRIPTION | WIKI PAGE |
Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | Honolulu release - functional requirements proposed list#PNFSoftwareUpgradeenhancement |
Architecture S/C info | Information on the Architecture sub-committee presentation |
|
Prior Project "Base" Wiki | Link to the "base" wiki for the Use Case, or work from a prior release. | Support xNF Software Upgrade in association to schema updates |
Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case | |
Key Use Case Leads & Contacts | USE CASE LEAD: @Zu Qiang USE KEY CONTACTS: |
|
Meetings Register & Recordings | Link to Use Case Team meetings. |
|
BUSINESS DRIVER
Executive Summary: In Rel 6 (REQ-84) and Rel 7 (REQ-324), PNF sw upgrade requirement in ONAP has progressed covering both with/without schema updates.
A schema update in relation to a xNF software 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. In Rel 8, the feature will be enhanced with PNF sw version management during sw upgrade procedure.
Business Impact: 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.
Business Markets: All operators and service providers that are using ONAP for service and network function Life Cycle Management
Funding/Financial Impacts: Reduction in operations expense from using industry standard Interfaces.
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.
Development Status
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | @William Reehil |
|
|
AAF | @Jonathan Gathman |
|
|
APPC | @Takamune Cho |
|
|
CLAMP | @Gervais-Martial Ngueko |
|
|
CC-SDK | @Dan Timoney |
|
|
DCAE | @Vijay Kumar |
|
|
DMaaP | @Mandar Sawant |
|
|
External API | @Adrian OSullivan |
|
|
HOLMES | @Guangrong Fu |
|
|
MODELING | @Hui Deng |
|
|
Multi-VIM / Cloud | @Bin Yang |
|
|
OOF | @krishna moorthy |
|
|
OOM | @Sylvain Desbureaux |
|
|
POLICY | @James Hahn |
|
|
PORTAL | @Sunder Tattavarada |
|
|
SDN-C | @Dan Timoney |
|
|
SDC | @ChrisC |
|
|
SO | @Seshu Kumar Mudiganti |
|
|
VID | @Ikram Ikramullah |
|
|
VF-C | @Yuanhong Deng |
|
|
VNFRQTS | @Steven wright |
|
|
VNF-SDK | @victor gao |
|
|
CDS | @Yuriy Malakov |
|
|