-
Notifications
You must be signed in to change notification settings - Fork 10
Actions
Jason Edelman edited this page Apr 28, 2014
·
1 revision
- Define what should be included in device "facts"
- Decide to focus on extracting data or extracting and/or pushing changes
- Decide on formats for -time, -macaddr, -date,
- Should we maintain a master dictionary for each device, i.e. dict of dict's. This reminds me of Arista's sysDB or OVSDB making it easier to integrate for 3rd party tooling, but while on CLI, either or can be used.
- Given all the ideas on making use of the data, build a structure on where to store the "widgets" and tools that will leverage the data for ops/troubleshooting.
Idea: Rather than do a dictionary per device type, we can create a dictionary per OSI layer to make it more cross functional. Example: layer2={vlans: all vlans, vlan names, etc., vtp: 'enabled/disabled', 'vtp_domain':'test'} This actually would be a dictionary of dictionaries too, but think it would streamline things.