[CONTROLLER-648] Configuration File for Plug-ins (not controller) Created: 24/Jul/14 Updated: 25/Jul/23 Resolved: 05/May/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | config |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Reinaldo Penno | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| Description |
|
Many plug-ins need a configuration file to bootstrap their state. Instead of each one coming one with a separate solution, there should be a standardized way to provide a configuration file to ODL that is read at bootup and commited to data store. Ideally such configuration file would contain the JSON object of yang based models that can be read by controller and committed to data store. |
| Comments |
| Comment by Tony Tkacik [ 30/Jul/14 ] |
|
This seems as usecase for Configuration subsystem, or you mean bootstraping initial value of MD-SAL Datastore from XML/JSON? |
| Comment by Reinaldo Penno [ 31/Jul/14 ] |
|
We solved it for our plug-in. We have series of JSON config files that drive the behavior and datastore of our plug-in. |