Page History

...

//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. 

The agreed solution is to split the query to get the CM Handles where the operational sync state in UNSYNCHRONIZED and select a random CM Handle and check the status of the CM Handle in READY state.

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.

...

The data received from the RAN should be updated in the CPS DB. The CPS currently supports the persist of the data in the format below. eg: stores:bookstore in the format <module>:<top level container>

The PNF simulator returns multiple resources but the actual RAN will return just one resource. So it is agreed to persist the first resource that is received from the RAN. 

{
  "stores:bookstore": {
    "categories": [
      {
        "code": "05",
        "books": [
          {
            "title": "A Romance Book",
            "price": "2000",
            "pub_year": 2002,
            "lang": "English",
            "authors": [
              "Lathish"
            ]
          }
        ],
        "name": "Romance"
      }
    ]
  }
}

...