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
Gliffy Diagram | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
End to End flow to be Tested: DCAE 3GPP PM Mapper
Gliffy Diagram | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Test Cases and Status: DCAE Data File Collector
# | Test Case | Status | ||||
---|---|---|---|---|---|---|
1 | xNF: Ensure fileReady event is received from xNF at DCAE VES collector. |
| ||||
2 | DCAE VES Collector: Ensure fileReady event is processed and forwarded to correct topic on DCAE Message Router. |
| ||||
3 | DCAE File Collector: Ensure fileReady event is received from DCAE Message Router. |
| ||||
4 | DCAE File Collector: Ensure event is processed and any invalid file entries (i.e. missing or corrupt data) are logged. |
| ||||
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. |
| ||||
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. |
| ||||
75 | DCAE File Collector: Ensure that for each new entry in the fileReady event the file is retrieved. |
| ||||
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. |
| ||||
9 | DCAE File Collector: Confirm that in the event a file fails to transfer successfully, retry is initiated. |
| ||||
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. |
| ||||
116 | DCAE File Collector: Ensure the connection to xNF is closed. |
| ||||
712 | DCAE File Collector: Ensure the data file(s) retrieved for that processed fileReady event are published to correct feed on DMaaP Data Router. |
|
13 | DMaaP DR: Confirm that DR client is able to subscribe and receive data file on expected feed. |
| ||||
14 | DCAE File Collector: Robustness testing. uService failures. uService behaviour tbd, test case to be defined. |
| ||||
15 | DCAE File Collector: Robustness testing, missed 'fileReady' event handling. uServcie behaviour tbd, test case to be defined. |
| ||||
Test environment requirements for above test cases:
|
Test Cases and Status: DCAE 3GPP PM Mapper
# | Test Case | Status | ||||
---|---|---|---|---|---|---|
1 |
| |||||
2 |
| |||||
3 |
| |||||
4 |
| |||||
5 |
| |||||
6 |
| |||||
7 |
|