When deploying network services on my devices where the service is configured identically for each device (for example, list of DNS servers for my devices to use), I can either model my services so that I end up creating an individual service instance for each device, which would get modeled like this:
module dns-service {
...
augment "/ncs:services" {
list dns {
key hostname;
leaf hostname {
tailf:info "Single device to apply this DNS profile to";
type leafref {
path "/ncs:devices/ncs:device/ncs:name";
}
}
leaf-list dns-server-ips {
type inet:ip-address;
}
}
}
}
Or, I can create a single instance and apply it to the whole network (or subsets of devices on the network), like this:
module dns-service {
...
augment "/ncs:services" {
list dns {
key profile-name;
leaf profile-name {
tailf:info "Name of this DNS profile";
type string;
}
list devices {
leaf hostname {
tailf:info "All devices to apply this DNS profile to";
type leafref {
path "/ncs:devices/ncs:device/ncs:name";
}
}
}
leaf-list dns-server-ips {
type inet:ip-address;
}
}
}
}
The second way let's me apply mass changes across the network very easily. If I want to add a third DNS server into my network, it's a single set and commit on a single service. If I want to have certain devices on the network have different DNS profiles, I just create another service instance and move those devices from the device list in the old service instance to the device list in the new one.
Is there any downside to this second method over the first?
