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.
Automation Is as Good as the Data Models is a chapter’s name in the great book titled “Network Programmability With YANG”. These days you won’t bedazzle anyone by just providing the set of YANG models for the flagship network products. The models alone, albeit a great step forward, do not guarantee that programmability will start flourish.
The automation tools leveraging YANG is often a missing link and in this post I am talking about the Nokia YANG tree and Path Browser tools which help both our internal automation squad and our customers to be more effective working with our YANG models.
We can praise YANG as long as we want, but for an end user YANG is useful as the tooling around it and the applications leveraging it. Ask yourself, as a user of any kind of NETCONF/YANG application what was the last time you looked at a *.yang file content and found something that was needed to consume that application?
In a user role I personally never look at a YANG source, though, I look at the tree or HTML representation of YANG all the time; Thats is the YANG human interface for me.
And even in these human friendly formats you can’t find all the answers; for example, looking at the YANG tree, how do you get the XML data sample of a given leaf? Thats what we will discover in this post.
I wrote about the Yang Explorer in a docker quite some time ago, Yang Explorer was v0.6 at that time. Back then the motivation to create a docker image was pretty simple – installation was a pain in v0.6, it is still a pain, but the official version bumped to 0.8(beta).
So I decided to re-build an image, now using Alpine Linux as a base image to reduce the size.
