[NETCONF-143] Unable to fully override netconf device capabilities Created: 08/Feb/16 Updated: 15/Mar/19 Resolved: 01/Mar/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Maros Marsalek | Assignee: | Maros Marsalek |
| 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: | 5269 |
| Description |
|
It's impossible to override device module-based capabilities with custom capabilities for custom modules. The default behavior in sal-netconf-connector is merge only and cannot be configured. In some situations, it makes a lot of sense to completely override device yang models with app/user models. An example would be device with many models violating YANG RFC, but only a subset required in ODL. Then the easiest way is to fix broken models required by ODL, and set only those as device module-based capabilities. |
| Comments |
| Comment by Maros Marsalek [ 08/Feb/16 ] |
| Comment by Maros Marsalek [ 08/Feb/16 ] |
|
This is a blocker for a certain, closed-source, ODL based project. The project needs to be based on Beryllium stable release and this bug prevents it. |
| Comment by Ryan Goulding [ 09/Feb/16 ] |
|
This was merged, can we close this? |
| Comment by Tomas Cere [ 09/Feb/16 ] |
|
decreasing importance since the fix was merged, we still need to do this for the topology configuration |
| Comment by Ryan Goulding [ 09/Feb/16 ] |
|
Well this would imply divergent behavior between the two methods. Is this something scheduled for Beryllium or Beryllium-SR1? |
| Comment by Tony Tkacik [ 01/Mar/16 ] |