Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

Version 1 Current »


                       

                           


Overview:

The PNF software upgrade use case consists of three main parts:

  • SDC for distributing the resource model and custom workflow design
  • SO will implement building blocks in workflow for preCheck, downloadNeSw, activateNesW, updateAAI & postCheck.
  • CDS Blueprint Processor will implement the mount, configure and un-mount requests to SDNC/ODL. The processor currently has the ability to read a blueprint from archive and process it.

JIRAs:

TODO - Need to create a filter to link all JIRAs


Deployment:

Test environment requirements for the test cases:

  • xNF simulator for test cases:  PNF Simulator with TLS & YANG support.
  • Rest Client simulator.
  • SO with BB implemented in workflows.
  • CDS Blueprint processor enhanced so that it can send mount, send configuration and un-mount rest request to SDNC.

This environment can be set up by following the steps below.

  1. Repo : Yet to update
  2. RUN : Yet to update

Use Case preconditions:

    • xNF simulator.
    • Rest Client sim.


Upgrade One PNF Instance

High Level feature integration Testcases 


#WorkflowTest CaseStatus
1Preparation WorkflowPreCheck and DownloadNESw - Sw image not available on PNF

NOT YET TESTED

2Preparation WorkflowPreCheck and DownloadNESw - Sw image already available on PNF

NOT YET TESTED

3Preparation WorkflowPreCheck and DownloadNESw - Sw image download failed

NOT YET TESTED

4Software Upgrade Workflow

PreCheck, DownloadNESw, ActivateNeSw(and update AAI) & postCheck with Sw image not available on PNF - Activation OK

NOT YET TESTED

5Software Upgrade Workflow

PreCheck, DownloadNESw, ActivateNeSw (and update AAI) & postCheck with Sw image already available on PNF - Activation OK

NOT YET TESTED

6Software Upgrade Workflow

PreCheck, DownloadNESw, ActivateNeSw with update AAI & postCheck - Activation NOK, Rollback triggered

NOT YET TESTED

Detailed Description Feature Integration Testcases :

Preparation Workflow Test Cases: 

Test Case ID

PNF_SW_UP_E2E_01

Test Case Name

PreCheck and DownloadNESw - Sw image not available on PNF

Test Description

Ensure that Precheck & DownloadNESw BB are run successfully.

Validate API decision of using CDS self-service API is following the design time configuration

ReleaseFrankfurt
Pre-conditions
  • PNF resource model is distributed to VID & SO
  • CBA is distributed to the BlueprintProcessor microservice
  • PNF is registration is completed & PNF entry is present in AAI.
  • The upgrade parameters, PNF-name/PNF-software-version being sent into the workflow are accurate.
Testing Steps
Detailed Test StepsExpected Result
  1. Operator selects the workflow to run along with target software version & PNF instance ID
  2. PreCheck workflow is successfully run by SO
  3. DownloadNESw workflow is successfully triggered post PreCheck
  4. Corresponding CBAs are executed correctly
  • The BB workflows are triggered and executed successfully
  • API decisions of using CDS self-service API are following the design time configuration
  • The upgrade parameters, PNF-name/PNF-software-version, are passed into the blueprint processor.
  • The correct software image is downloaded onto the PNF
Conclusion (Pass /Fail)
Testing Lab



Test Case IDPNF_SW_UP_E2E_02
Test Case Name

PreCheck and DownloadNESw - Sw image already available on PNF

Test Description

Ensure that Precheck & DownloadNESw BB are run successfully.

Validate API decision of using CDS self-service API is following the design time configuration

ReleaseFrankfurt
Pre-conditions
  • PNF resource model is distributed to VID & SO
  • CBA is distributed to the BlueprintProcessor microservice
  • PNF is registration is completed & PNF entry is present in AAI.
  • The upgrade parameters, PNF-name/PNF-software-version being sent into the workflow are accurate.
  • New Software image is already available on a pre-configured location on the PNF

Testing Steps



Detailed Test StepsExpected Result
  1. Operator selects the workflow to run along with target software version & PNF instance ID
  2. PreCheck workflow is successfully run by SO
  3. DownloadNESw workflow is successfully triggered post PreCheck
  4. Corresponding CBAs are executed correctly
  • The BB workflows are triggered and executed successfully
  • API decisions of using CDS self-service API are following the design time configuration
  • The upgrade parameters, PNF-name/PNF-software-version, are passed into the blueprint processor.
  • Blueprint processor checks for available software images and ejects once if finds the image already available
  • No new software image is downloaded onto the PNF
Conclusion (Pass /Fail)
Testing Lab



Test Case ID

PNF_SW_UP_E2E_03

Test Case Name

PreCheck and DownloadNESw - Sw image download failed

Test Description

Ensure that Precheck BB runs successfully & DownloadNESw BB fails due to download failure.

Validate API decision of using CDS self-service API is following the design time configuration

ReleaseFrankfurt
Pre-conditions
  • PNF resource model is distributed to VID & SO
  • CBA is distributed to the BlueprintProcessor microservice
  • PNF is registration is completed & PNF entry is present in AAI.
  • The upgrade parameters, PNF-name/PNF-software-version being sent into the workflow are accurate.
Testing Steps
Detailed Test StepsExpected Result
  1. Operator selects the workflow to run along with target software version & PNF instance ID
  2. PreCheck workflow is successfully run by SO
  3. DownloadNESw workflow is successfully triggered post PreCheck
  4. Corresponding CBAs are executed correctly
  • The BB workflows are triggered and executed successfully
  • API decisions of using CDS self-service API are following the design time configuration
  • The upgrade parameters, PNF-name/PNF-software-version, are passed into the blueprint processor.
  • Software image download is denied/image not found
Conclusion (Pass /Fail)
Testing Lab


Software Upgrade Workflow Test Cases:

Test Case IDPNF_SW_UP_E2E_04
Test Case Name

PreCheck, DownloadNESw, ActivateNeSw(and update AAI) & postCheck with Sw image not available on PNF - Activation OK

Test Description

Ensure that Precheck, DownloadNESw, ActivateNeSw with update AAI & postCheck BB are run successfully.

Validate API decision of using CDS self-service API is following the design time configuration

ReleaseFrankfurt
Pre-conditions
  • PNF resource model is distributed to VID & SO
  • CBA is distributed to the BlueprintProcessor microservice
  • PNF is registration is completed & PNF entry is present in AAI.
  • The upgrade parameters, PNF-name/PNF-software-version being sent into the workflow are accurate.

Testing Steps



StepsExpected Result
  1. Operator selects the workflow to run along with target software version & PNF instance ID
  2. PreCheck workflow is successfully run by SO
  3. DownloadNESw workflow is successfully triggered post PreCheck
  4. ActivateNESw BB is triggered.
  5. PostCheck activities are completed
  • The BB workflows are triggered and executed successfully
  • API decisions of using CDS self-service API are following the design time configuration
  • The upgrade parameters, PNF-name/PNF-software-version, are passed into the blueprint processor.
  • The correct software image is downloaded onto the PNF
  • Corresponding CBAs are executed correctly.
  • The targeted software version is activated on the PNF
  • AAI is updated with the new software version
  • PostCheck operations are completed successfully
Conclusion (Pass /Fail)
Testing Lab


Test Case IDPNF_SW_UP_E2E_05
Test Case Name

PreCheck, DownloadNESw, ActivateNeSw (and update AAI) & postCheck with Sw image already available on PNF - Activation OK

Test Description

Ensure that Precheck, DownloadNESw, ActivateNeSw with update AAI & postCheck BB are run successfully.

Validate API decision of using CDS self-service API is following the design time configuration

ReleaseFrankfurt
Pre-conditions
  • PNF resource model is distributed to VID & SO
  • CBA is distributed to the BlueprintProcessor microservice
  • PNF is registration is completed & PNF entry is present in AAI.
  • The upgrade parameters, PNF-name/PNF-software-version being sent into the workflow are accurate.
  • Targeted Software image is already available on a pre-configured location on the PNF

Testing Steps



Detailed Test StepsExpected Result
  1. Operator selects the workflow to run along with target software version & PNF instance ID
  2. PreCheck workflow is successfully run by SO
  3. DownloadNESw workflow is successfully triggered post PreCheck
  4. ActivateNESw BB is triggered.
  5. PostCheck activities are completed
  • The BB workflows are triggered and executed successfully
  • API decisions of using CDS self-service API are following the design time configuration
  • The upgrade parameters, PNF-name/PNF-software-version, are passed into the blueprint processor.
  • Blueprint processor checks for available software images and ejects once if finds the image already available
  • New software image download is skipped
  • Corresponding CBAs are executed correctly.
  • The targeted software version is activated on the PNF
  • AAI is updated with the new software version
  • PostCheck operations are completed successfully
Conclusion (Pass /Fail)
Testing Lab

Test Case IDPNF_SW_UP_E2E_06
Test Case Name

PreCheck, DownloadNESw, ActivateNeSw with update AAI & postCheck - Activation NOK, Rollback triggered

Test Description

Ensure that Precheck & DownloadNESw BBs run successfully but ActivateNeSw BB fails.

Validate API decision of using CDS self-service API is following the design time configuration

Software Upgrade Activation failed, Rollback is triggered

ReleaseFrankfurt
Pre-conditions
  • PNF resource model is distributed to VID & SO
  • CBA is distributed to the BlueprintProcessor microservice
  • PNF is registration is completed & PNF entry is present in AAI.
  • The upgrade parameters, PNF-name/PNF-software-version being sent into the workflow are accurate.

Testing Steps



Detailed Test StepsExpected Result
  1. Operator selects the workflow to run along with target software version & PNF instance ID
  2. PreCheck workflow is successfully run by SO
  3. DownloadNESw workflow is successfully triggered post PreCheck
  4. ActivateNESw BB is triggered.
  5. PostCheck activities are completed
  • The BB workflows are triggered and executed successfully
  • API decisions of using CDS self-service API are following the design time configuration
  • The upgrade parameters, PNF-name/PNF-software-version, are passed into the blueprint processor.
  • The correct software image is downloaded onto the PNF
  • ActivateNESw results in failure.
  • Rollback activity is triggered.
  • Corresponding CBAs are executed correctly.
  • AAI is updated with the failure
  • PostCheck operations are completed successfully
  • PNF is running on the old software version
Conclusion (Pass /Fail)
Testing Lab


Information:


Next Step(s):

  • No labels