...
Note: For the tests involving DMaaP, DMaaP should be set up. For API calls/responses, if the real components (e.g., OOF) are not available, stubs shall be used.
| S.No. | Description | Status | Remarks |
|---|
| 1. | SON Handler MS successfully on-boarded on to DCAE and comes online | |
Not yet tested |
|
| 2. | PostgreSQL DB (used by SON Handler MS) comes online | |
Not yet tested |
|
| 3. | SON Handler MS is able to successfully fetch configuration policies using CBS API | |
|
| 4. | SON Handler MS is able to subscribe to DMaaP messages | |
Not yet tested |
|
| 5. | SON Handler MS is able to receive messages on DMaaP (e.g., from SDN-R, VES-Collector, Policy) | |
Not yet tested |
|
| 6. | SON Handler MS is able to post messages on DMaaP (e.g., to Policy) | |
Not yet tested |
|
| 7. | SON Handler MS is able to read/write data (e.g., state info, FM data) into PostgreSQL DB | |
Not yet tested |
|
| 8. | SON Handler is able to invoke API call(s) to ConfigDB and handle the response | |
Not yet tested |
|
| 9. | SON Handler MS is able to invoke API call(s) towards OOF for PCI optimization | |
|
| 10. | SON Handler MS is able to handle callbackURL call (async response) from OOF, process it, and send out a DMaaP message (to Policy) | |
|
| 11. | SON Handler MS log message formats are compliant to the ONAP logging specifications | |
Not yet tested
2. Policy
| S.No. | Description | Status | Remarks |
|---|
| 1. | Policy Handler (DCAE) is able to fetch the SON-Handler MS config policies | |
Not yet tested |
|
| 2. | SON Control Loop to be extended to include handling of DMaaP message (response) from SDN-R | |
|
| 3. | Policy is able to receive the new DMaaP message from SDN-R to notify the result of changes in RAN | |
|
| 4. | Policy is able to send the new DMaaP message to SON-Handler MS to notify the result of changes in RAN (upon reception of DMaaP message from SDN-R) |
| 3. SDN-R and Config DB
| S.No. | Description | Status | Remarks |
|---|
1. | New API to update single cell's details in DB works successfully2.
