[OVSDB-427] OVS nodes should be load-balanced among ODL nodes Created: 06/Sep/17 Updated: 04/Aug/20 |
|
| Status: | Open |
| Project: | ovsdb |
| Component/s: | Clustering |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Stephen Kitt | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
Currently switches are managed by whatever controller node responds first when they connect. There should be a mechanism to allow the OVSDB plug-in to load-balance switches among the controller nodes. (It's probably worth analysing the impact of shard leadership too.) |
| Comments |
| Comment by Anil Vishnoi [ 08/Sep/17 ] |
|
I believe EOS implementation has a load balancing strategy for distributing the ownership. That need to be explored and tested with the existing cluster code to see if that works out of the box. |