Re: [c-nsp] ASR9K using XR 7
Saku Ytti <[email protected]>
| Newsgroups | gmane.network.nsp.cisco |
|---|---|
| Message-ID | <CAAeewD_UNWhbS=u4xb4UMRJgDwZ-ZU9nZ0hhUZ6GnkfLefCzHg@mail.gmail.com> |
On Fri, 30 Jul 2021 at 20:29, Nick Hilliard <[email protected]> wrote: > there are several reconfig / deconfig operations that can't be handled > on XR using a single commit, e.g. changing ISIS NET address, some > netflow stuff, etc. Deapplying and removing QoS policy in a single commit :). Opening tickets about these tactically feels frustrating when the vendor doesn't understand there is a strategic problem under the hood causing these. Some other vendors who simply cannot produce config without having models first don't have these commit time problems or they are orders of magnitude rarer events. Cisco keeps being confused about what does 'model driven' mean, the moment you talk about coverage of models and being model driven, you're confused what model driven means. Cisco doesn't even have real config infra, if QoS policy doesn't commit, that is QoS people problem, if tunnel config doesn't commit, that's tunnel team problem and so-forth. Instead of them consuming some internal config API, and having all commit problems be a config team problem. -- ++ytti _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/