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
**This should be a summary level Sequence diagram done in Gliffy**: DCAE Data File Collector
| 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 | ||||||
|---|---|---|---|---|---|---|---|---|
| 1There should be a test case for each item in the sequence diagram | 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 connection to file location is initiated for file retrieval. |
| ||||||
| 5 | DCAE File Collector: Ensure that for each new entry in the fileReady event the file is retrieved. |
| ||||||
| 6 | DCAE File Collector: Ensure the connection is closed. |
| ||||||
| 2 | create additional requirements as needed for each discreet step |
| ||||||
| 3 | Test cases should cover entire Use Case |
| 4 | Test Cases should include enough detail for testing team to implement the test | ||||
| Status | ||||||||
| colour | Red | title | Failed||||||
| 7 | DCAE File Collector: Ensure the data file(s) retrieved for that processed fileReady event are published to 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 Mapper
| # | Test Case | Status | ||||
|---|---|---|---|---|---|---|
| 1 |
| |||||
| 2 |
| |||||
3 |
| |||||
4 |
| |||||
| 5 |
| |||||
| 6 |
| |||||
| 7 |
|