[BGPCEP-373] Move BGP/PCEP configuration into the data store Created: 23/Jan/16 Updated: 03/Mar/19 Resolved: 05/Jan/18 |
|
| Status: | Verified |
| Project: | bgpcep |
| Component/s: | General |
| Affects Version/s: | Bugzilla Migration |
| Fix Version/s: | Oxygen |
| Type: | Improvement | ||
| Reporter: | Tom Pantelis | Assignee: | Claudio David Gasparini |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
In Be, configuration of netconf connectors was moved from the config system to the data store. This bug is a request to do the same for BGP/PCEP configurations. This will make it easier for upgrades. Currently, using the config system, the user-facing config is mixed with the internal code wiring which is a pain-point for upgrades if the code wiring is changed but the user-facing config needs to be preserved. This becomes even worse if configs are pushed via the controller-config loopback mount as all the configs are munged into the uber current.xml. |
| Comments |
| Comment by Milos Fabian [ 19/Apr/16 ] |
|
BGP already supports configuration via OpenConfig BGP API https://wiki.opendaylight.org/view/BGP_LS_PCEP:User_Guide#OpenConfig_BGP |
| Comment by Tom Pantelis [ 19/Apr/16 ] |
|
Yeah I found that out later. However I've been told that there are parts of it (maybe PCEP config) that still uses the config system. |
| Comment by Milos Fabian [ 27/Jul/16 ] |
|
BGP: |
| Comment by Milos Fabian [ 01/Sep/16 ] |
|
TODOs for Carbon: |