On Mon, Oct 6, 2014 at 8:01 AM, Alia Atlas <[email protected]> wrote:
> On Mon, Oct 6, 2014 at 9:32 AM, Jeffrey Haas <[email protected]> wrote: > >> On Fri, Oct 03, 2014 at 05:43:27PM -0400, Alia Atlas wrote: >> > Now - if we have to decide that the CLI always wins, that is one option. >> > I, personally, would be quite opposed to the idea that I2RS would always >> > win. That does not give recovery mechanisms to the operators when and >> > if something goes wrong. >> >> So, what is your proposal to allow CLI/local config to win over ephemeral >> state? If not something comparable to "option 4", what then? >> > > Jeff, > > It's a good question. I have been sweeping it under > "implementation-specific" > since it is up to an implementation to decide what collides. If we were > talking about > vendor-specific CLI vs. YANG models for I2RS, how would it work? At the > end of > the day, there has to be understanding of what internally is impacted. > > If an I2RS client needs to monitor system state, local config changes, and also know the proprietary CLI in order to function, it will be too complicated to implement. If the CLI or local config has disabled I2RS for some or all clients, then the requests will get rejected by the agent. Proprietary data models and CLI should be out of scope. I can picture different abstractions or subsets being exposed for I2RS > rather than > CLI or NetConf-for-config. I do go more towards Russ's idea of I2RS as a > routing > protocol that cooperates with the other routing protocols rather than just > another name > for a management protocol. > I was surprised at the interim that every config=true schema node could apply to running config or ephemeral data, and it is always an operator decision as to which instances go in which datastore. This seems like a vendor decision first. I also figured I2RS would ignore local config and just attempt to inject routing state. It is up to the agent to resolve local config with ephemeral config to produce operational state. I can see local CLI disabling I2RS, but not competing with it to insert data, so I don't understand the "CLI wins over I2RS" use-case. > Regards, > Alia > > >> -- Jeff >> > > Andy
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
