---TEST STATUS for Dublin Release ----
Use Case 1
:
Event-driven bulk transfer of monitoring data from an xNF to ONAP/DCAE. A micro-service will listen for 'FileReady' VES events sent from an xNF via the VES collector. Once files become available the collector micro-service will fetch them using protocol such as FTPES
or SFTP. The collected data files are published internally on a DMaaP Data Router (DR) feed.
A File Consumer node which is a simulated PM file subscriber that subscribe to Data Router feed and receive PM files.
Use Case 2:
Event-driven bulk transfer of monitoring data from an xNF to ONAP/DCAE. A micro-service will listen for 'FileReady' VES events sent from an xNF via the VES collector. Once files become available the collector micro-service will fetch them using protocol such as FTPES or SFTP. The collected data files are published internally on a DMaaP Data Router (DR) feed. The PM mapper receives the files by subscribing to a Data Router feed. The 3GPP PM Mapper micro-service
will extract selected (filtered) measurements from a 3GPP XML file and publish them as VES events on a DMaaP Message Router topic for consumers that prefer such data in perf3gpp VES format.
Use Case 1 High Level End-to-End integration Testcases :
# | Test Case | Status | ||||||
---|---|---|---|---|---|---|---|---|
1 | Ensure that the 'FileReady' VES event is sent from the simulated xNF via the VES collector. |
| ||||||
2 | Ensure that the unauthenticated.VES_NOTIFICATION_OUTPUT topic |
is present once it received "File Ready" VES notification from VES Collector. |
| |||||||
3 | Ensure that the Data File Collector starts to download the xml PM file(s) from the simulated xNF once it receives the 'FileReady' VES event via the VES collector. |
| ||||||
4 | Ensure that the PM xml file(s) are published to the Data Router. |
| ||||||
4a | Ensure that a simulated File Consumer is able to subscribe and consume the PM file(s) from the Data Router. |
| ||||||
5 | Verify the Data File Collector Metadata file is valid |
|
Use Case 2 High Level End-to-End integration Testcases :
# | Test Case | Status | ||||||
---|---|---|---|---|---|---|---|---|
1 | Ensure that the 'FileReady' VES event is sent from the simulated xNF via the VES collector. |
| ||||||
2 | Ensure that the unauthenticated.VES_NOTIFICATION_OUTPUT topic is present once it received "File Ready" VES notification from VES Collector. |
| ||||||
3 | Ensure that the Data File Collector starts to download the xml PM file(s) from the simulated xNF once it receives the 'FileReady' VES event via the VES collector. |
| ||||||
4 | Ensure that the PM xml file(s) are published to the Data Router. |
| ||||||
5 | Verify the Data File Collector Metadata file is valid |
| ||||||
6 | Verify 3GPP PM Mapper subscribes to feed on the Data Router and maps the PM xml file onto the Message Router as a VES Message(s) |
| ||||||
7 | Verify that "simulated PM VES Consumer" receive VES events from Message Router topic. |
|
E2E Sunny Day Scenario Sequence Diagram:
Gliffy Diagram | ||||||||
---|---|---|---|---|---|---|---|---|
|
JIRAs:
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Deployment:
Test environment requirements for above test cases:
- xNF simulator for test cases: FTPes capable server.
- with VES 7.0.1 support for 'fileReady' event.
- 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 R3, at minimum
- need DR running and configured for Bulk PM support
- DCAE R3, MR with support for VES 7.
- 1 spec
- DCAE R3, Data File Collector installed and configured
Use Case preconditions:
- xNF simulated script.
E2E Sequence Diagram
High Level End-to-End feature integration Testcases :
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||
---|---|---|
|
Status | ||||
---|---|---|---|---|
|
This environment can be set up by following the steps below.
- Clone the integration/csit repo (git clone ssh://gerrit.onap.org:29418/integration/csit ).
- Run: .run-csit.sh plans/usecases/5G-bulkpm
Use Case preconditions:
- xNF simulator.
Detailed Description End-to-End Feature Integration Testcases :
Test Case ID | Bulk_PM_E2E_01 | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Test Case Name | Send FileReadyEvent to Data File VES Collector | |||||||||||||||||||||
Description | Ensure that the 'FileReady' VES event is sent from the simulated xNF via to the VES collector and is received by Data File Collector. | |||||||||||||||||||||
Release | Casablanca | |||||||||||||||||||||
Pre-conditions | From the above section "Deployment" a test environment with all the required components , - xNF will be simulated by a script(simulated with sftp or sftpe ), VES Collector are all started. | |||||||||||||||||||||
Testing Steps |
| Testing Steps | Simulate a xNF (support sftpe protocol )
Expand | title | Sample File Exist
| Expected Result |
| |||||||||||||||
Conclusion (Pass /Fail) | PASS | |||||||||||||||||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID | Bulk_PM_E2E_02 | ||||||
---|---|---|---|---|---|---|---|
Test Case Name | DmaaP topic for unauthenticated.VES_NOTIFICATION_OUTPUT | ||||||
Description | Ensure that the unauthenticated.VES_NOTIFICATION_OUTPUT topic is present on the DMaaP Message Router once it receives "File Ready" VES notification from VES Collector. | ||||||
Release | Casablanca | ||||||
Pre-conditions | 1 .The DmaaP Message Router is up and running. 2. The Previous Test case has passed and its environment is still running | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | PASS | ||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID | Bulk_PM_E2E_ |
---|
03 | |
---|---|
Test Case Name | Download of xml PM file(s) from xNF when 'FileReady' VES event is received. |
Description | Ensure that the Data File Collector starts to download the xml PM file(s) from the simulated xNF once it receives the 'FileReady' VES event via the VES collector. |
Release | Casablanca |
Pre-conditions | The Previous Test case has passed |
- The FTPes is successfully initiated.
- The xml PM file is successfully downloaded by the File Collector.
and its environment is still running |
Testing Steps |
- The File Collector initiates a FTPes session with the simulated xNF.
- The File Collector downloads an XML file.
|
Conclusion (Pass /Fail) | PASS |
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID | Bulk_PM_E2E_ |
---|
04 | |
---|---|
Test Case Name | File Collector informs Data Router of xml PM file(s) |
Description | Ensure that the PM xml file(s) are published to the Data Router. |
Release | Casablanca |
Pre-conditions | The Previous Test case has passed |
and its environment is still running | ||||||
Testing Steps |
|
| ||
Conclusion (Pass /Fail) | PASS | |
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID | Bulk_PM_E2E_ |
---|
04a | |
---|---|
Test Case Name | Simulated File Consumer receives the xml PM file(s) |
Description | Ensure that a simulated File Consumer is able to subscribe and consume the PM file(s) from the Data Router. |
Release | Casablanca |
Pre-conditions | The Previous Test case has passed |
and its environment is still running | ||||||
Testing Steps |
|
|
|
| |
Conclusion (Pass /Fail) | PASS |
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID | Bulk_PM_E2E_05 |
---|---|
Test Case Name | Verify the Data File Collector Metadata file is |
valid | |||||||
Description | Verify that the Metadata for the PM xml file is correct | ||||||
Release | Dublin | ||||||
Pre-conditions | The Previous Test case has passed and its environment is still running | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | PASS | ||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID | Bulk_PM_E2E_06 | ||||||
---|---|---|---|---|---|---|---|
Test Case Name | Verify PM-Mapper successfully receives uncompressed the PM XML file | ||||||
Description | Verify 3GPP PM Mapper successfully receives the uncompressed PM xml file from the DataRouter | ||||||
Release | Dublin | ||||||
Pre-conditions | The Previous Test case has passed and its environment is still running | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | PASS | ||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Test Case ID | Bulk_PM_E2E_07 | ||||||
---|---|---|---|---|---|---|---|
Test Case Name | Verify PM-Mapper successfully publishes a PMMeasResult VES Messageonto the Message Router Topic "PM_MAPPER" | ||||||
Description | Verify that the PM-Mapper successfully publishes the VES Message on the topic "PM_MAPPER" | ||||||
Release | Dublin | ||||||
Pre-conditions | The Previous Test case has passed and its environment is still running Table | ||||||
Testing Steps |
| ||||||
Conclusion (Pass /Fail) | PASS | ||||||
Testing Lab | https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine |
Information:
For more information on the DMaaP API's see this link DMaaP API
Next Step(s):
Write Tests cases to verify BulkPM on an ONAP environment.
Anchor | ||||
---|---|---|---|---|
|
Performance Verification:
- To arrive at the xNF’s that 5G - Bulk PM E2E can handle, two scenarios must be fulfilled and measured.
1.X Number of xNF’s sending a VES FileReady Event every 15 minutes to an ONAP until PM-Mapper has finished processing the last PM file that was sent in that ROP.
2.ONAP looses connection to X Number of xNF’s and ONAP gains re-connection to the xNF after 1 day, this gives a maximum number of new PM files in the VES FileReady event 96*X Number of xNF’s.
1.When adding 70 new xNF’s every 1.5hours to mimic xNFs being added to an ONAP deployment up to 420 xNF (420 new PM files every 15 minutes) , it takes 4 minutes for all the 420 xNF PM Files to be processed in the Bulk PM e2e Flow.
2.For a spike of 420 xNF’s, its took Bulk PM 5 hours to process the backlog i.e all the initial 40,320 (96* 420) PM files and 420 new PM files every 15 minutes.
For more information on how the 420 xNF's was obtained see the slidepack Integration Meeting.pptx