...
| Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CPS-200 |
|---|
|
Models and data
There was an issue with the original json data provided. We corrected this issue by modifying the root element.
cps-ran-inventory.yang-data-incorrect.json (original)
cps-ran-inventory-data.json (corrected)
cps-ran-inventory.yang
Queries used for the RAN inventory model
| API Path | Description of Operation |
|---|
| GET /ran-inventory/sliceProfilesList/{sNSSAI} | Find a slice profile list that has the given sNSSAI value |
For the model provided above it will return: leafsNSSAI typestring mandatory false The S-NSSAI may include bothList of slice profiles supported by the |
|
SST and SD fields (in which case the S-NSSAI length is 32 bits in total), or the S-NSSAI may just include the SST field (in which case the S-NSSAI length is 8 bits only)";
}
- use query of cpsPath starting with given path (maybe even add '[') - '/ran-inventory/sliceProfilesList[@sliceProfileId=\'f33a9dd8-ae51-4acf-8073-c9390c25f6f1\']
- use json-query tools to only get the 'fragment' that contain required name-value pair
(probably need native-query annotation)
|
| PUT /ran-inventory/{rannfnssiid}/sliceProfilesList/ | Add/update the given slice profile for the given rannfnssi |
Groovy Test - E2E Coverage Area-Tracking Area & TA-Cell mapping data can be parsed for RAN inventory
...
