Cisco OnePK VM in Parallels

Over the last couple of weeks, I've been bit by the "Automation Bug".  I want to automate everything.  Why?  Well, there are two reasons why I want to automate everything I can: Remove tedious, mundane, and repetitive tasks.  If I can do the same task over and over again, not only do I save time, but I remove any human errors from the equation. Abstract the complexities of the tasks at hand.  This is very useful when delegating the tasks to personnel who may not fully understand or know the intricacies of the steps. This week, I've started to learn about Cisco's OnePK software develop...

SDN Should Not Require Programming – Per Se

Provided as-is, with permission by Creative Commons 2.0, and courtesy of Libby Levi for
There has been a lot of controversy about how the network engineering profession will change in the future, thanks to SDN (Software Defined Networking).  Because network decisions will now be controlled by software, many think the network engineering profession will have to learn programming.  While this may be true in some cases, I do not believe it to be true in the majority of the cases. If you break down the acronym, it will say "Software-Defined" networking.  This means software that has previously been written to accomplish a specific task will be deployed on the network.  Do you need...

SDN is a Concept, Not a Technology

I was recently posed a question: "How does the networking industry train and build skills for tomorrow's SDN with today's engineers?". Personally, I think that is the wrong question.  SDN is not a skill that you learn.  SDN is not a class you can take.  SDN is certainly not a training path you can attend.  SDN is a concept, plain and simple.  It's the software and underlying technologies that you must train, understand, and build upon.  SDN, like Cloud, is born from the limitations of the current technology to keep up with the changes in other technologies and demands.  It is a mix of techn...

Interview of HP’s Saar Gillai on SDN

During HP Discover 2012, I've been asking various HP divisions on the plans HP has for an OpenFlow controller.  The reason?  For the last 18 months, I've noticed that every HP event mentions SDN and OpenFlow.  Why?  Just adding support for a technology is not a big deal.  One, maybe two announcements, and you are done.  Why so much talk about it?  Surely this means that HP has big plans for it. The answer I get back is, "What would you do with one today?".  Well, nothing, TODAY.  The enterprise doesn't really have a need for it yet.  But th...