2am PDT → 5am EDT → 11:00 CEST → 12:00 EEST → 17:00 CST
(please feel free to correct, update your names Thank you very much!!!)
|0min||chair topic||no update|
2020-03-25: Martin Skorupski
2020-04-01: Martin Skorupski
2020-04-08: Thorsten Heinze
2020-04-15: Martin Skorupski
core-model allows definition of both Logical Termination Points (interfaces), but also connections
core-model is also suitable for representing entire Networks, not only a Device
this means that Universally Unique IDs are required
Devices cannot get the UUIDs from outside, they need to be generated by the device, and cannot be overwritten from outside
Devices are unaware by their surroundings (the network), so it cannot know if a UUID is already used by some other interface in other devices
IETF defines how to create UUIDs, and the core-model references this RFC
Out of time, we need to follow up: proposal, next week Tuesday 09:00 CET
Discussion about UUID and Links/Asszosations/References between object classes
ODL MountPoint is and association to a NetConf server - some NetConf servers representing some times the microwave model.
UUID would be unique when the combination of device-id/mountpoint-name/network-element-name and device internal ids are unique.
UUID are created in advance by Planning Tools - and could be derived from expected equipment.
Idea: Planning tool deals with hardware templates - Requirement: capabilities, validation