With the announcements on NX-OS APIs, Application Centric infrastructure APIs, python scripting support, SDN, open source projects OpenStack, OpenDaylight, and Puppet, I have opened an account at codecademy.com and will start with Python and Java. I see many late nights in my future. This stubborn old networker is finally onboard.
Apps, apps and more apps, is your company experiencing a proliferation of apps? Cisco certainly is. We are moving out of the experimental stage of app development and shifting toward measuring ‘repetitive usage’ as one of the main gauges for on-going support and improvements.
I have worked in IT since 1995 and never learned programming. Sure, I can do a little HTML, and years ago, I learned just enough Perl to configure MRTG, but I have never written a program. The good old CLI has kept me very busy and brought home the bacon.
Therefore, I have opened an account at codecademy.com. I will start with Python and Java. I see many late nights in my future.
I have thought about learning code, but I could never think of an app I wanted to write. Now Cisco is bringing together networking and programming. Cisco is not only making APIs available, Cisco is contributing code to the open source community. In fact, Cisco has created a Data Center repository, a Nexus 9000 community, and a general Cisco Systems repository on GitHub.
Cisco has recently overhauled the developer program and its content. The new DevNet website is filled with developer information on products such as AVC, Collaboration, UCS, CTI, Energywise, FlexPod, UCS Microsoft Manager, Jabber, onePK, XNC, Telepresence.
Cisco is bringing the networking and programing worlds together and this stubborn old networker is finally onboard.
Bill Carter is a Senior Network Engineer with more than 18 years of experience. He works for Sentinel Technologies and specializes in next-generation data center, campus and WAN network services.
Since they graced the covers of The Saturday Evening Post, the illustrations of Norman Rockwell and J.C. Leyendecker have created many of the Christmas holiday season’s de facto images. For many families, the reality of their Christmas celebration doesn’t match the picture-perfect, however. That’s especially true when the family member with the strongest belief in Santa has pressing questions like “how will Santa find me if the hospital has no chimney?”
The good news is that as he readies for Christmas, Santa is taking extra time to visit with children who are hospitalized this season. Instead of just making a quick stop on his whirlwind worldwide delivery route, he’s checking in with some of these very special children from his communications headquarters at the North Pole. Not content to have one of his shopping mall stand-ins do the work, he has personal face-to-face videoconferences with kids who can’t leave the hospital. Nationwide Children’s Hospital in Columbus, Ohio, posted a great video of Santa’s visit from earlier this week.
Connected Santa is a collaboration in which volunteer elves visit hospitals to help make the connection between children and Santa. Using Cisco TelePresence and Jabber technology, the elves conference a child with Santa so they can have the ever-important conversation about good, bad, and wish lists.
The other week I attended the “Software Defined Networking 2013” conference in London. This is a UK-based event for the discussion of SDN, OpenFlow and Network Virtualisation Solutions from a strategic perspective. There were quite a few interesting perspective s I picked up at this conference. In particular, the conference for me reinforced the potential of SDN – but if you apply it to the wrong problem, you may not get the return you hope for!
Top of mind for me, then, coming out of this conference was a demo of “What SDN Can Do For You” from one of our competitors. At best, the phrase “using a sledge hammer to crack a nut” comes to mind.
The demo came from our friends in Palo Alto, who once (boldly but incorrectly!) predicted that “Cisco UCS would be dead a year after launch”. They gave a SDN-focused demo that, when I “peeled back the onion”, didn’t demonstrate a compelling SDN use case. Rather, it convinced me that if you have this particular problem as illustrated in their demo, you don’t need SDN: you need a new vendor!