Table of Contents
Table of Contents
Scenario Scope In Frankfurt
This scenario will complete the E2E procedure of PNF in-place SW upgrade case started from Casablanca (evolved in Dublin). The E2E procedure is VID→ SO→ Controller(SDNC/CCSDK)→Ansible Server→ EMS → PNF.
- Trigger by VID to upgrade speficific PNF instance's software
- Enhance SO to support PNF S/W upgrade workflow execution
- Add SO BBs to do precheck/downloadNESw/activateNESw/UpdateAAI/postcheck using SDNC client
Support LCM API for downloadNESw and activateNESw actions
Provide ansible playbooks for downloadNESw and activateNESw
- Enhance EMS emulator for integration test
Since this scenario started from Casanblanca, it is helpful to find more details completed in past releases with following link.
- In Casablanca: 5G - PNF Software Update
- In Dublin: 5G - PNF SW Upgrade (Casablanca carry-over items)
Procedure
Pre-conditions
- ONAP is ready to use, while min components are VID/SO/SDNC/CCSDK.
- PNF PnP is completed, and EMS ipaddress is strored in AAI within PNF Registration step, as ipaddressV4Oam.
- EMS (Emulator) is running, and SFTP (can be with EMS) is ready.
Upgrade procedure
- (1) In PNF pre-onboarding, operator delivers the PNF packages, including necessary ansible artifacts, to SDC. [playbook distribution is out of scope in this release]
- (2) In Sw Upgrade runtime, operator initiates the command, via VID or timer, to SO. (Before that, operator should design the upgrade workflow, or use the existing one).
- (3) SO executes the Sw upgrade task, like A&AI retrieval, and sends LCM requests to the controller.
- (4) Ansible Adaptor forwards requests to EMS via ansible server.
Sequence Diagram
Impacts
| Project/Component | Story |
|---|---|
SO | Support generic PNF workflow design |
SO | Support upgrade sw version at PNF instance level |
| SO | Align with SO building block for PNF Upgrade procedure 1) Create new SO BB – downloadNESw 2) Create new SO BB – activateNESw 3) Create new SO BB – update AAI 4) Update SO BB – preCheck and postCheck |
| SO | Support different controller decision points in SO |
| SDNC/CCSDK | Support LCM API for downloadNESw and activateNESw actions |
| SDNC/CCSDK | Provide ansible playbooks for downloadNESw and activateNESw |
| VNFRQTS | PNF Software Upgrade with ansible with EM |
| Integration | 1) EMS simulator extension 2) Integration document revision for PNF Sw Upgrade UC |
API Impacts Details
- NBI of SO:
tbd
- LCM API of CCSDK:
tbd
- Itf-N of EM:
tbd
JIRA Status Tracking
Note that, this scenario has some common task with scenario 1.
Common Task with Scenario 1:
tbd
Scenario 3 Specific:
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|