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.
Design Decisions:
- Group Identifier will be represented as a simple Integer. Will be revisited at a later point of time to see if it needs to be aligned with PortNumber representation
- Group objects for a device will only be created/updated/removed by current Master controller instance.
- So as, the Group Identifier allocation/management also will only be done by current Master controller instance.
- Groups for a device are only replicated in the Master controller instance and another potential candidate instance. It is not replicated in all the instances.
- Group creation/update/removal/query request can be submitted in any controller instance and that instance will take care of routing the request to current Master controller instance.
- Group creation API does not return any Group object as in some scenarios the request needs to be routed to Master controller instance where the Group object gets created. Application should use Group Query API to retrieve the Group object after creation.
- Group query API blocks the caller thread until it retrieves from the remote Master controller instance if the instance where request is submitted is not having the control over that device
- Group query API returns the Group object even if the Group object is in PENDING_ADD state
- Group subsystem generates GROUP_ADDED event only after it receives confirmation from Data plane through Barrier Reply or Group Description Reply (In the first phase, it will be based on Group Description Reply)
Group Subsystem Design:
High level layout of Group subsystem components is depicted below.
...