[NETCONF-22] Need to define Netconf Clustering/Data Persistence Behavior Created: 31/Mar/15 Updated: 15/Mar/19 Due: 03/Dec/15 Resolved: 22/Feb/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Reinaldo Penno | Assignee: | Tomas Cere |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2922 |
| Description |
|
Given the with clustering enabled data is persistent, how will Netconf behave in the light of bugs 2920 and 2921? SFC relies on Netconf maintaining the netconf topology accurately so defining the behavior in the light of data persistence and fixing any bugs is paramount for SFC to work properly. In the case of Netconf, it seems there is a further complication in that it maintains a list of netconf nodes it knows about in current_config.xml across Karaf reboots. |
| Comments |
| Comment by Robert Varga [ 13/Nov/15 ] |
|
Move to NETCONFI project. |
| Comment by Tomas Cere [ 05/Jan/16 ] |
|
https://git.opendaylight.org/gerrit/#/q/topic:netconf-clustering |
| Comment by Colin Dixon [ 07/Jan/16 ] |
|
I don't see where in those patches we actually "define Netconf Clustering/Data Persistence Behavior". Did I miss something? It would be nice to actually understand what the desired behavior was. |
| Comment by Tony Tkacik [ 12/Jan/16 ] |
|
Configuration persistance as of now is defined by CDS behaviour instead of seperate behaviour model inherited via use of config subsystem. |
| Comment by Tomas Cere [ 22/Feb/16 ] |