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 HTTPS. 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.
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
End to End flow to be Tested: DCAE Data File Collector
End to End flow to be Tested: DCAE 3GPP PM Mapper
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 output: fileReady event received | NOT YET TESTED |
2 | DCAE VES Collector: Ensure fileReady event is processed and forwarded to correct topic on DCAE Message Router. | NOT YET TESTED |
3 | DCAE File Collector: Ensure fileReady event is received from DCAE Message Router. | NOT YET TESTED |
4 | DCAE File Collector: Ensure event is processed and any invalid file entries (i.e. missing or corrupt data) are logged. Expected output: fileReady event meets VES 6.x specification | NOT YET TESTED |
5 | DCAE File Collector: After succesful event parsing, confirm connection to file location is initiated for file retrieval. E.g. connection to xNF file location contained in the event. | NOT YET TESTED |
6 | DCAE File Collector: Confirm that if a successful connection can not be made to the location, an error log is raised. E.g. authentication failed, destination unreachable, etc. | NOT YET TESTED |
7 | DCAE File Collector: Ensure that for each new entry in the fileReady event the file is retrieved. | NOT YET TESTED |
8 | DCAE File Collector: Ensure any files which are not available are logged. E.g. file no longer on the xNF, logged as non-existant file. | NOT YET TESTED |
9 | DCAE File Collector: Confirm that in the event a file fails to transfer successfully, retry is initiated. | NOT YET TESTED |
10 | DCAE File Collector: Confirm that in the event the maximum number of retries is exceeded, an error is logged. E.g. file not able to be retrieved. | NOT YET TESTED |
11 | DCAE File Collector: Ensure the connection to xNF is closed. | NOT YET TESTED |
12 | DCAE File Collector: Ensure the data file(s) retrieved for that processed fileReady event are published to correct feed on DMaaP Data Router. | NOT YET TESTED |
Test environment requirements for above test cases:
|
Test Cases and Status: DCAE 3GPP PM Mapper
# | Test Case | Status |
---|---|---|
1 | DMaaP DR: Confirm that file is available on expected feed. | NOT YET TESTED |
2 | DCAE 3GPP PM Mapper: Confirm that DR client (mapper) is able to receive data file. | NOT YET TESTED |
3 | DCAE 3GPP PM Mapper: Confirm that mapper can validate the file using schema (e.g. 3gpp xml format). | NOT YET TESTED |
4 | DCAE 3GPP PM Mapper: Confirm any file validation errors are logged. | NOT YET TESTED |
5 | DCAE 3GPP PM Mapper: Confirm that mapper creates expected VES PM events for the mapped data. | NOT YET TESTED |
6 | DCAE 3GPP PM Mapper: Confirm that any mapping errors are logged. | NOT YET TESTED |
7 | DCAE 3GPP PM Mapper: Confirm that mapped events are forwarded on DCAE Messaeg Router. | NOT YET TESTED |
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.