Loading...

XML

Word

Printable

Type: Epic
Resolution: Done
Priority: High
Fix Version/s: Frankfurt Release
Affects Version/s: None
Component/s: None
Labels:
- CCSDK
- SDC
- SDNC
- SO
- VID

Epic Name:
PNF Software Upgrade using direct Netconf/Yang interface

There are 4 scenarios proposed for PNF software upgrade use case. This EPIC ticket only covers the implementation for scenario 1.

PNF software upgrade is one aspect of Software Management. The purpose of this procedure is to upgrade the software currently running on the PNF to a target software version without impacts on PNF schema and service template. The details of the solution including:

Enhancement and additions of PNF in-place software update.
Support direct PNF NETCONF interface with the vendor-specific YANG model.
Enhance SO in-place software upgrade workflow with generic SO building blocks, which can be used for workflow design in the design time.
Using CDS self-service API between SO and controller with the support of PNF in-place software upgrade
Enhance VID to demonstrate single PNF in-place software upgrade
Enhance SO procedure to support AAI update after the software upgrade completion.

blocks

REQ-84 PNF Software Upgrade using direct Netconf/Yang interface with PNF

Done

relates to

REQ-53 Enhancement on PNF S/W Upgrade with EM with Ansible

Done

mentioned in: Page Loading...; Page Loading...

Wiki Page: Wiki Page Loading...; Wiki Page Loading...

(1 Wiki Page)

Assignee:: zuqiang

Reporter:: zuqiang

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 26/Jun/19 4:49 PM

Updated:: 15/May/20 12:57 PM

Resolved:: 15/May/20 12:57 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates