Hi all,
We're looking to have a service in which service instances will be created under a list nested on another list.
That is to say, that we're going to have a list with some common attributes, which will contain no service point.
This list will also contain another list, which in turn will include a service point.
Below you can see a simplified representation:
list nested {
key name;
leaf name {
tailf:info "upper layer";
tailf:cli-allow-range;
type string;
}
leaf dummy-upper {
type string;
}
list nested-service {
min-elements 1;
max-elements 2;
key name;
leaf name {
tailf:info "nested service instance";
tailf:cli-allow-range;
type string;
}
uses ncs:service-data;
ncs:servicepoint nested-servicepoint;
leaf dummy-nested {
type string;
}
}
}
The idea is to be able to trigger the deployment of only one of the instances of the nested list, rather then all of them (as in the case where the service point was located on the top-level list.
I tested the basic idea and it seems to be working as we would have expected, but my question is whether there are any caveats in such design?
Usually we have a service point under a list which always exist, while in this case, the service point is under a list which only exists when we create an entry of the upper layer list.
Any issues you can see for such architecture?
Thanks,
Yftach
