Disaggregated, modular, mix and match, open, these are the sound bites of the emerging white box and open software ecosystems. Will they define the architectural thinking used throughout our information-driven world moving forward?
From the Open Compute Project in data center hardware to open source software such as Open Daylight and OpenStack, the principles of ‘don’t lock me in’ and ‘let me be in charge of components I need for my best-in-class solution’ are making a play for being the dominant drivers for solution designs in nearly every network and IT platform category.
Take Cavium’s just-announced XPliant family of terabit-scale Ethernet Data Center switches as a fresh example. Its Open Compute Project design foundation means, with OCP’s Switch Abstraction Interface (SAI) the switches can be used by any open networking software team to build functions that suit their needs without being held back by the underlying hardware’s processing architecture. And, with its Open Network Install Environment (ONIE), solution designers can decide whichever network OS best suits their needs.
In another closely related category, look at Ericsson’s Hyperscale Data Center System (HDS 8000) introduced at Mobile World Congress last week. To support an array of cloud-scale workloads, Ericsson determined it makes sense for the processor and memory elements in its HDS server ‘sleds’ (individual units) to be mixable in a manner customers decide are optimal for their needs. Each combination can be made available to the larger ‘pool’ of resources available and allocated as desired by the cloud management system in use. Each module is attached via an optical infrastructure to simplify storage and compute integration, again based on the workload’s needs.
Does this ultra-modular perspective mean the era of integrated product and solution deliveries is dead? Not completely. They will be less prominent in the long run but unlikely to go completely away. For example, HP delivers its Helion OpenStack cloud computing platform as a whole system offering for which it is accountable to its customers. It includes HP and open community components. Juniper delivers its OCX 1100 Open Networking Switch as a platform full of choices about the OS a customer chooses to use in its data center for which Juniper is accountable. It includes Juniper and open community components.
The increased role of open and modular thinking in solution deliveries is just an indication that the range of ingredients available to producers is increasing (these options were not possible 10 years ago) and the opportunity to bring them to customers in creative ways have expanded. In that sense, the line defining for whom a solution integrator works—a ‘whole system’ vendor (Cisco, Ericsson, HP); a professional services firm (Accenture, Tata); or an end customer (DT, Equinix, NTT)—is being drawn more flexibly today (and moving to the future) than was possible a decade ago. Each party can decide the amount of responsibility it thinks it should shoulder in delivering the end result. The range of options has increased.
Like many deeply rooted transitions, there are parts of this one that are sometimes messy and a bit fragile compared with the ‘certainty’ that integrated platform deliveries of the past have offered. However that fragility will likely subside in coming years as integrators of every type get more familiar with the open building blocks with which they are working, and the use cases they’re supporting put their real and natural pressure on where the boundaries of responsibility should lie for the solutions to be practical. The outcome will be a downshift in the unit cost of underlying hardware, an uptick in the amount of choice that solution integrators decide to use in their designs, and a rise in the value of the software in the solutions at every stage of deployments—from network nodes to server units to higher level applications—that support the services we decide we want to use.
That transition will undoubtedly have its jarring and its stellar moments and will take some time to occur. In the meantime as it unfolds, it’s worth paying close attention to the shifts being brought to market in line with that trajectory in offerings such as the Cavium and Ericsson solutions highlighted here.
Hi Friends, I have an ASR 1001(Cisco IOS XE Software, Version 03.16.01a.S/Cisco IOS Software Version 15.5(3)S1a).I checked it, but can't configure 'MPLS ldp', and no MPLS command under the interface. My question is which lowest release can ...
It is established that auto-upgrade should be disabled during an XR upgrade process. However, what is recommended for normal operations? I can see the advantage of having "auto-upgrade" in place so that any RMA or new LC's would/should be upgra...
Hi Everyone, I'd like to know what is most MPLS providers' SOP for their COS especially for Premium i.e. Voice. If you subscribed 10M Premium and exceed that amount, what happens? Assuming the the entire pipe purchased is 100Mb for argument sake and ...
TRAI Regulation on Inbound outbound calling in Domestic Call centres in India As govt of India is promoting to create jobs in rural area's in Big way we are getting stuck as there is no clarity of making or receiving calls in our centers in Rural Are...
Hi, I'd like to ask how to check via SNMP signal to noise ratio or number of codewords (without errors, with correctable errors etc.) on interfaces connected to CTMS via R-PHY shelf. So far, I've been using OIDs from DOCS-IF-MIB (like for exampl...