Re: [babel] Example configuration

[Mahesh Jethanandani <[e-mail]>]

Hi Juliusz,

> On Aug 8, 2019, at 3:15 PM, Juliusz Chroboczek <[e-mail]> wrote:
> 
>> In the second example, the operator will define a babel-link-properties-obj,
>> call it “radio” or “wireless” or anything they want, and within that object set
>> the babel-interface-metric-algorithm (because it a mandatory parameter), and
>> set the babel-split-horizon to false. They will then associate “radio” object
>> with eth1 interface.
> 
> Can the UI simulate the babel-link-properties-obj without it being part of
> the model?

Before I answer that question, let me know if the following answers help. If they do not, I am afraid that we will need a whiteboard discussion on management interface and the role YANG plays in it.

> 
> I.e. the operator defines a set of values called "radio", this set only
> exists within the UI.  

“radio” in my example is what you call UIs, just like “wireless”. Therefore when you say “set of values called “radio””, I read it as set of link properties that you want to club together and associate with a name, and that name is “radio". Is that correct?

> The operator then applies "radio" to a number of
> interfaces, and the frontend applies the individual values contained in
> the "radio" dictionary to each of those interfaces.


But that is exactly what the new babel-link-properties-obj allows you to do. It allows you to define any number of babel-link-properties-obj, and name them whatever you want, e.g. “radio”, “wired”, “wireless” etc, or what you call “UI". In each of the babel-link-properties-obj you set the properties you want, e.g. split horizon, rtt, etc.  As a final step you associate any of the defined UI with any number of interfaces. When you associate the given UI with an interface, all the link properties defined as part of that UI are then applied on the interface.

Did that answer your question, or confuse you even more?

> 
> Or does YANG require that the UI reflect the model?

> 
> -- Juliusz

Mahesh Jethanandani
[e-mail]