...

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)

...

A1 Mediator/Real-RT RIC
- A1 Mediator (Developer version 1.0.0), is currently deployed in the Windriver Lab in a standalone VM (without full RIC deployment), and can be accessed at 10.12.7.38:10001.
- Details about RIC deployment and HELM charts can be found at: https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt%2Fric-dep.git;a=shortlog;h=refs%2Fheads%2Fmaster
ONAP (Non-RT RIC)
- Use Frankfurt ONAP deployment
- Configuration changes to the DG properties file required, if testing/deployment is done against A1 mediator other than described below
  - Properties file: /opt/onap/ccsdk/data/properties/a1-adapter-api-dg.properties
    - SSH into rancher node (NFS/rancher)
    - sudo su
    - kubectl get pods -n onap -o wide | grep sdnc
    - Execute the following command to all sdnc POD's to update properties file
      - kubectl exec -it dev-sdnc-sdnc-x bash (x=0, 1, 2, depending upon number of sdnc replicas in the setup)
    - Once in the docker, edit the properties file (/opt/onap/ccsdk/data/properties/a1-adapter-api-dg.properties)
    - Make following configuration changes per setup
      - Update IP address/port# for A1 Mediator (a.b.c.d:port# below)
        near-rt-ric-id=a.b.c.d:port#

...

Mapping of flow to Test Cases described here:

Following is the current testing environment in the WIndriver Lab:

...

Perform testing and further development against full-blown RIC deployment that includes A1 mediator
Modify DG's to ensure RequestID and CorrelationID are in sync for DMAAP request and response messages
Integrate ONAP/A1 Mediator with Near-RT deployment
Any code changes to conform to the latest A1 Mediator OpenAPI specs (2.1.0)
Current Gaps and Limitations
- A1 mediator response to getStatus RPC is not rendered correctly for DMAAP response message
- For few API requests to A1 Mediator, there is no response message payload, and for these situations, DMAAP response message payload indicates "Working On it"

11. Supporting Documents

...

Versions Compared