You slice and dice your files in a git repo like a pro and accidentally commit a binary file. It happened to you as well, don’t pretend it didn’t.
Sooner or later you recognizes this file shouldn’t be there, it is clogging your git repo for no reason. OK, you delete the file and commit. But the repo size doesn’t get any smaller. Hm…
gnmic was the first opensource project that I’ve been part of that got widely adopted. As the maintainers of a public project, Karim and I were wondering when would we get the first external contribution.
To our surprise, the very first external contribution laid out the foundation to one of the most exciting features of
gnmic - YANG-Completions.
We were pleasantly surprised by the way community appreciated gNMIc release. Thank you 🙏! That solidifies the fact that a well-formed, documented and easy to use gNMI tool was needed.
Now with gNMIc available to everybody its easy like never before to test gNMI implementation of different routing OSes. And in this post we will get our hands on Arista vEOS.
Despite the fact that gNMI is defacto the go-to interface for a model-driven telemetry collection, we, as a community, had no gNMI tool that was easy to install, pleasure to use, documented and pre-built for common platforms. Until now.
I am excited to announce the public release of
gnmic - a CLI client and a collector that talks gNMI to your devices.
If you pick a random NetEng and ask them if they love NETCONF they would likely say “Nah”. The
hate-hate love-hate kind of relationship with NETCONF mostly roots in its XML layer that one can’t swap out. But if we set the XML-related challenges aside, it will become clear that NETCONF is a very well designed management interface with lots of capabilities.
In this topic we will touch on the NETCONF’s subtree filtering capabilities.