Editor’s Note: This is a guest post by two Wireless Networking Group interns, Nonie Grewal and Nivedita Jagdale, to capture their thoughts on the Connected Mobile Experiences Hackathon that they helped plan and execute.
June 29th marked the start of the Connected Mobile Experiences (CMX) Hackathon in the Cisco San Jose campus. CMX, powered by the Mobility Services Engine, provides a unique way of providing personalized real time location services over Wi-Fi. CMX aims to increase customer-oriented and operational efficiencies through analytics and personalized mobile services. The contestants at the hackathon were invited to help build prototypes that could help complement these goals, focusing on enhancing user connectivity and visibility.
As summer college interns volunteering at the event, we walked into the Deep Space Nine room where the hackathon was held, to find clusters of intense developers at each table. With each passing minute, we felt the name “Deep Space” seemed apt for the cause it was hosting -- deep thought and real coding! Read More »
Tags: API, Cisco, cmx, Connected, connected mobile, hack, hackathon, mobile experience, mobile experiences, network, networking, REST, rest api, wireless
Network programmability means democracy, means freedom, freedom to program across all layers and entities, software or hardware – depending on your needs. Is SDN required to have network programmability? Not at all. Does the SDN architecture leverage network programmability? Yes, of course. So, why do many people equate network programmability and SDN? Read More »
Tags: API, Cisco ONE, Cisco ONE Architecture, onePK, OpenFlow, programmability, SDN, SDN architecture
I admit it. I’ve grown weary of the debate about whether SDN includes network programmability or whether or not SDN can only be accomplished through NfV, or the relative merits of control plane / dataplane separation. I will leave those debates to others more focused on the technology itself. Personally, I have been more fascinated with what I see as the new business opportunities emerging around SDN.
Certainly there is a raft of opportunities for start-up companies in the controller space or in the virtualization of various networking functions. Many innovative new companies are re-examining existing network functions within the SDN paradigm; that will lead to some potentially new and useful approaches that may be cheaper/easier/faster than current designs. No doubt many customers will see value in these new ways of doing things, and everybody will benefit.
But that’s not what I find fascinating about SDN. What I am starting to see are ideas that are completely out of the box, and would likely not be thought of by typical network technologists working alone. Let me discuss a few categories of things I have seen possible with the emerging technologies.
The Network as a Compute Resource
It turns out Read More »
Tags: API, cloud, NFV, ONE, onePK, opendaylight, OpenFlow, SDN
The announcement today of OpenDaylight is big news. Industry leading companies are partnering via Open Source to serve an emerging set of market needs:
- Operators: want affordable real-time orchestration and operation of integrated virtual compute, application, and network.
- Application Developers: want a single simple interface to the network. Underlying details such as “router”, or “switch”, or “topology” can be a distraction they desire to abstract and simplify away.
- Equipment Vendors: want a stable forum to interwork a plethora of Application interfaces with a plethora of nascent Network Device programmatic interfaces.
OpenDaylight members understand Read More »
Tags: API, Daylight, I2RS, intent, open source, opendaylight, OpenFlow, orchestration, SDN, SDN controller, virtualization
Back in May 2012 Mike Fratto predicted in his blog that SDN will be “Reborn in Network Management”. There is a lot of truth to his statement. The words “software defined” in “Software Defined Networking (SDN)” inspired people to rethink the overall control plane architecture of the network making the case for infrastructure software that complements software already embedded in virtual and physical devices, (e.g., the software and protocols running in and between network elements).
We are evolving our treatment of the network. What once was a discrete set of loosely coupled devices will now be interacted with as a system. To get there means the network must be represented by an overall system model. Classic network management functions become an integral part of the infrastructure software, and will spawn their own management requirements. SDN makes network management a first class citizen. Effectively we’re past the time when network management was an afterthought, or when network management was an operational silo. The coming integration of network management into the larger network software domain means infrastructure managers will not only manage and operate, but also actively contribute to the overall business proposition of the IT infrastructure. Read More »
Tags: API, Network programmability, onePK, OpenFlow, SDN