- CPS-97Getting issue details... STATUS
Contacts and other Resources
Issues/Decisions
# | Slogan | Notes | Decision |
---|---|---|---|
1 | What model is being used for the SON PIC use case? | ||
2 | Yang imports (in ran-network@2020-08-06.yang) do not mention version. Does that mean they always use latest? | 'Latest' module could change in an uncontrolled manner Have asked advise from Architect Team |
|
3 | Is it allowed to not include a imported module (without revision) | if the YANG library is not available, then there must have been some other well-defined way how you get the information about the modules that form a schema tree – perhaps netconf-monitoring, or some packaging solution. Currently, YANG models are integrated into ODL based CCSDK repo (as part of RANSlice feature), and parent POM files dictate versions for any common YANG files used across CCSDK/SDNC code. For example (as of Guilin release), following IETF import versions we are used: |
Yang Data Model(s)
- oofpcipoc.yang (model A)
- oofpcipoc-tree3.txt
- ran-network@2020-08-06.yang (model B)
- ran-network-tree-11.txt
Preload-JSON-Oct30.json (data for ran-network, model B)
- SDNC_ConfigDB_API_v4.0.0.json Includes (legacy) ConfigDB API definition for Slicing for refrrence purposes
Test Results
Test | ODL Parsing | Details |
---|---|---|
Passed | ||
ran-network@2020-08-06.yang | Passed | Downloaded latest version imported modules form internet and provide all 3 files to ODL Yang Parser |
Preload-JSON-Oct30.json |
Yang Features Used
# | Models | Feature | Impacts | Jira(s) | Notes |
---|---|---|---|---|---|
1 | AB | typedef | None | N/A | |
2 | AB | grouping | None | N/A | |
3 | AB | container | None | N/A | |
4 | AB | list with single key* | Add List | ||
5 | AB | list with composite key* | Store & retrieve list with composite key | ||
6 | AB | String length <min>..<max> | ? | Verify ODL YangTools behavior | |
7 | AB | default <default value> | ? | Verify ODL YangTools behavior | |
8 | AB | uses <grouping> | ? | Verify ODL YangTools behavior | |
9 | AB | reference | None | No effect on data or valdiation Internal Model Documentation only | |
10 | AB | mandatory | ? | Verify ODL YangTools behavior | |
11 | AB | config false | ? | TBD | |
12 | AB | leaf-list min-elements/max-elements | ? | Verify ODL YangTools behavior | |
13 | AB | range n1..n2 | ? | Verify ODL YangTools behavior | |
14 | AB | enum | ? | Verify ODL YangTools behavior | |
15 | AB | notification | Study "notification" in Yang | ||
16 | B | import (without revision, see issue #2) |
| ||
17 | B | units | None, only to be used in a future 'describe' method | ||
18 | B | config true | ? | ||
19 | B | range " n1 | n2 | n3 | n4 | .. | nn " | ? | Verify ODL YangTools behavior | |
20 | Imports | pattern | Hard to tell if this is used in actual models | Verify ODL YangTools behavior |
*Note all 'list' in both models are confirm to have keys
Examples of 'Slice' Data in Preload-JSON-Oct30.json
1 | "sliceProfilesList": [ { "sliceProfileId": "b594-e98r-c7f2-ij78", "sNSSAI": "10000100", "coverageAreaList": [ "Kingston" ], "resourceSharingLevel": "Shared", "uLThptPerSlice": 45, "maxNumberofConns": 5000, "uEMobilityLevel": "stationary", "latency": 0, "maxNumberofUEs": 2000, "dLThptPerSlice": 55 } ] | |
2 | ||
3 |