Memorize — or Think?
I have several friends with either photographic, or near photographic, memories. For instance, I work with someone (on the philosophical side of my life) who is just astounding in this respect. If you walk into his office and ask about some concept you’ve just run across, no matter how esoteric, he can give you a rundown of every major book in the field covering the topic, important articles from several journals, and even book chapters that are germane and important. I’ve actually had him point me to the text of a footnote when I asked about a specific concept.
It seems, to me, that the networking industry often focuses on this sort of thing. Quick, can you name the types of line cards available for the Plutobarb CNX1000, how many of each you can put in the chassis, what the backplane speed is, and what the command is to configure OSPF type 3 filters on Tuesdays between three and four o’clock? When we hit this sort of question, and can’t answer it, people look at us like we’re silly or something.
Right?
I know, because I’ve been there. I’ve had people ask me the strangest questions in interviews, such as Continue reading
Beyond SDN, Now What?
When we started Plexxi almost 5 years ago, SDN was about to become a “thing.” The topic of advancing networking soon went from obscure to being coined with a name to the full fledge hay day of acquisition euphoria and main stream press. It’s fair to say we have followed the proverbial hype curve quite predictably, and some might say we are now well into the trough of disillusionment. Which leaves some asking, now what?
I’m probably not the only one that feels that we, as an industry, should have moved past the point of showing up at a conference with a “What is SDN” slide. That is, once we move beyond trying to define SDN, we see that perhaps that is the least important thing to do.
Instead of trying to define SDN, I like to try to understand why we’re even discussing it. To me, this entire journey we’ve been on has always been an indication of user discontent. By user, I don’t just mean network engineers and operators, but also the constituents that rely on the network (like the other IT stack components and their respective operators/owners), and ultimately the users that rely on the applications Continue reading
Some Thoughts on the Open Internet
I’m sure we’ve all heard about "the Open Internet." The expression builds upon a rich pedigree of term "open" in various contexts. We seem to have developed this connotation that "open" is some positive attribute, and when we use the expression of the "Open Internet" it seems that we are lauding it in some way. But in what way? So let’s ask the question: What does the "Open Internet" mean?Automation Testing: Tools and Concepts
One of the key tenets of DevOps is automation, or more specifically, “Infrastructure as Code.” That means your system configuration is expressed as a series of scripts that can be executed by your configuration management software, repeatedly, across multiple machines.
Treating infrastructure as code has many benefits, including the abilities to control when and how changes are applied, to apply changes quickly and to manage your changes with version control. Most importantly, because it’s code, you can test it.
If you’ve been maintaining computer systems for any amount of time, you’ve probably accidentally broken something important when you were making a configuration change; either the change didn’t work as you expected or you typed the wrong command. What if you had been able to write your changes ahead of time and test them before you applied them to production? Infrastructure as Code enables you to do just that.
Software developers have been testing their code for a long time, and we can leverage their experience and knowledge and apply it to Infrastructure as Code. So, just as there are a series of testing tools available for software engineers, automation engineers can also draw from a collection of tools and build themselves a complete end-to-end Continue reading
HP Spearheads Open Source Network OS Initiative
Linux-based OpenSwitch NOS is designed to provide data center networks with more flexibility.Software-Defined IXP with Laurent Vanbever on Software Gone Wild
A while ago I started discussing the intricate technical details of fibbing (an ingenious way of implementing traffic engineering with traditional OSPF) with Laurent Vanbever and other members of his group, and we decided to record a podcast on this topic.
Things never go as planned in a live chat, and we finished talking about another one of his projects – software defined Internet exchange point (SDX), the topic of Episode 41 of Software Gone Wild.
Read more ...SDN 101: OpenFlow, HP Virtual Routers and GNS3
In a previous blog entry, I showed you how to integrate Mininet and GNS3 (SDN 101: Mininet (OpenFlow) and GNS3) for learning SDN andSoftware defined WAN (SD-WAN) is really about Intelligence ..
Lets admit that most of us in the networking domain know as much about SD-WAN as an average 6th grader on fluid mechanics — which is to say pretty much nothing. We take it as something much grander and exotic than what it really is and are obviously surrounded by friends and well-wishers who wink conspiratorially that they “know it all” and consider themselves on an intellectual high ground to educate us on matters of this rich and riveting biological social interaction. Like most others in that tender and impressionable age, i did get swayed by what i heard and its only later that i was able to sort things out in my head, till it all became somewhat clear.
The proverbial clock’s wound backwards and i experience that feeling of deja-vu each time i read an article on SD-WAN that either extols its virtues or vilifies it as something that has always existed and is being speciously served on a platter dressed up as something that it is not. And like the big boys then, there are men who-know-it-all, who have already written SD-WAN off as something that has always existed and really presents nothing new here. Clearly, i disagree with that view.
Software defined WAN (SD-WAN) is really about Intelligence ..
Lets admit that most of us in the networking domain know as much about SD-WAN as an average 6th grader on sex — which is to say pretty much nothing. We take it as something much grander and exotic than what it really is and are obviously surrounded by friends and well-wishers who wink conspiratorially that they “know it all” and consider themselves on an intellectual high ground to educate us on matters of this rich and riveting biological social interaction. Like most others in that tender and impressionable age, i did get swayed by what i heard and its only later that i was able to sort things out in my head, till it all became somewhat clear — surely i am nowhere close to Mr. Hefner who has, and am willing to wager large amounts here, gamed it entirely and has acquired a skill that only a few of us get blessed with.
The proverbial clock’s wound backwards and i experience that feeling of deja-vu each time i read an article on SD-WAN that either extols its virtues or vilifies it as something that has always existed and is being speciously served on a platter dressed up as something that it is not.
I presume, perhaps a trifle rashly, that you are already Continue reading