Table of Contents |
---|
Contacts and other Resources
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CPS-97
...
Issues/Decisions
# | Slogan | Notes | Decision |
---|---|---|---|
1 | What model is being used for the SON PIC use case? | ran-network@2020-08-06.yang will be used for both E2E Network Slicing and SON PIC use cases | |
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 Models & Data
Models
- oofpcipoc.yang (model A)
- oofpcipoc-tree3.txt
- ran-network@2020-08-06.yang (model B)
- ran-network-tree-11.txt
Data
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
...