[CONTROLLER-1146] Clustering: Dynamically load different RoutingLogic implementations based on installed karaf features Created: 10/Feb/15 Updated: 25/Aug/15 Resolved: 25/Aug/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | Post-Helium |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Gary Wu | Assignee: | Xueke Li |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
For the Unified Secure Channel (USC) Project (https://wiki.opendaylight.org/view/USC:Main) in Lithium, there may need to be a mechanism for the controller to dynamically load an alternative RoutingLogic implementation based on whether the USC karaf feature is installed. Implementation details TBD. There may be some commonality between this requirement and the requirements from OpenFlow's device mastership concept, e.g. always route RPC calls to the device master. |
| Comments |
| Comment by Tom Pantelis [ 10/Feb/15 ] |
|
One thing to consider is whether the USC-specific RoutingLogic impl would be applied globally and, if so, how that would affect other apps. Maybe it might be possible to configure the RoutingLogic impl per RPC type. So if USC is defining its own RPCs then the USC-specific RoutingLogic would only apply to those. |
| Comment by Moiz Raja [ 25/Aug/15 ] |
|
Not needed anymore |