3 ms·
OpenConfig: Vendor-neutral, model-driven network management designed by users
- HstryrsrBttn 5y ago
- encryptluks2 5y agoLast update in the news appears to be 7 years old. I can't find any modern software using this. As much as it sucks, I think netplan and maybe netjsonconfig are much further along.
- unmole 5y ago> I can't find any modern software using this. You're looking in the wrong place. Virtually every networking vendor supports OpenConfig.
- encryptluks2 5y agoI want to believe you, but it appears to be primarily used by large expensive vendors. No OpenWrt support, no official Ansible modules... I am not seeing it.
- unmole 5y agoWell, yeah. OpenConfig is primarily driven by Google. So, only the networking vendors who want to sell to Google have any incentive to support it. As it happens, these vendors tend to be large and expensive.
- sigmonsays 5y agothere is a big distinction to be made here... netplan solves host network configuration where openconfig solves router network configuration, the latter being much more complicated.
- musicale 5y agoYes - and you can also configure servers to be routers (see quagga, bird, etc.) if you want all of that fun (?) complexity. Even some seemingly more basic networking functionality on Linux, such as static routing with iproute2, firewalling with iptables/ebtables°, traffic management with tc, switching/bridging with OvS, etc., can quickly become extremely complicated. °ufw is nice though if it can do what you want/need
- musicale 5y agoI like the idea of OpenConfig, but some challenges I have run into are that: 1. The models specify data formats in machine readable form, but the semantics are still specified in English. 2. In my experience, semantic complexity and variation across devices bubbles up to the application layer, effectively requiring custom code for each device (or at best each vendor.) 3. Many network devices do not implement OpenConfig. 4. In spite of abundant evidence to the contrary (including the above) it has been frustratingly hard to convince some people (and equipment vendors) I've worked with that YANG is not a panacea that enables network and device management software to automatically know how to configure and manage new devices. (For some reason protobufs/gNMI/gNOI didn't seem to inspire the same madness.)