You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

This is a continuation of the use case started in Casablanca: 5G - PNF Software Update

Background (R3 Casablanca)

In Casablanca,  the UC leveraged the Ansible adaptor of ONAP controller to implement three S/W upgrade related operations for 5G PNFs. As an important feature the new workflow supports an External Controller (EC) in the execution of these operations. All these operations  have shared the same LCM APIs with VNF S/W upgrade with PNF specific parameters passed in the API payloads. The corresponding DGs of LCM APIs are updated. The operations are:

  • /operations/LCM:upgrade-pre-check
  • /operations/LCM:upgrade-software
  • /operations/LCM:upgrade-post-check

Dublin Scope

For Dublin, the target of this UC includes:

  • 3GPP Software Management API alignment
    • South-bound of SDNC: Extend upgrade-software operation by leveraging sub-operations from 3GPP (like download/install/activate).
    • North-bound of SDNC: Rollback/fallback API support for 5G PNF
  • Workflow support for PNF in-place SW upgrade in SO (stretch goal)


Presentations and Discussion Slides:

Related Meeting Links:

Development Status

Proposed Dublin scope presented Dec 20, 2018 to the 5G UC meeting.

ProjectPTL/ContanctsJIRADescriptionStatus

APPC

SDNC

CCSDK


  1. Support vendor-specific mapping of upgrade APIs to NETCONF requests in addition to other options.

  2. Support of roll-back API for PNF, New DG needed. Impact to SO building blocks and SDNC.
  3. LCM API payload  and playbook enhancements for S/W upgrade for alignment with 3GPP S/W management APIs in ansible playbooks
  4. PNF S/W upgrade workflow design and test (Stretch goal)

VF-C
No Impact

SO

VID


  1. Provide re-usable workflows and building blocks for PNF SW upgrade
  2. Trigger upgrade workflow from GUI

IntegrationYang Xu
No impact
External Controller
Support for 3GPP API calls for sw download, install and activate.

Project Impacts

Description

Links

SDNC/CCSDK

Modify SDNC LCM action - rollback

https://jira.onap.org/browse/SDNC-664

complete rollback LCM action for PNF   S/W upgrade

https://jira.onap.org/browse/SDNC-669

create a DG for PNF S/W upgrade

https://jira.onap.org/browse/SDNC-670

provide corresponding ansible playbook   for rollback operation

https://jira.onap.org/browse/SDNC-671

Extend PNF upgrade-software   operation by leveraging sub-operations from 3GPP (like   download/install/activate)

https://jira.onap.org/browse/SDNC-677

External   Controller

Support swFallback/download/install/activate operations

NA

Requirements Impact

CCSDK → Changes in LCM.yang file

SDN-C → (1) New ansible playbooks, (2) New DG for rollback

EC → New substeps such as sw download, install and activate

API changes

  • Yang model changes to current LCM:rollback action in CCSDK (mandatory fields in rollback action will be optional to make the LCM:rollback action more generic, optional output payload field is added)
  • Definition of rollback input and output payloads for 5G PNF specific rollback
  • Possible payload changes into existing API /operations/LCM:upgrade-software
  • sw download, install and activate APIs in southbound of SDNC (to EC) as part of Ansible playbook for LCM:upgrade-software API.

Test cases and Status

Master Integration Test Page: Dublin Release Integration Testing Status


#Test Case DescriptionTest Status

1 PreCheck test

Ensure LCM:upgrade-pre-check can be executed (north-bound of SDNC)

NOT TESTED

2 SwUpgrade test

Ensure LCM:upgrade-software can be executed (north-bound of SDNC)

NOT TESTED

3 PostCheck test

Ensure LCM:upgrade-post-check can be executed (north-bound of SDNC)

NOT TESTED

4 SwRollback testEnsure LCM:rollback can be executed (north-bound of SDNC)

NOT TESTED

5 SwDownload

Ensure software download API can be executed (south-bound of SDNC to EC)

NOT TESTED

6 SwInstall

Ensure software install API can be executed (south-bound of SDNC to EC)

NOT TESTED

7 SwActivate

Ensure software activate API can be executed (south-bound of SDNC to EC)

NOT TESTED



  • No labels