Network Automation Ninja at DT / TeraStream. I like YANG, Snabbswitch and Python. OpenConfig representative. Author of NIPAP, vrnetlab etc. polyglot wannabe.
Oct 5, 2021 • 24 tweets • 5 min read
I'd like to tell you about Acton, a programming language that I've been part of developing over the last couple of years.
"What? A new language? But why?"
I think you'll like it, so I'll try to explain... 🧵
The killer feature of Acton is that it provides for a distributed persistent programming environment. AFAIK, the way Acton does this is unique and a world first. I will get to details of that, but first an introduction to the Acton language in general.
Mar 14, 2019 • 10 tweets • 5 min read
@burneeed Our work predates gNMI and gNMI doesn't solve anything - it's just different. We prefer NETCONF, which is a standard, over gNMI, which is not. From a technical point of view there is nothing really wrong with gRPC although it is lacking some of NETCONF features.
@burneeed If you are the Goog and run gRPC on N million computers then you want the same stack on your network gear. Makes sense, I get that. If you are Facebook you want Thrift and if you are Microsoft you want Bond. NIH seems to be strong with these companies ;)
Dec 21, 2018 • 4 tweets • 5 min read
@gp_ifconfig@dbarrosop@kirkbyers@adainese If everything has a uniform interface, like NETCONF, then it is trivial to build a generic CLI rendered from the YANG models. Juniper took this approach early on, thanks @philatjuniper. Others did not which is why it's a tad messy now *looking at you, XR*
@gp_ifconfig@dbarrosop@kirkbyers@adainese@philatjuniper this can be cisco style or junos style or some other style. The operations and behavior of the CLI is orthogonal to the data (config and operational state) that it operates on. Imagine configuring XR via NETCONF through JUNOS style CLI or vice versa.
