This group is locked. No changes can be made to the group while it is locked.
[mdsal-dev] Is it possible to add a default variable in yang binding objects generated
On 30/08/17 21:49, Vikram Darsi wrote:
Hi TeamHello Vikram,
Is there a way to add a variable called “message-id” in all theThere is a way, but generating such a field really does not buy you
anything, as it still needs to propagate through the system, and that
requires it having a modeling underpinning.
* *This goes against the architectural requirement of loose coupling
between producers and consumers. Consumers should not care where the
data is coming from, they just need to act on the data -- otherwise the
system will have variances based on undocumented decisions (i.e. 'if
this data was written by foo, do X, if by bar, do Y'), which makes it
non-modular, as when baz is introduced, the consumer needs to be
revisited and taught to 'if by baz, do Z'.
Furthermore you need to deal with state compression and persistence --
essentially answering questions about semantics of that metadata, how it
state-compresses and what the lifecycle is:
- does this mean each subtree has a persistent 'originator' tag?
- how do tags work in face of subtree edits?
- etc. etc.
So, we wanted to follow the NETCONF RPC “message-id” concept to identifyYeah, but as you noted this is a transient RPC concept, where there is a
known 1:1 relationship between the requesting entity and the entity
processing the request. There is no such relationship in the data store.