This weekend’s interesting link is to a post by Jeremy Schulman, formerly Director of Network Automation with Juniper Networks, but now the founder of Schprokits, a startup which aims to generate automation framework tools for network professionals that are of a similar standard to those achieved in the DevOps community. Though Schprokits is operating in stealth mode currently, Jeremy is publishing blog posts relating to his mission.
I first met Jeremy at Networking Field Day 4, then saw him again at Networking Field Day 5, each time presenting Juniper automation solutions to us. I’ve stayed in touch with Jeremy since then and he has offered many wise words and honest guidance to me with regard to automation. Thus I find the conversations I have with him invigorating, and while he willingly shares his insights and vision for the future of NetOps, he is also a good listener and willing to consider with humility any contrary positions, different ideas, or any other feedback. That’s pretty cool, all things considered.
And so, the link.
Recently I’ve been writing some automation code for Atlassian’s JIRA project management / bug tracking product. Think of JIRA as a generic AGILE-aware tool that can provide everything from project tracking all the way down to task tracking, trouble ticketing and so on.
The task I had set myself was to automatically create a ticket of a particular problem type (one that arises a lot) so that I could save a few minutes every time by not having to do so manually. That aim quickly became something that could plug into another script which could feed identified problems into my script so that it could generate the problem ticket on behalf of that tool.
What I learned was an interesting lesson in refactoring as I tried to optimize my code.
I had a chance last week to speak with a couple of folks at Solarwinds about the release of their Network Performance Monitor (NPM) 11 product, which is being announced today. I don’t cover network management products too often, but Solarwinds is adding something interesting with this release, and I think it deserves a mention.
Another day, another issue with an automation script.
Today’s task was to grab the configuration file from an A10 Thunder load balancer. I don’t want to use the GUI, and while I could – in theory – use ssh and expect to scrape the CLI, it’s not the way I’m trying to work now, presumably because I’m a masochist.
It all went smoothly, right?
I’ve noticed – and it’s really no surprise – that I get fewer people visiting this bastion of technical omnibabble on the weekends. I get it, you’re busy and have real lives; and to that end I rarely publish posts on the weekends either. In a fit of alcohol-induced something or other, however, it struck me that this is a missed opportunity to make some special posts just for you lovely weekend visitors – a “Secret Sunday” club. Heck, maybe people want posts on the weekend, right?
Ok, so let’s give this a shot. I’ll do my best to post something on Sundays, and if you read if on the day it’s posted, please know that it was just for you, my special Sunday readers, who I value just as much as the poor suckers who only check out this site during the work week.
The trick with the Sunday posts though is that they’ll be short and sweet. Weekday readers may at this point be wishing for a week of Sundays, but they’ll be disappointed. I am well known for my inability to express an idea in less than 1000 words, and nothing will change there. Secret Sunday posts will be shorter. Promise!