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

« Previous Version 37 Next »

--- Frankfurt Release Test Scope ---

5G Bulk PM "Control Plane"

Bulk PM "Control plane” in ONAP  will manage PM

  • Support enabling configuration of PM jobs/subscriptions on xNFs

  • PM consumers can conveniently define PM subscriptions on (sub)network-level, thereby configuring PM on a set (small or large) of xNF instances in a single subscription. Different consumers to manage their own subscriptions, independently of each other.

Configuration aspects of the PMSH mS:

  • The PMSH mS is mainly configured via the configuration policy in CLAMP. The actual PM subscription is configured this way.
  • Post-deployment reconfiguration of the subscription/mS is also being considered, via different means (e.g. CLAMP or some new types of events on DMaaP). This can be reconfiguration of xNF filter or reconfiguration of the actual PM subscription (e.g. list of measurements).
  • PMSH probably also needs some additional basic configuration, e.g. which MR to connect to, which MR topics to listen and publish to.


Deployment:

Test environment requirements for the test cases:

  • xNF simulator for test cases:  SFTP / FTPes capable server.
  • xNF is registered with ONAP:
    • E.g. xNF able to produce data files and send VES fileReady events,
    • E.g. xNF emulator able to produce 'fileReady' notification events including updated events, or a series or predefined VES events at periodic intervals.
    • Sample data files for collection. E.g. 3gpp PM file(s)
  • DMaaP Message Router.
  • DCAE PMSH.
  • CLAMP
  • SDNC
  • A&AI
  • POLICY

JIRA / Confluence Link:

High Level End-to-End integration Testcases


#TestcasesStatus
Bulkpm_CL_01Ensure an ONAP user can create an inactive PM Subscription for specified PNF through CLAMP GUI.

PLAN

Bulkpm_CL_02Ensure an ONAP can user create an active PM Subscription for specified PNF through CLAMP GUI.

PLAN

Bulkpm_CL_03Ensure an ONAP can user create an active PM Subscription for specified VNF through CLAMP GUI.

PLAN

Bulkpm_CL_04

Ensure a Network Function's PM Configuration is available on the Network Function Instance After an ONAP user activates an Inactive subscription.

PLAN

Bulkpm_CL_05

Ensure a Network Function's PM Configuration is available on the Network Function Instance After an ONAP user creates an active subscription.

PLAN

Bulkpm_CL_06

Ensure a subscription config is removed from a network function after an ONAP user deactivates a PM subscription.

PLAN

Bulkpm_CL_07Ensure an existing network function's PM configuration is applied for newly added PNF instances in ONAP if it matches NF filter criteria.

PLAN

Bulkpm_CL_08Ensure an un-deploy PM Subscription control loop removes corresponding network functions subscription from the node.

PLAN

Bulkpm_CL_09Ensure that removal of PNF from ONAP (A&AI), trigger the automatic removal of xNF from all the subscriptions it is currently included in.

PLAN

*Ensure that removal of VNF from ONAP (A&AI), trigger the automatic removal of xNF from all the subscriptions it is currently included in.

STRETCH GOAL

*Ensure an ONAP can user create an inactive PM Subscription for specified VNF  through CLAMP GUI.

STRETCH GOAL

*Ensure an existing network function's PM configuration is applied for newly added VNF instances in ONAP if it matches NF filter criteria.

STRETCH GOAL

*Ensure that ONAP user is able to modify PM Subscription configuration (e.g. add/remove PM counters, change granularity period, file location, etc) only when it is in inactive state)

STRETCH GOAL

*Ensure that ONAP user is able to modify NF Filter in PM Subscription.

STRETCH GOAL

Bulk PM "Control Plane" E2E Sunny Day Scenario Sequence Diagram


Detailed Description End-to-End Feature Integration Testcases :


Test Case ID

Bulkpm_CL_01

Test Case NameEnsure an ONAP user can create an inactive PM Subscription for specified PNF through CLAMP GUI.
DescriptionThis test verify that once inactive pm subscription is deployed through CLAMP GUI, it is present in PMSH config in consul.
ReleaseFrankfurt
Pre-conditionsONAP with SDNC,SDC,DMAAP,CLAM should be installed. PMSH Control Loop service exist in SDC.
Testing Steps
StepsExpected Result
  1. Create PM Subscription with administrativeState": "LOCKED"  in CLAMP and Deploy Control Loop.

Sample inactive configuration:

          {
            "subscriptionName": "B1000",
            "administrativeState": "LOCKED",
            "fileBasedGP": 15,
            "fileLocation": "c://PM",
            "measurementGroups": [
              {
                "measurementGroup": {
                  "measurementTypes": [
                    {
                      "measurementType": "attTCHSeizures"
                    },
                    {
                      "measurementType": "succTCHSeizures"
                    }
                  ],
                  "managedObjectDNsBasic": [
                    {
                      "DN": "RncFunction=RF-1,UtranCell=Gbg-998"
                    },
                    {
                      "DN": "RncFunction=RF-1,UtranCell=Gbg-500"
                    },
                    {
                      "DN": "RncFunction=RF-1,UtranCell=Gbg-100"
                    }
                  ]
                }
              }
            ]
          }
  1. Bulk-pm Control Loop will be deployed. Following artifact will be created as a part of CL
  •  PMSH service.
  • Monitory Policy distribution. 



2. Confirm PM subscription is present in consul configuration of PMSH service.Subscription info is present in consul config of PMSH.
Conclusion (Pass /Fail)
Automation ( Yes - link / No)
Testing Lab

///

Test Case ID

Bulkpm_CL_02

Test Case NameEnsure an ONAP can user create an active PM Subscription for specified PNF through CLAMP GUI.
Description
Release
Pre-conditions
Testing Steps
StepsExpected Result




Conclusion (Pass /Fail)
Automation ( Yes - link / No)
Testing Lab

///

Test Case ID

Bulkpm_CL_03

Test Case NameEnsure an ONAP can user create an active PM Subscription for specified VNF through CLAMP GUI.
Description
Release
Pre-conditions
Testing Steps
StepsExpected Result




Conclusion (Pass /Fail)
Automation ( Yes - link / No)
Testing Lab

///

Test Case ID

Bulkpm_CL_04

Test Case NameEnsure a Network Function's PM Configuration is available on the Network Function Instance After an ONAP user activates an Inactive subscription.
Description
Release
Pre-conditions
Testing Steps
StepsExpected Result




Conclusion (Pass /Fail)
Automation ( Yes - link / No)
Testing Lab

///

Test Case ID

Bulkpm_CL_05

Test Case NameEnsure a Network Function's PM Configuration is available on the Network Function Instance After an ONAP user creates an active subscription.
Description
Release
Pre-conditions
Testing Steps
StepsExpected Result




Conclusion (Pass /Fail)
Automation ( Yes - link / No)
Testing Lab

///

Test Case ID

Bulkpm_CL_06

Test Case NameEnsure a subscription config is removed from a network function after an ONAP user deactivates a PM subscription.
Description
Release
Pre-conditions
Testing Steps
StepsExpected Result




Conclusion (Pass /Fail)
Automation ( Yes - link / No)
Testing Lab

///


Test Case ID

Bulkpm_CL_07

Test Case NameEnsure an existing network function's PM configuration is applied for newly added PNF instances in ONAP if it matches NF filter criteria.
Description
Release
Pre-conditions
Testing Steps
StepsExpected Result




Conclusion (Pass /Fail)
Automation ( Yes - link / No)
Testing Lab

///

Test Case ID

Bulkpm_CL_08

Test Case NameEnsure an un-deploy PM Subscription control loop removes corresponding network functions subscription from the node.
Description
Release
Pre-conditions
Testing Steps
StepsExpected Result




Conclusion (Pass /Fail)
Automation ( Yes - link / No)
Testing Lab

///

Test Case ID

Bulkpm_CL_09

Test Case NameEnsure that removal of PNF from ONAP (A&AI), trigger the automatic removal of xNF from all the subscriptions it is currently included in.
Description
Release
Pre-conditions
Testing Steps
StepsExpected Result




Conclusion (Pass /Fail)
Automation ( Yes - link / No)
Testing Lab

///

  • No labels