Flexibility
Converged systems represent a trade-off in flexibility. When you choose a converged system, you lose the ability to make fine-grained choices about components that you have when building something from individually selected components. But you gain a set of validated components known to work with each other, which are less likely to encounter nasty ‘gotchas’ down the road.
Marketing and advertising company STW Group chose converged infrastructure, specifically FlexPod from integrator VMtech, for precisely this reason. “We wanted something that wasn’t as prescriptive as some of the other in-a-box solutions,” says STW Group CIO Tom Ceglarek. The company installed FlexPod infrastructure a little over five years ago and has grown it to suit their evolving requirements.
It was also important to STW Group that the system was very much integrated when it came to the support arrangements. “There’s people willing to stand behind this combination of products and take responsibility,” Ceglarek says.
Who’s using it?
“If you look at the telco industry in Australia, you’re going to find several telcos using Vblocks as the foundation of their private cloud capability,” says Trevitt. Telstra offers private cloud services on Vblocks out of NextDC.
System integrator Dimension Data also uses Vblock to power its own private cloud for customers, even if the company implemented a FlexPod-based private cloud for ING Australia.
The bank’s choice also touches on the distinction within the converged systems space between an all-in-one stack from VCE and the blueprint provided by Cisco and NetApp. “While FlexPod is absolutely a converged system, it’s still a reference architecture rather than a pre-configured or pre-engineered solution,” Prowse explains. “ING needed some customisation for some DevOps and application requirements they had.”
Who profits?
Are converged systems good for end customers, or do most of the benefits flow to the channel?
“Customers should really only care about the outcome they’re getting,” says Peter Prowse.
“Most of our conversations with customers are around SLA and legal constructs,” says VMtech’s Len Findlay. He says customers only need to care about the gear underneath so that they believe the agreed SLA is achievable.
“We care about the fact that it’s FlexPod because we’re trained to be able to deliver that technology very, very well.”
The move to using pre-integrated hardware stacks like converged and hyper-converged infrastructure means that channel partners are having to become more skilled in total stacks of infrastructure and software, as well as the business problems they’re helping to solve.
It’s not about the tech
“There’s a great opportunity to wrap high-value services around converged infrastructure, to transition their businesses from comparatively lower-value rack, stack and integrate activity, and move it more to managed services or private cloud capability,” Trevitt says.
“Customers are asking partners more and more to focus on the outcomes they can deliver and are less concerned with the procurement function that resellers used to provide,” he adds.
Partners should be making sure they are able to continue to provide services that customers value, which increasingly have nothing to do with racking and stacking gear.
To remain a valued partner, you must start talking to customers about their business outcomes and helping to broker a relationship with the vendors who best help customers to resolve their business problems.
What are converged systems?
Reference architecture A reference architecture defines a set of components – compute, storage, networking and software – that can be combined to build a system. The customer or systems integrator is responsible for procuring and assembling the components. Example: NetApp FlexPod
Engineered system A set of compute, storage, networking and software components is assembled by the vendor and delivered as a unit, ready to be installed in the customer’s data centre. Example: VCE Vblock
Hyper-converged system Compute and storage pre-configured and purchased as ‘nodes’ that are connected over a network. The network components are usually purchased and installed separately and do not form part of the node configuration. Example: Nutanix, Simplivity
A brief history of convergence
The concept was sound, even in the early days. New hardware and software helped bring the industry’s top vendors to the table as new offerings hit new performance benchmarks.
2008 - Exadata
Arguably the first converged system was the Sun Microsystems (now Oracle) Exadata database machine launched in 2008 as the first of its “engineered systems”. The Exalogic product line was introduced in 2010, positioned as a more generic compute platform than the database specific Exadata line.
2009 - Vblock
VCE was formed in November 2009 as a joint partnership between VMware, Cisco and EMC to develop cloud computing platforms originally known as Vblock infrastructure packages. Cisco and EMC announced a joint venture at the same time called Acadia, which would build Vblock infrastructure packages for customers. Acadia was combined into the VCE entity in January 2011. In October 2014, EMC acquired 90 percent of VCE, while Cisco retained 10 percent.
2010 - FlexPod
NetApp launched its FlexPod reference architecture in 2010, in partnership with Cisco. FlexPod was widely seen as a competitive response to EMC/VCE’s Vblock.
2011 - CloudSystem
HP (now HP Enterprise) launched its CloudSystem platform in January 2011, which was merged into the Converged Systems portfolio in April 2013.
_page-0001.jpg&w=100&c=1&s=0)
-1.jpg&w=100&c=1&s=0)
.png&w=100&c=1&s=0)
