[MDSAL-390] Entity Ownership Service: need to exchange state for generations Created: 26/Jan/16 Updated: 14/Nov/18 |
|
| Status: | Confirmed |
| Project: | mdsal |
| Component/s: | EOS |
| Affects Version/s: | Fluorine |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| Description |
|
The OpenFlow specification assumes strongly-consistent controllers in that each role change needs to specify the generation ID (a 64bit integer). This means that nodes participating in control of a particular switch need to have a strongly-consistent view of what the current generation is. The generation needs to change any time the set of candidates changes, or when a master/slave transition occurs. Note that the fact this is 64 bit integer and its assignement rules are protocol-specific, hence the EOS APIs need to provide a way for OF to plug in and manage this piece of state. |
| Comments |
| Comment by Robert Varga [ 30/Mar/16 ] |
|
Thinking about this a bit more, it would be sufficient if EOS exposed a 64bit generation number which would be incremented every time ownership change is performed. |