The below indicates high-level test cases for A1 Adapter in ONAP to interface with A1 Mediator in RT RIC. The test cases will be further detailed out before the testing cycle.
...
# | Component(s) | Test Case | Status | Remarks |
|---|---|---|---|---|
| #1 | SDN-R/A1 Adapter and A1 Mediator | A1 Adapter in Non-RT RIC establishes connection with A1 Mediator in RT RIC | NOT STARTED | |
| #2 | SDN-R/A1 Adapter and ONAP components | Upon receiving A1 Policy management DMAAP message from any ONAP components or micro-services, SDNR sends corresponding A1 message to A1 Mediator in Near Real TIme RIC. | NOT STARTED | Currently there are close to 10 A1 messages that will be supported in Frankfurt, and individual test cases will correspond to the respective A1 messages |
#3 | SDN-R/A1 Adapter and ONAP components | SDNR is able to receive A1 message on A1-P topic and invoke corresponding RPC to trigger respective DG | NOT STARTED | Currently there are close to 10 A1 messages that will be supported in Frankfurt, and individual test cases will correspond to the respective A1 messages |
#4 | SDN-R/A1 Adapter and ONAP components | RPC/DG execution: Verify if respective A1 Rest API is invoked against A1 Mediator, based on the received A1 Policy management DMAAP message | NOT STARTED | Currently there are close to 10 A1 messages that will be supported in Frankfurt, and individual test cases will correspond to the respective A1 messages |
#5 | SDN-R/A1 Adapter and ONAP components | RPC/DG execution: Verify if DMAAP message confirming success or failure of API transaction with A1 mediator is published on A1-P-RSP topic. This DMAAP message to be consumed by ONAP components, as confirmation of its requested action | NOT STARTED | Currently there are close to 10 A1 messages that will be supported in Frankfurt, and individual test cases will correspond to the respective A1 messages |
| #6 | SDN-R/A1 Adapter and A1 Mediator | A1 Mediator in RT RIC to invoke Notification message against A1 Adapter | NOT STARTED | Would be tested using CURL, as the current A1 mediator does not implement notifications |
1. DMAAP Message
DMAAP Message Request (sent from ONAP or MS components):
Topic: A1-P { "body": { "input": { "CommonHeader": { "TimeStamp": "2018-11-30T09:13:37.368Z", "APIver": "1.0", "RequestID": "9d2d790e-a5f0-11e8-98d0-529269fb1459", "SubRequestID": "1", "RequestTrack": {}, "Flags": {} }, "Action": "getNearRT-RICs", "Payload": {"input": {"dummy": "dummy"}} }, "version": "1.0", "rpc-name": "getNearRT-RICs", "correlation-id": "9d2d790e-a5f0-11e8-98d0-529269fb1459-1", "type": "request" } } |
|---|
DMAAP Message Response (sent from A1 Mediator with status response)
Topic: A1-P-RSP { "body": { "output": { "CommonHeader": { "TimeStamp": "2018-09-10T07:10:05.614Z", "APIver": "1.0", "RequestID": "9d2d790e-a5f0-11e8-98d0-529269fb1459", "SubRequestID": "1", "RequestTrack": [], "Flags": [] }, "Status": { "Code": 200, "Value": "SUCCESS" }, "Payload": "[ 10.12.7.38:10001 ]" } }, "version": "1.0", "rpc-name": "getNearRT-RICs", "correlation-id": "9d2d790e-a5f0-11e8-98d0-529269fb1459-1", "type": "response" } |
|---|
DMAAP message payload is aligned with YANG RPC Input parameters and is exactly the same as, when YANG model RPC input is rendered as a JSON object. See the above example, where DMAAP message is related to RPC "getNearRT-RICs".
IMPORTANT: Please note that “input” key needs to be included in the payload. Escape characters ARE NOT to be INCLUDED.
2. DMAAP Message Request Payload
| RPC | DMAAP Message Request Payload |
| getNearRT-RICs | { "input" : { "dummy" : "Hello" } } |
| getHealthCheck | { "input" : { "near-rt-ric-id" : "10.12.7.38:10001" } } |
| getPolicyTypes | { "input" : { "near-rt-ric-id" : "10.12.7.38:10001" } } |
| getPolicyType | { "input" : { "near-rt-ric-id" : "10.12.7.38:10001", “policy-type-id": “20001" } } |
| deletePolicyType | { "input" : { "near-rt-ric-id" : "10.12.7.38:10001", “policy-type-id": “20001" } } |
| createPolicyType | { "input" : { } } |
| getPolicyInstances | { "input" : { "near-rt-ric-id" : "10.12.7.38:10001", “policy-type-id": “20001" } } |
| getPolicyInstance | { "input" : { "near-rt-ric-id" : "10.12.7.38:10001", “policy-type-id”: “20001”, “policy-instance-id”: “” } } |
| deletePolicyInstance | { "input" : { "near-rt-ric-id" : "10.12.7.38:10001", “policy-type-id": “20001", “policy-instance-id": “" } } |
| createPolicyInstance | { "input" : { } } |
| getStatus | { "input" : { "near-rt-ric-id" : "10.12.7.38:10001", “policy-type-id": “20001", “policy-instance-id": “" } } |
| notifyPolicyEnforcementUpdate | { "input" : { "near-rt-ric-id" : "10.12.7.38:10001", “policy-type-id": “20001", “policy-instance-id": “" } } |
3. DMAAP Message Response Payload
...