As companies search for the most efficient and cost-effective way to deploy converged infrastructure, more and more have come to the conclusion that hosting converged infrastructure on a private cloud makes sense. According to Forrester, about 13 percent of the private market consists of converged systems with compute, network and storage resources. Forrester considers converged architecture an ideal match for private clouds. Private clouds enable companies to control asset provisioning, scalability, security and flexibility. They also tend to be much faster and require fewer onsite employees to manage the infrastructure.
But not all private clouds or all converged architectures have the same capabilities. What might be right for one organization might not make sense for another. Here are some tips for getting it right:
1. Keep it simple.
The best solutions are often the simplest, and that’s definitely true when it comes to private cloud and converged infrastructure, said Stuart Miniman, a senior analyst at Wikibon. “Companies today have bought infrastructure in pieces and have to rack them, stack them and test them. What you want to gain from a converged infrastructure is something that goes in faster and that you shouldn’t have to touch much,” he said. This kind of convergence, combined with a private cloud, should markedly simplify the user experience, he added. Other features that help streamline operations include centralized control, automation systems and integrated lifecycle management.
2. Know your priorities.
Before even beginning your research, know what your users need to do their jobs. That means developing a map that shows how different types of end users will access functions from specific applications. A private cloud is a good way to integrate these functions into a comprehensive service, but it won’t be effective without a deep understanding of what users need.
3. Do an application analysis.
Most companies have a combination of older mission-critical applications and newer digital or mobile applications. By analyzing your applications, you can determine which are best for the private cloud/converged architecture system and which should remain on premise, Miniman explained.
4. Choose the right private cloud and converged architecture vendor.
Make sure your vendor has a proven track record of using a structured service lifecycle approach that addresses not only the technology, but also the people involved. The approach should be as flexible as possible--including support for open standards and a variety of computing environments, among other things--to efficiently enable change as requirements evolve.
5. Don’t overbuy.
Unlike public clouds, which are fully pay-as-you-grow models, private clouds require that companies commit to a base amount of infrastructure. “One of the top complaints I hear from users is that they overbuy,” Miniman said. Companies need to make sure that the vendor they buy from has pricing models in place that will enable them to not only buy the right amount to start, but also to scale as needed. “If you grow as expected, you will pay as expected,” said Miniman. “And if you don’t grow as fast or grow more, you’ll easily be able to adjust.”
Underwritten by HPE
Part of HPE’s Power of One strategy, HPE Converged Architecture 700 delivers infrastructure as one integrated stack. HPE Converged Architecture 700 delivers proven, repeatable building blocks of infrastructure maintained by one management platform (HPE OneView), built and delivered exclusively by qualified HPE Channel Partners. This methodology saves considerable time and resources, compared to the do-it-yourself (DIY) approach.
Based on a complete HPE stack consisting of HPE BladeSystem with Intel® Xeon® E5 v3-based HPE ProLiant BL460c Gen9 blades, HPE 3PAR StoreServ all-flash storage, HPE Networking, and HPE OneView infrastructure management software, the HPE Converged Architecture 700 can be easily modified to fit within your existing IT environment.