5G - Bulk PM
The bulk PM feature consists of two main parts:
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 (committed) or SFTP. The collected data files are published internally on a DMaaP Data Router (DR) feed.
For 3GPP formatted measurement data and for consumers that prefer such data in VES format, an optional 3GPP PM Mapper micro-service is planned that can extract selected measurements from a 3GPP XML file and publish them as VES events on a DMaaP Message Router topic. The mapper receives the files by subscribing to a Data Router feed.(Strech Goal For Casablanca)
Presentations:
Development Status
Project | PTL | JIRA | Description |
|---|---|---|---|
DCAE | @Lusheng Ji | https://lf-onap.atlassian.net/browse/DCAEGEN2-566 |
|
DMaaP | @Ramprasad Koya |
| |
VNFRQTS | @Steven wright |
|
Testing
Current Status
Testing Blockers
High visibility bugs
Other issues for testing that should be seen at a summary level
Where possible, always include JIRA links
Test contacts:
Rajendra Jaiswal rajendra.jaiswal@ericsson.com
Liam Burke liam.burke@ericsson.com
End to End flow to be Tested: DCAE Data File Collector
Gliffy Diagram is only supported by the cloud editor
Because Forge macros arent supported by the legacy editor, you'll need to convert this content to the cloud editor to display this macro properly. Find out more about converting to the cloud editor
Test Cases and Status: DCAE Data File Collector
# | Test Case | Status |
|---|---|---|
1 | xNF: Ensure fileReady event is received from xNF at DCAE VES collector. Expected outcome: fileReady event received, and meets VES 7.x specification | Not yet tested |
2 | DCAE VES Collector: Ensure fileReady event is processed and forwarded to DCAE Message Router. Expected outcome: fileReady event on correct MR topic | Not yet tested |
3 | DCAE Data File Collector: Ensure fileReady event is received from DCAE Message Router. Expected outcome: fileReady event received by Data File Collector | Not yet tested |
4 | DCAE Data File Collector: Ensure event is processed and any invalid file entries (i.e. missing or corrupt data) are logged. Expected outcome: any fileReady event which does not meet VES 7.x specification is logged as invalid event | Not yet tested |
5 | DCAE Data File Collector: After succesful event parsing, confirm secure connection to file location is initiated for file retrieval. Expected outcome: connection to xNF file location contained in the event. | Not yet tested |
6 | DCAE Data File Collector: Confirm that any unsuccessful connection attempts are logged. Expected outcome: any errors such as authentication failed, destination unreachable, etc. are logged. | Not yet tested |
7 | DCAE Data File Collector: Ensure that for each new entry in the fileReady event the file is retrieved. Expected outcome: every file indicated in the fileReady event is retreived from the xNF | Not yet tested |
8 | DCAE Data File Collector: Ensure any files which are not available are logged. Expected outcome: any errors such as non-existant file (e.g. file removed before retrieval) are logged | Not yet tested |
9 | DCAE Data File Collector: Confirm that in the event a file fails to transfer successfully, retry is initiated. Expected outcome: Retry is initiated for unsuccessful transfer. | Not yet tested |
10 | DCAE Data File Collector: Confirm that in the event the maximum number of retries is exceeded, an error is logged. Expected outcome: Error log indicating that the file was not able to retrieved. | Not yet tested |
11 | DCAE Data File Collector: Ensure the connection to xNF is closed. Expected outcome: Connection to xNF is closed. | Not yet tested |
12 | DCAE Data File Collector: Ensure the data file(s) retrieved for that processed fileReady event are published. Expected outcome: Data retrieved is avaialble on correct feed on DMaaP Data Router | Not yet tested |
|
|
|
|
|
|
| Test environment requirements for above test cases:
|
|
End-to-End feature integration : To be Tested
Gliffy Diagram is only supported by the cloud editor
Because Forge macros arent supported by the legacy editor, you'll need to convert this content to the cloud editor to display this macro properly. Find out more about converting to the cloud editorEnd-to-End feature integration:
Test cases (tbd) to test end-to-end feature interaction for PnP, Bulk PM (File collector + Mapper), closed loop (e.g. TCA triggered on specific PM counter in the bulk data) and action performed.
# | Test Case | Status |
|---|---|---|
1 | Ensure that the 'FileReady' VES event is sent from the simulated xNF via the VES collector and is received by Data File Collector. | DONE |
2 | 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. | DONE |
3 | Ensure that the PM xml file(s) are published to the Data Router. | DONE |
4 | Ensure that the File Consumer is able to subscribe and consume the PM file(s) from the Data Router. | DONE |
5 | Ensure that a simulated File Consumer is able to subscribe and consume the PM file(s) from the Data Router. | DONE |
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) | STRETCH GOAL |
| Test environment requirements for above test cases:
|