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 HTTPSSFTP. 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 |
|
| |||||||||||||||||||||||||
| DMaaP | Ramprasad Koya |
|
| ||||||||||||||||||||||||
| VNFRQTS |
|
|
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
End to End flow to be Tested: DCAE 3GPP PM Mapper| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Gliffy Diagram | ||||||||
| size | 500 | |||||||
| name | Summary SeqDia Template | |||||||
| pagePin | 2 | |||||||
|
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 |
| ||||
| 2 | DCAE VES Collector: Ensure fileReady event is processed and forwarded to correct topic onDCAE Message Router. Expected outcome: fileReady event on correct MR topic |
| ||||
3 | DCAE File DCAE Data File Collector: Ensure fileReady event is received from DCAE Message Router. Expected outcome: fileReady event received by Data File Collector |
| ||||
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 |
| ||||
| 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. |
| ||||
| 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. |
| ||||
| 5 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 |
| ||||
| 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 |
| ||||
| 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. |
| ||||
| 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. |
| ||||
| 611 | DCAE Data File Collector: Ensure the connection to xNF is closed. Expected outcome: Connection to xNF is closed. |
| ||||
| 712 | DCAE Data File Collector: Ensure the data file(s) retrieved for that processed fileReady event are published to. Expected outcome: Data retrieved is avaialble on correct feed on DMaaP Data Router . |
|
Q: Should we need separate test cases for validation and error handling scenario? Or just include in above as exceptions per test case?
Test Cases and Status: DCAE 3GPP PM MapperTest environment requirements for above test cases:
|
End-to-End feature integration : To be Tested
| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
|
End-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. |
| 2 |
| 3 |
|
| ||||||||||||||||||
| 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. |
| |||||||||||||||||||||||
| 3 | Ensure that the PM xml file(s) are published to the Data Router. |
| |||||||||||||||||||||||
| 4 | Ensure that the File Consumer is able to subscribe and consume the PM file(s) from the Data Router. |
| |||||||||||||||||||||||
| 5 | Ensure that a simulated File Consumer is able to subscribe and consume the PM file(s) from the Data Router. |
| |||||||||||||||||||||||
| 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) |
| |||||||||||||||||||||||
Test environment requirements for above test cases:
| 4 |
| 5 |
| 6 |
| 7 |
|