[NETCONF-115] Extend netconf-node-topology model to distinguish user overriden capabilities from device reported capabilities Created: 04/Jan/16 Updated: 15/Mar/19 Resolved: 29/Oct/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Jakub Morvay | Assignee: | Rudolf Brisuda |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
Netconf-node-topology model currently does not distinguish between capabilities overrided by user (https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Connecting_to_a_device_not_supporting_netconf_monitoring) and device provided capabilities (reported in netconf monitoring and in netconf hello message). Both are listed just as available-capabilities. It would be better to see the difference. |
| Comments |
| Comment by Rudolf Brisuda [ 16/Aug/16 ] |
| Comment by Jakub Morvay [ 20/Oct/16 ] |
| Comment by Jakub Morvay [ 20/Oct/16 ] |
|
(In reply to Jakub Morvay from comment #2) Ignore this comment this is patch for another bug. |
| Comment by Jakub Morvay [ 20/Oct/16 ] |
|
Ok so this is the right one. |
| Comment by Jakub Morvay [ 21/Oct/16 ] |
|
We decided to add this enhancement only to Carbon. netconf-node-topology model is slightly changed, so it can cause some problems to applications built on boron. They would have to work with list of available capabilities instead of leaf-list of strings. Therefore, boron patch is abandoned. |
| Comment by Vratko Polak [ 29/Oct/16 ] |
|
> it can cause some problems to applications One of the applications affected in Carbon is Of-config project. |