Description
PNF Software upgrade includes:
- Define generic building blocks, which can be used for workflow design in the design time.
- Enhance precheck and postcheck steps in the upgrade process by vendor-specific rules. There are two approaches to provide these rules. One is artifacts in the PNF packages, and the other is preprovisioning in the EC. Anyhow, during the design time, operator could specify the used rules as need.
- Expected software version is modeled in PNF Modeling phase (same as 5G PNF PnP), and given corresponding value during the upgrade process.
- Apply in-place software upgrade in Casablanca.
- Basically, complete single PNF upgrade first, and the batch upgrade is considered as a stretch goal.
Presentations:
PNF Software upgrade flow to be tested
tbd
Test cases and status
Flow steps
| # | Test Case Description | Test Status |
|---|---|---|
1 EC registration test | Ensure ONAP controller can find out the EC | NOT TESTED |
2 PreCheck test | Ensure the EC can receive the precheck command from ONAP controller | NOT TESTED |
3 SwUpgrade test | Ensure the EC can receive the software upgrade command from ONAP controller | NOT TESTED |
4 PostCheck test | Ensure the EC can receive the postcheck command from ONAP controller | NOT TESTED |
5 New SW version report test | Ensure the software upgrade completion event can be reported to DCAE | NOT TESTED |
6 New SW version update test | Ensure the new software version can be updated in A&AI | NOT TESTED |
7 E2E Workflow execution test | Ensure the e2e software upgrade workflow can be executed at run time | NOT TESTED |