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)
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:
LCM API Abbre. | HTTP Method | URI | Yang Model Section | Request Example | Response Example | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
UpgradePreCheck* | POST | /operations/LCM:upgrade-pre-check |
|
|
|
|
|
|
|
|
| 400: Success
| ||||||||||||||||||||
UpgradePostCheck* | /operations/LCM:upgrade-post-check |
|
|
|
|
|
|
|
|
|
| 400: Success
| ||||||||||||||||||||
DownloadNESw | /operations/LCM:download-n-e-sw |
|
|
|
|
|
|
|
| 400: Success
| ||||||||||||||||||||
ActivateNESw | /operations/LCM:activate-n-e-sw |
|
|
|
|
|
|
|
|
| 400: Success
|
*: These LCM APIs are enhanced from R4/R5, and update the vnf-id field in action-identifiers to pnf-id in the request parameter.
The playbook-name in the payload of request is opitional. If not set the playbook-name in the request, it will use the value in the config file /opt/onap/sdnc/data/properties/lcm-dg.properties of SDNC.
- 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 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|