--- 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:
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-129 - 5G Bulk PM in Frankfurt/R6
High Level End-to-End integration Testcases
| # | Testcases | Status | ||||
|---|---|---|---|---|---|---|
| * | Ensure an ONAP user can create an inactive PM Subscription for specified PNF through CLAMP GUI in SDC. |
| ||||
| * | Ensure an ONAP can user create an active PM Subscription for specified PNF through CLAMP GUI in SDC. |
| ||||
| * | Ensure an ONAP can user create an active PM Subscription for specified VNF through CLAMP GUI in SDC. |
| ||||
| * | Ensure a Network Function's PM Configuration is available on the Network Function Instance After an ONAP user activates an Inactive subscription. |
| ||||
| * | Ensure a Network Function's PM Configuration is available on the Network Function Instance After an ONAP user creates an active subscription. |
| ||||
| * | Ensure a subscription config is removed from a network function after an ONAP user deactivates a PM subscription. |
| ||||
| * | Ensure an existing network function's PM configuration is applied for newly added PNF instances in ONAP if it matches NF filter criteria. |
| ||||
| * | Ensure an un-deploy PM Subscription control loop removes corresponding network functions subscription from the node. |
| ||||
| * | Ensure that removal of PNF from ONAP (A&AI), trigger the automatic removal of xNF from all the subscriptions it is currently included in. |
| ||||
| * | Ensure that removal of VNF from ONAP (A&AI), trigger the automatic removal of xNF from all the subscriptions it is currently included in. |
| ||||
| * | Ensure an ONAP can user create an inactive PM Subscription for specified VNF through CLAMP GUI in SDC. |
| ||||
| * | Ensure an existing network function's PM configuration is applied for newly added VNF instances in ONAP if it matches NF filter criteria. |
| ||||
| * | 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) |
| ||||
| * | Ensure that ONAP user is able to modify NF Filter in PM Subscription. |
|
Bulk PM "Control Plane" E2E Sunny Day Scenario Sequence Diagram
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
Detailed Description End-to-End Feature Integration Testcases :
| Test Case ID | |||||
|---|---|---|---|---|---|
| Test Case Name | |||||
| Description | |||||
| Release | |||||
| Pre-conditions | |||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Automation ( link ) | |||||
| Testing Lab |
| Test Case ID | |||||
|---|---|---|---|---|---|
| Test Case Name | |||||
| Description | |||||
| Release | |||||
| Pre-conditions | |||||
| Testing Steps |
| ||||
| Conclusion (Pass /Fail) | |||||
| Automation ( link ) | |||||
| Testing Lab |