We are living in arguably the most exciting time in human history, and I’m mesmerized by how fast our world is evolving thanks to brilliant technologies and the sheer volume of inanimate objects that are connecting to the internet on a daily basis, forming the internet of everything (IoE).
As much as it seems everything is digital these days, our world is almost entirely analog. However, digital technology (and its massive potential to revolutionize our world) is trending toward mainstream popularity, in spite of traditionally being relegated to the minds of the ‘geeky’ few. The reason for this trend is simpler than it might initially appear and it’s the topic of this post. Read More »
Tags: #ciscochampion, Dave Evans, DesignTheory, digital technology, guest blogger, healthcare, IBM, IoE, Isaac Naor, NASA, technology, UI, user interface, UX
Complexity and Cost Comparison: Cisco UCS vs. IBM Flex System is report recently published by Principled Technologies.
They evaluated both the technologies and costs of each solution and found a UCS solution is both less expensive to deploy and less complex to manage than an IBM Flex System.
Off all the ways Principled Technologies shows how UCS is a superior solution, I wanted to touch on just one: highly available and scalable management. A UCS management domain consists of a pair of Fabric Interconnects and supports up to 160 blade and/or rack servers. In contrast, IBM is limited to 54 blade servers plus a non-redundant Flex System Manager node. Quoting from the paper:
Because IBM Flex System Manager nodes do not failover automatically like the Cisco UCS solution, administrators must manually connect to a backup node and bring it online. Each target system has an OS agent that remains registered to the original FSM node and does not recognize the new FSM. Admins must manually unregister each of these agents from the failed node and then register the new FSM node. [page 7]
Read the full report to learn the many additional ways which UCS is shown to be superior solution and why Cisco has leapt ahead of IBM and is now the #2 blade server vendor worldwide1
Would like to learn more about how Cisco is changing the economics of the datacenter, I would encourage you to review this presentation on SlideShare or my previous series of blog posts, Yes, Cisco UCS servers are that good.
- Source: IDC Worldwide Quarterly Server Tracker, Q1 2013 Revenue Share, May 2013
Tags: 2208XP, 6248UP, 6296UP, B200 M3, blade server, capex, Cisco, CMM, CN4093, Fabric Interconnect, fex, Flex System, FSM, G8264R, IBM, patterns, Principled Technologies, rack server, ROI, service profile, tco, UCS, UCS Manager, x240
As we continue to expand on the conversation of the Cisco Open Network Environment (Cisco ONE), this week provides yet another educational opportunity (Register here) to discuss a topic that has become some what top of mind to customers, partners and even investors alike. This is the topic of open source in networked environments. While Cisco has always been known for open standards, it has now stepped up into the open source conversation in a fairly big way over the couple of years with its contributions to both OpenStack and the more recent OpenDaylight project under the Linux foundation.
Read More »
Tags: Cisco ONE, Dan Frye, IBM, Jim Zemlin, Linux, Linux Foundation, Michael Enscu, open source, opendaylight, Shashi Kiran
This week kicked off with a trip to Boston and Red Hat Summit where Cisco is talking about our partnership with Red Hat on open source projects including OpenStack, and the Kernel-based Virtual Machine (KVM) hypervisor. I’m here to highlight some of our Nexus 1000V virtual networking innovations that involve Red Hat open source distributions of red Hat Enterprise Linux (RHEL), KVM and OpenStack.
As you probably know, Cisco started shipping the Nexus 1000V virtual switch for Microsoft Hyper-V this month (and it won a Best of TechEd Show award at Microsoft’s TechEd conference). But open source virtualization and cloud infrastructure platforms continue to be an important strategy for our entire data center portfolio here at Cisco. KVM will be the next hypervisor that we’ll ship our Nexus 1000V virtual switch on, and the rest of the Red Hat open source cloud infrastructure will be an important part of our open strategy, and that includes Red Hat Linux and their Red Hat OpenStack distribution.
Read More »
Tags: Cisco ONE, IBM, KVM, Linux, Microsoft Hyper-V, Nexus 1000v, opendaylight, OpenStack, Red Hat Summit
It’s great to see Cisco and many companies across the industry make a major change in the use of Open Source via the newly form project hosted by the Linux Foundation called OpenDaylight. This consortium is an industry-wide, open and transparent effort to catalyze innovation and accelerate an application ecosystem for software-defined networking. With all the partners involved we are working to not only further development and adoption of SDN but also to foster a new developer community. A consortium like this has been long overdue and it’s great to finally see it come to fruition.
We are incredibly pleased to partner with Arista, Big Switch Networks, Brocade, Citrix, Dell, Ericsson, Fujitsu, HP, IBM, Intel, Juniper Networks, Microsoft, NEC, Nuage Networks, PLUMgrid, RedHat and VMware on the Project. This is the largest effort to date to drive Software-Defined Networking across the industry and into new markets. While the initial goal is to build a common, industry backed SDN Platform, the broader objective is to give rise to an entire ecosystem of developers that can freely utilize the code, contribute to the project and commercialize the offerings. I further expect the ecosystem to expand into areas like tools and services.
Cisco has donated our core “Cisco ONE” controller code to the project and has officially open sourced the code under the Eclipse Public License. The community has come together around this code to form the architecture (see below) for the Open SDN Framework. Beyond donations of code, Project members are supporting the project via both financial investment and via developers we are committing to work full-time on the project overall. Donations from other members of the Project can be seen here and we expect this list to only grow.
As Open Source increasingly becomes a standard for customers and developers, we look at this as a new way to meet our customer needs and also help developers innovate in new ways without the barriers of vendor lock-in. Open Source is increasingly important for our customers and developers as well and as they evolve, we evolve. Cisco to date has supported Open Source through efforts such as OpenStack and now OpenDaylight and we look at Open Source as a critical pillar in our software strategy moving forward. By allowing developers to freely use these solutions we hope to enable a new developer ecosystem for software-defined networking and more. We are fully committed to enabling developers, both current and new, to deliver innovating applications and services that will help customers across the board realize the value of SDN faster than before.
The OpenDaylight architecture and code offering to date includes a modular southbound plugin architecture for multi-vendor environments. In addition, OpenDaylight offers an extensible northbound framework with both Java & REST APIs to ensure multiple developer skill-sets can build applications to the platform. We are also planning to build a onePK plugin for OpenDaylight to enable multiple users to drive network intelligence into their SDN applications. As you can see from below we will also be supporting key standards with this effort, including OpenFlow.
It’s important to note that you don’t launch a community; you build one. By investing in OpenDaylight we hope that our customers, partners and developers across multiple industries will now have the ability to build applications that frankly make the network easier to use and more automated. As an industry we are moving in a new direction and further up the stack and OpenDaylight offers new opportunities for application creation and monetization beyond the networking layer.
It’s a true rarity when you see both partners and competitors come together for the good of the community, and contribute code for the universal good of the customer. All OpenDaylight participants have committed to open source guidelines that include open communication, ethical and honest behavior, code and roadmap transparency and more. An Open Source project is only as successful as the community of developers and the level of code quality, and OpenDaylight’s Board of Directors (which includes multiple parties cross-industry) will be ensuring that partners, code contributors and project committers all abide by the same guidelines for the success of the project over the success of their own company’s offerings.
For more information, please see www.opendaylight.org. Code will be available for download soon, and we are looking for interested individuals for commitments across the board – from technical offerings to application development, and we welcome contributions from both individuals and other organizations. All ideas are welcome, and we look forward to multiple new innovative solutions coming from this.
Congratulations to all our partners and individuals who helped to make this happen, including the hard work done by the Linux Foundation. It’s truly an amazing accomplishment and we expect to see much more in the near future.
Tags: arista, big switch networks, Brocade, Cisco SDN Controller, citrix, dell, ericsson, Fujitsu, HP, IBM, Intel, juniper, Microsoft, NEC, Nuage, open source, opendaylight, PLUMgrid, RedHat, SDN, VMware