On Fri, Aug 28, 2015 at 11:31 AM, Alexander Clemm (alex) <[email protected]> wrote:
> > > -----Original Message----- > From: netmod [mailto:[email protected]] On Behalf Of Ladislav Lhotka > Sent: Friday, August 28, 2015 4:31 AM > To: Martin Bjorklund <[email protected]>; [email protected] > Cc: [email protected] > Subject: Re: [netmod] logical systems model > > > ..... > <snip> > > NACM, as well as all other modules we have, is based on the assumption of > a single managed device. > > I think it is a typical trend that what once was a single instance becomes > an array. If we did ietf-routing 20 years ago, there would probably be no > routing-instance list. > > So I think it is a real problem that we can't migrate from a container to > a list and reuse the container's data model. Groupings might help somewhat > but they are still not fully reusable, if, for example, they contain > absolute references. > > Lada > </snip> > > One comment, if you forgive the pitch, but this problem / use case is by > the way exactly one of the reasons for mounting, which allows you to > introduce and impose an additional structure on top of an existing > structure, and "insert" the existing structure into it. Augmentations etc > can only add below the hierarchy, there is no way we can put a new > container or list or whatever on top of an existing structure (without > replicating the existing structure in a duplicate model), but peer-mount > lets you do that. One use case used in Open Daylight involves organizing/ > inserting device-level information into a network inventory, which is > basically imposed "on top". > > I thing YANG Mount would be the best way to solve this problem. It provides a standard way to do "chroot" and it is flexible. The mechanics of a "datastore within a datastore" are the same and independent of the source of the data (local, remote, virtual, etc.) Andy
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
