Versions Compared

Old Version 14

changes.mady.by.user Sandeep Shah

Saved on

compared with

New Version 15

changes.mady.by.user Toine Siebelink

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Issues/Decisions

#SloganNotesDecision
1What model is being used for the SON PIC use case?

oofpcipoc.yang or ran-network@2020-08-06.yang

ran-network@2020-08-06.yang will be used for both E2E Network Slicing and SON PIC use cases
2Yang 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

  • Import without revision (and include without revision) is commonly used in YANG and must be supported. They are widely used in IETF modules and others.
  • Where the YANG library is available, the YANG library will contain the revision of the module to be used.
  • Where the YANG library is not available, the semantics are such that the “newest” revision of the module shall be used.
3Is 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:
         <bundle>mvn:org.opendaylight.mdsal.binding.model.ietf/rfc6991-ietf-yang-types/2.0.17</bundle>
         <bundle>mvn:org.opendaylight.mdsal.binding.model.ietf/rfc6991-ietf-inet-types/2.0.17</bundle>
 https://mvnrepository.com/artifact/org.opendaylight.mdsal.binding.model.ietf/rfc6991-ietf-yang-types


...