PNF software upgrade in R6 Frankfurt
Table of Contents
- 1 Table of Contents
- 2 BUSINESS DRIVERS
- 3 Current Status of PNF Software Upgrade
- 4 PNF Software Upgrade Scenarios
- 5 Common Tasks for all scenarios
- 6 Development Status
- 7 Test Status
- 7.1 Scenario 1: PNF Software Upgrade Using direct NETCONF/YANG interface with PNF Test Cases
- 7.2 Scenario 2: PNF Software Information On boarding Test Cases
- 7.3 Scenario 3: PNF Software Upgrade Using Ansible with EM Test Cases
- 7.4 Scenario 4: PNF Software Upgrade Using Netconf/Yang Interface with EM Test Cases
- 8 Reference
BUSINESS DRIVERS
This section describes Business Drivers for this Use Case.
Executive Summary - PNF software updates are routine for network upgrades to support new features, improve efficiency or increase capacity on the field, and to eliminate bugs. This use case positions ONAP as a vantage point in orchestrating and managing PNF software upgrades inline with the business and service objectives.
Business Impact - Deployment and orchestration of new network services over both VNFs and PNFs in a model and software driven way simplifies the network management. As 5G networks will host a large number of PNFs from multiple vendors, streamlining service upgrades that involve PNF software changes through ONAP will reduce the OPEX substantially.
Business Markets - Carriers both in the mobile and fixed-line space host PNFs at the edge of the network. New 5G deployments as well as legacy 4G systems in the mobile carrier space should be considered as target markets.
Funding/Financial Impacts - Orchestrating PNF software updates via an ONAP deployment will enable better service planning, faster introduction of new network services over field-deployed PNFs, and reduce the operational costs.
Organization Mgmt, Sales Strategies - Harmonizing PNF and VNF software management in a model and workflow driven manner is essential in 5G systems where PNFs will continue to exist in large numbers and they are expected to have more frequent software upgrades (as they will have more capabilities that can be controlled or upgraded via software). Thus ONAP can be the "go-to" solution if this harmonization can be done successfully.
Current Status of PNF Software Upgrade
PNF in place software upgrade is supported in Casablanca and updated in Dublin
With the support of an EM
Ansible protocol only
Plan to use LCM API with existing SO building blocks
Impacts on SDNC only (not E2E solution yet)
More details, 5G - PNF Software Update & 5G - PNF SW Upgrade (Casablanca carry-over items)
PNF Software Upgrade Scenarios
There are 4 scenarios are proposed:
Common Tasks for all scenarios
SO workflow Example to upgrade one PNF instance
SO activities operations:
LCM evolution with API Decision Tree
Development Status
Impacts Summary
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | @James Forsyth | ||
AAF | @Jonathan Gathman | ||
APPC | @Takamune Cho | ||
CLAMP | @Gervais-Martial Ngueko | ||
CC-SDK | @Dan Timoney | Epic #1: PNF Software Upgrade |
|
DCAE | @Vijay Kumar | ||
DMaaP | @Mandar Sawant | ||
External API | @Matthieu Geerebaert | ||
MODELING | @Hui Deng | ||
Multi-VIM / Cloud | @Bin Yang | ||
OOF | @Shankaranarayanan Puzhavakath Narayanan | ||
POLICY | @Pamela Dragosh | ||
PORTAL | @Manoop Talasila | ||
SDN-C | @Dan Timoney | Epic #1: PNF Software Upgrade |
|
SDC | @Ofir Sonsino | Epic #1: PNF Software Upgrade |
|
SO | @Seshu Kumar Mudiganti | Epic #1: PNF Software Upgrade |
|
VID | @ittay | Epic #1: PNF Software Upgrade |
|
VNFRQTS | @Steven wright | Epic #1: PNF Software Upgrade | update the PNF/VNF upgrade requirements |
VNF-SDK | @victor gao | ||
CDS | @Yuriy Malakov | Epic #1: PNF Software Upgrade |
|
Integration | @Brian Freeman |
List of PTLs: Approved Projects
Requirements Tickets
Scenario 1 Using direct Netconf/Yang interface with PNF
| key | summary | type | created | updated | assignee | reporter | priority | status | resolution | subtasks | fixversions |
|---|
Scenario 2 Enable service level LCM operations
| key | summary | type | created | updated | assignee | reporter | priority | status | resolution | subtasks | fixversions |
|---|
Scenario 3 Using Ansible protocol
Scenario 4 Netconf/Yang interface with EM
Test Status
1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
2 | create additional requirements as needed for each discreet step | COMPLETE |
3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
4 | Test Cases should include enough detail for testing team to implement the test | FAILED |
Scenario 1: PNF Software Upgrade Using direct NETCONF/YANG interface with PNF Test Cases
Test Case Id | Test Case | Test Type | Status |
|---|---|---|---|
TEST-CASE-1 | Test Check in SDNC certificates to connect node are properly installed | Integration(robot) | COMPLETE |
TEST-CASE-2 | Test Blue print archive is properly uploaded to blueprint-processor | Integration(robot) | COMPLETE |
TEST-CASE-3 | Test resource package and service is successfully distributed from SDC to SO | Integration(robot) | COMPLETE |
TEST-CASE-4 | Test all the pnf workflows are successfully fetched from SO | Integration(robot) | COMPLETE |
TEST-CASE-5 | Test Service instantiation is triggered from VID to SO and status is COMPLETED for preparation(Download) workflow | Integration(robot) | COMPLETE |
TEST-CASE-6 | Verify on PNF-simulator that there is pnf_sw_version-2.0.0 entry added into the list and its status is DOWNLOAD-COMPLETED | Integration(robot) | COMPLETE |
TEST-CASE-7 | Test Service instantiation is triggered from VID to SO and status is COMPLETED for software upgrade workflow | Integration(robot) | COMPLETE |
TEST-CASE-8 | Verify on PNF-simulator that there is pnf_sw_version-3.0.0 entry added into the list and its status is ACTIVATION-COMPLETED | Integration(robot) | COMPLETE |
TEST-CASE-9 | Verify on AAI-Simulator that for pnf PNFDemo sw-version is pnf_sw_version-3.0.0. | Integration(robot) | COMPLETE |
Test Cases Details:
All the test cases for Scenario 1 are robot tests that can be ran automatically from the same steps which will be shown below.
Testing Steps | |
Status (Pass/Fail) | ONAP Jira Ticket: · https://jira.onap.org/browse/INT-1308 ONAP PNF SW Upgrade Daily CSIT Tests: |
Testing Lab | CSIT PNF SW Upgrade https://jenkins.onap.org/job/usecases-master-verify-csit-pnf-sw-upgrade/ |
Test Case ID | Test Case Name | Description | Release |
TEST-CASE-1 | Test Check in SDNC certificates to connect node are properly installed | This test will check whether the keystore is setup and certificates installed for SDNC and ODL once SDNC is installed | Frankfurt |
TEST-CASE-2 | Test Blueprint archive is properly uploaded to blueprint-processor | Test Blueprint archive is properly uploaded to blueprint-processor | Frankfurt |
TEST-CASE-3 | Test resource package and service is successfully distributed from SDC to SO | Test resource package and service is successfully distributed from SDC to SO | Frankfurt |
TEST-CASE-4 | Test all the PNF workflows are successfully fetched from SO | Test all the PNF workflows are successfully fetched from SO | Frankfurt |
TEST-CASE-5 | Test Service instantiation is triggered from VID to SO and status is COMPLETED for preparation (Download) workflow | Test Service instantiation is triggered from VID to SO and status is COMPLETED for preparation (Download) workflow | Frankfurt |
TEST-CASE-6 | Verify on PNF-simulator that there is pnf_sw_version-2.0.0 entry added into the list and its status is DOWNLOAD-COMPLETED | Verify on PNF-simulator that there is pnf_sw_version-2.0.0 entry added into the list and its status is DOWNLOAD-COMPLETED | Frankfurt |
TEST-CASE-7 | Test Service instantiation is triggered from VID to SO and status is COMPLETED for software upgrade workflow | Test Service instantiation is triggered from VID to SO and status is COMPLETED for software upgrade workflow | Frankfurt |
TEST-CASE-8 | Verify on PNF-simulator that there is pnf_sw_version-3.0.0 entry added into the list and its status is ACTIVATION-COMPLETED | Verify on PNF-simulator that there is pnf_sw_version-3.0.0 entry added into the list and its status is ACTIVATION-COMPLETED | Frankfurt |
TEST-CASE-9 | Verify on AAI-Simulator that for pnf PNFDDemo sw-version is pnf_sw_version-3.0.0 | Verify on AAI-Simulator that for pnf PNFDDemo sw-version is pnf_sw_version-3.0.0 | Frankfurt |
Scenario 2: PNF Software Information On boarding Test Cases
Test Case Id | Test Case | Test Type | Status |
|---|---|---|---|
TEST-CASE-1 | Test Onboarding of PNF Package with non-mano Software Information in SDC Sanity-API test | Sanity | Local SDC deployment: COMPLETE SDC Daily API Sanity: COMPLETE |
TEST-CASE-2 | Test Onboarding of PNF Package with non-mano Software Information in SDC GUI | Manual | Local SDC deployment: COMPLETE |
TEST-CASE-3 | Test Onboarding of PNF Package with non-mano Software Information in SDC Sanity-UI test | Sanity | Local SDC deployment: COMPLETE SDC Daily UI Sanity: COMPLETE |
Test Types:
Sanity-API: automated sanity tests for backend SDC APIs (SDC Sanity);
Sanity-UI: automated sanity tests for SDC GUI;
Manual: manual test in SDC UI (either local SDC or ONAP deployment);
End to End (E2E): end to end test with other interested ONAP components.
Test Cases Details
Test Case ID | TEST-CASE-1 |
|---|---|
Test Case Name | Test Onboarding of PNF Package with non-mano Software Information in SDC Sanity-API test |
Description | The test will onboard PNF Packages with non-mano Software Information in the SDC Sanity API test flow |
Release | Frankfurt |
Preconditions | Local SDC or ONAP deployment available and running |
Testing Steps | |
Status (Pass/Fail) | Local SDC deployment: COMPLETE SDC Daily API Sanity: COMPLETE |
Testing Lab | Local SDC deployment, SDC Daily API Sanity run https://jenkins.onap.org/view/sdc/job/sdc-master-verify-csit-sanity-testng/ |