[OPNFLWPLUG-932] Revise mastership service APIs Created: 22/Aug/17 Updated: 27/Sep/21 Resolved: 02/May/19 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | Fluorine-SR2, Neon |
| Type: | Improvement | Priority: | High |
| Reporter: | Tomas Slusny | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | neon-release | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
Move FRM from notification, CSS and data-tree-change listener based approach to just using mastership service for notifying FRM when should reconciliation start to reduce code complexity and remove use of deprecated notificiations. |
| Comments |
| Comment by Tomas Slusny [ 22/Aug/17 ] |
| Comment by Anil Vishnoi [ 11/Jun/18 ] |
|
Arunprakash Hematg sunilkumarms gobinath Please review the existing mastership API's and lets discuss if the design is appropriate and the API's are clear, so that we can conclude whether we should open these API's to be consumed by other dependent applications. |
| Comment by Anil Vishnoi [ 02/Jul/18 ] |
|
Avishnoi Action: Start discussion on mailing list. |
| Comment by Anil Vishnoi [ 10/Sep/18 ] |
|
FRM is already fixed using these API's. We need to revise these API's to make sure these are the right API's to expose to all the OpenFlow application to use and make it public. These API's than will go through the standard process of deprecation and change in case required. |