On Mon, Jan 23, 2017 at 1:19 PM, Martin Bjorklund <[email protected]> wrote:
> Robert Varga <[email protected]> wrote: > > On 01/23/2017 09:26 PM, Martin Bjorklund wrote: > > >> I'm pulling your questions to the top of this email. > > >> > > >> > > >> > > >> Question 1: Ok. Just to make sure I understand this correctly - these > > >> topology models are intended to be I2RS-specific, and they cannot be > used > > >> for any other purpose. If anyone needs a general topology model > outside of > > >> the I2RS protocol, they will have to design their own model. Is this > > >> correct? > > >> > > >> > > >> > > >> Response 1: Not really. > > > Ok, so are you saying that the models are in fact generic, and can be > > > used outside of I2RS? I.e., they *can* be used with the normal > > > configuration datastores? > > > > > > > From implementation experience, yes, they can be used for storing > > configuration. OpenDaylight uses (an ancient predecessor of) > > yang-network-topo to store configure details about devices in its > > managed networks. > > Robert, this sub-thread started with Susan's statement: > > 1) I2RS Data models do not utilize the configuration data store, > > i.e., despite the fact that the data model is config true, it cannot > be edited via running etc in NETCONF (or normal edit in RESTCONF). > > My comment on this was that *if* this is true, it should be noted in > the document. At this point, I am not sure if it is true or not. > > Agreed. But a larger issue is the balkanization of YANG. To every YANG reader, the YANG data-def-stmts look exactly like those that would be interpreted as configuration and state data nodes. I little note that says "This is not regular YANG that is intended for NETCONF or RESTCONF servers" is not really a solution. RFC 7950 says YANG is for NETCONF, which is extra confusing. > /martin > > Andy > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs >
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
