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

Compare with Current View Page History

« Previous Version 120 Next »

Table of Contents

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:

  1. Using direct Netconf/Yang interface with PNF
  2. Enable service level LCM operations
  3. Using Ansible protocol with EM
  4. Using Netconf/Yang interface with EM

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

PROJECTPTLUser Story / EpicRequirement
A&AI

James Forsyth



AAF
Jonathan Gathman


APPC

Takamune Cho



CLAMP

Gervais-Martial Ngueko



CC-SDK

Dan Timoney

Epic #1: PNF Software Upgrade
  1. Support LCM API / self service API for downloadNESw and activateNESw actions
  2. Provide CDS blueprint for downloadNESw and activateNESw (Test only)
DCAE

Vijay Venkatesh 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
  1. Support LCM API for downloadNESw and activateNESw actions
  2. Provide ansible playbooks for downloadNESw and activateNESw (Test only)
SDC

Ofir Sonsino

Epic #1: PNF Software Upgrade
  1. support generic workflow design
  2. CBA association enhancement to support PNF upgrade. Impacts on PNFD AID model
  3. CBA association enhancement to support VNF upgrade. Impacts on VNFD AID model
SO

Seshu Kumar Mudiganti

Epic #1: PNF Software Upgrade
  1. Support generic PNF CM workflow, including SO building block shall be extended to support PNF LCM actions
  2. SO API extension: PNF software upgrade with target software version
  3. SO BB for downloadNESw, activateNESw, preCheck, postCheck
  4. API (LCM or CDS SS) selection within the same BB
VID
Ittay Stern
Epic #1: PNF Software Upgrade
  1. trigger PNF Sw upgrade workflow, providing corresponding parameter values
VNFRQTS
Steven Wright
Epic #1: PNF Software Upgradeupdate the PNF/VNF upgrade requirements 
VNF-SDK
Weitao Gao


CDS

Yuriy Malakov

Epic #1: PNF Software Upgrade
  1. Provide CDS blueprint for downloadNESw and activateNESw
  2. API (LCM or CDS SS) selection within the same BB
IntegrationBrian Freeman

List of PTLs: Approved Projects

Requirements Tickets

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Development Tickets

    Key Summary T Created Updated Assignee Reporter P Status Resolution Sub-Tasks Fix Version/s
    Refresh

    Key Summary T Created Updated Assignee Reporter P Status Resolution Sub-Tasks Fix Version/s
    Refresh

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Refresh

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Refresh

    Test Status

    1There should be a test case for each item in the sequence diagram

    NOT YET TESTED

    2create additional requirements as needed for each discreet step

    COMPLETE

    3Test cases should cover entire Use Case

    PARTIALLY COMPLETE

    4 Test Cases should include enough detail for testing team to implement the test

     FAILED

      PNF Software Upgrade Using direct NETCONF/YANG interface with PNF Test Cases

      Test Case Id Test Case Test Type Status
      TEST-CASE-1 Test resource package and service is successfully distributed from SDC to SO Integration

      NOT YET TESTED
      TEST-CASE-2 Test Service instantiation is triggered from VID to SO and accepted by SO  Integration NOT YET TESTED
      TEST-CASE-3 Test PNF softoware upgrade Workflow is triggered and precheck building block sends correct request to CDS Integration NOT YET TESTED
      TEST-CASE-4 Test PNF softoware upgrade Workflow is triggered and downloadSwNE building block sends correct request to CDS Integration  NOT YET TESTED
      TEST-CASE-5 Test Correct software is downloaded on Simulator and it send expected response to cds Integration NOT YET TESTED
      TEST-CASE-6 Test PNF softoware upgrade Workflow is triggered and ActivateSwNE building block sends correct request to CDS Integration NOT YET TESTED
      TEST-CASE-7 Test Correct software is activated on Simulator and it send expected response to cds and its being updated in A&AI Integration NOT YET TESTED
      TEST-CASE-8 Test PNF softoware upgrade Workflow is triggered and postcheck building block sends correct request to CDS Integration NOT YET TESTED

      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
      # Step Expected Result
      1

      Run SDC sdc-api-tests

      		 sdc-api-tests running
      2

      Wait for the tests to finish

      		 Tests finished without timeout
      3 Check the test reports All test cases run successfully
      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/


      Test Case ID
      • TEST-CASE-2
      Test Case Name Test Onboarding of PNF Package with non-mano Software Information in SDC GUI
      Description Manually onboard the PNF Package with non-mano Software Information in the SDC GUI, creating a VSP and importing as a ONAP PNF Resource.
      Release Frankfurt
      Preconditions
      • Local SDC or ONAP deployment available and running;
      • A SDC Vendor License Model already created;
      • A valid PNF Package with non-mano Software Information.
      Testing Steps
      # Step Expected Result
      1

      Access SDC GUI as a Designer.

      SDC Home screen is shown.
      2

      Go to the Onboard Workspace .

      		 Onboard workspace is shown.
      3 Click on "CREATE NEW VSP". "New Software Product" popup is shown.
      4 Fill in the "New Software Product" required information, selecting "Network Package" as the Onboarding Procedure and click on create. The VSP Overview page is shown.
      5 In the VSP Overview screen, Software Product Attachments, click on select file and provide the PNF Package with non-mano Software Information. The VSP attachment validation screen is shown.
      6 In the VSP attachment validation, click on the Submit button. A "Commit & Submit" popup is shown.
      7 Fill the "Commit & Submit" popup with any comment and click in the "Commit & Submit" button. A "Submit Succeeded" information is shown.
      8 Close the "Submit Succeeded" popup and go to the Home workspace. SDC Home screen is shown.
      9 Hover your mouse to the IMPORT square and click in "Import VSP". A "Import VSP" modal is shown with the SDC VSP list.
      10 Search for the created VSP. The created VSP is shown in the VSP list.
      11 Click on the VSP and then in the Download VSP link. The VSP CSAR package is downloaded.
      12 Open the CSAR package and check that the software information artifact is present in the folder Artifacts/Informational/PNF_SW_INFORMATION. The onboarded artifact is present on the folder.
      13 Go back to the "Import VSP" modal and click on the "Import VSP" link. The Resource Design General page is open with the PNF package information.
      14 Click on the "Create" button to create the resource. A creation confirmation message is shown.
      15 On the left panel, click on the "Properties Assignment". The "Properties Assignment" page is shown.
      16 Verify that the "software_versions" property is present and filled with the versions provided in the software information artifact. The "software_versions" property is present with the expected content.
      Status (Pass/Fail)

      Local SDC deployment: COMPLETE

      Used package: onboarding-package.csar

      Test case recording: Onboard_PNF_Software_Version.mkv
      Testing Lab Local SDC deployment


      Test Case ID
      • TEST-CASE-3
      Test Case Name Test Onboarding of PNF Package with non-mano Software Information in SDC Sanity-UI test
      Description The test will onboard the PNF Package with non-mano Software Information in the UI SDC Sanity test flow
      Release Frankfurt
      Preconditions

      Local SDC or ONAP deployment available and running
      Testing Steps


      # Step Expected Result
      1

      Run SDC sdc-ui-tests

      		 sdc-ui-tests running
      2

      Wait for the tests to finish

      		 Tests finished without timeout
      3 Check the test reports All test cases run successfully
      Status (Pass/Fail)

      Local SDC deployment: COMPLETE  SDC-2702 - Getting issue details... STATUS

      SDC Daily UI Sanity: COMPLETE https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/sdc-master-csit-uiSanity-testng/1102/SDC_UI_Extent_Report.html.gz
      Testing Lab Local SDC deployment, SDC Daily UI Sanity run https://jenkins.onap.org/view/sdc/job/sdc-master-csit-uiSanity-testng/

      TBD

      TBD

      Reference

      ONAP Controller Evolution Consideration - LCM APIs 

      Discussion Materials

      This section is to review slides for discussion.


      PNF Software Upgrade Proposal for Scenario 1 Controller to PNF Interface

      Version 2 with updates from Aug 8 2019 meeting

      PNF SW Upgrade Proposal v2.pptx


      Analysis of SO Instance Management API

      ONAP-PNF-Software-Upgrade-SO-v0.1.docx

      ONAP-PNF-Software-Upgrade-SO-v0.2.docx

      SO API requirements in R6

      Meeting Schedule for Impacted Project Discussion

      The meeting schedule is to present this use case slides to the impacted projects.

      Planned DateRelated Project/UC Meeting HostOther
      July 15SDC

      Ofir Sonsino


      July 11CDS

      Yuriy Malakov


      July 10Use case Realization

      Benjamin Cheung


      July 10Change Management

      Ajay Mahimkar


      Oct 9SO

      Seshu Kumar Mudiganti


      • No labels