Open bevolz opened 6 years ago
zihaohe123
commented
6 years ago I see your point here. Probably 'inherit-option-set' is not necessary, since that two different levels use one 'option-set-id' is equal to 'inherit-option-set' being 'true'. In this model, I think just like Kea, instances of options at a lower level will be given priority. If any instances are not specified at lower level, we will then search those instances at higher levels.
bevolz
commented
6 years ago Yes, sounds fine.
The option sets should be assumed to be hierarchical starting with the most specific (i.e., client) and going to less specific (client class, pool, …, server-wide).
From: Zihao He notifications@github.com Reply-To: dhcwg/yang reply@reply.github.com Date: Tuesday, January 30, 2018 at 5:56 AM To: dhcwg/yang yang@noreply.github.com Cc: Bernie Volz volz@cisco.com, Author author@noreply.github.com Subject: Re: [dhcwg/yang] inherit-option-set (#17)
I see your point here. Probably 'inherit-option-set' is not necessary, since that two different levels use one 'option-set-id' is equal to 'inherit-option-set' being 'true'. In this model, I think just like Kea, instances of options at a lower level will be given priority. If any instances are not specified at lower level, we will then search those instances at higher levels.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/dhcwg/yang/issues/17#issuecomment-361557642, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABm3YXH7QYkUW3iYPoPVgmd-A84enFwaks5tPvVxgaJpZM4RwxBc.
Perhaps this is a Kea thing, but I'm not sure I understand this and how it applies?
The description isn't that useful: leaf inherit-option-set { type boolean; mandatory true; description "indicate whether to inherit the configuration from higher level"; }
If false, it means that "higher levels" aren't used?
For our server, we always use the full set of options but start at the lowest (client specific) level. When searching for an option, we stop when searching the levels once an instance is found. The only issue with this model is that you can't easily "drop" an option that is configured at a higher level -- perhaps that is what this intends to solve. But it is seems to course (all or nothing).