Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
For the eventually consistent stores, events are partially ordered with vector clocks. The logical clock used by the DeviceStore and LinkStore is a combination of the number of mastership handoffs for a device since its discovery (its term number), and a sequence number local to the node that is incremented per timestamp generation. The HostStore relies on system time (the wall clock), due to the lifespan of Host objects and their mobility . At the moment, this limits what can be used as the basis for a HostEvent timestamp.that prevents them from being tied to a particular device.
Cluster Management
| Info |
|---|
ONOS also uses the term 'cluster' to refer to connected subgraphs of the network topology, which has no association to the cluster in the multi-instance sense. When clusters are mentioned in this section, they are strictly in terms of the latter. |
...
The current ONOS implementation does not handle the case where the partitions are equal in size, and both are still connected to the network.
Relation to the Device Subsystem
The Device subsystem uses the role information maintained by the MastershipManager in order to determine which nodes are allowed to interact in what way with the devices that it has knowledge about. The MastershipManager also listens for device events as cues to force role reelections and relinquishments. Finally, any role-related control messages to and from the network, such as OpenFlow RoleRequests and RoleReplies, must be sent and received via DeviceProviders; therefore, the DeviceService must manipulate the network on behalf of the MastershipService.