Hierarchically Applied key:value config store
Allowing for a system level JSON object/property on each device that applies hierarchically and with more specific key:value pairs overriding less specific (higher in the tree) ones
The simplest use case is that of NTP or DNS server settings. You'd set a DNS/NTP Key:Value pair at the building top level building of say {"DNS1": "1.1.1.1"} So all devices in those sub buildings, rooms, and racks would have automatically have that value applied to them (and that info could be queired via the API). But if you edit a say a specific room such as the LAB room that needs to use a different DNS server of 2.2.2.2. You would edit the room object and update the key:value pair to be {"DNS1": "2.2.2.2"}. Now Device42 would automatically compute that any devices apart of that room should have this new more specific key:value pair because it's lower in the hierarchy.
Please sign in to leave a comment.
Comments
0 comments