| Jira Legacy |
|---|
| server | ONAP System Jira |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a4733707d-557c2057-3c0c3a0f-b515ae5e-579789cceedb4fd8aff50176 |
|---|
| key | CPS-1000 |
|---|
|
The Data Synchronization watchdog updates the cps database with RAN CM Handle data. The Synchronization uses DMI passthrough service and SDNC to get the data from RAN. Refer here for more information.
...
| Code Block |
|---|
|
//state[@cm-handle-state="READY"]/ancestor::cm-handles | //state/datastore/operational[@sync-state="UNSYNCHRONIZED"]/ancestor::cm-handles |
CPS do not support AND operation in the query. Create a new user story to introduce this feature.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | CPS-1055 |
|---|
|
The agreed solution is to split the query to get the CM Handles where the operational state in UNSYNCHRONIZED and select a random CM Handle and check the status of the CM Handle in READY state.
| Code Block |
|---|
|
Query 1:
//state/datastore/operational[@sync-state="UNSYNCHRONIZED"]/ancestor::cm-handles
Query 2:
//cm-handles[@id='some-cm-handle']/state[@cm-handle-state="READY"] |
Step 2:
Get the CM Handle data from RAN through DMI passthrough service.
...