Skip navigation
Policy Makeovers for Converged Environments

Policy Makeovers for Converged Environments

Making the best use of converged infrastructure not only requires changes in processes, but in policies and standards.

While the benefits of converged infrastructure are undeniable, so too are the changes this type of infrastructure can cause to a typical data center. No longer, for example, does IT staff have to spend weeks collecting requirements, sizing, planning, procuring equipment, deploying and testing when servicing a new application or requirements. Instead, the process is streamlined and much faster.

That’s just one difference between traditional data center architecture and converged infrastructure. Making the best use of converged infrastructure not only requires changes in processes, but in policies and standards.

While traditional data center standards were developed for the typical federated model of IT deployment, “converged infrastructure is much more akin to mainframes, so the architecture and compliance standards must apply to these types of architectures as well,” says Roy Illsley, a lead infrastructure analyst at Ovum Research. Illsley also points out that in most cases, converged infrastructure coexists with traditional architecture, so standards and policies must be broadened to include both.

“This is the area where compliance and standards fall down,” he says. “There is never going to be a single ring that rules them all, so we just need to have the appropriate standards for the appropriate systems.”

Here are three areas that need policy makeovers:

1. Capacity planning and scale

In the world of converged architecture, each system has a finite capacity, and the way to increase capacity is by adding another unit of infrastructure. In traditional federated deployments, whatever is the weakest link—storage, compute or networking—can be upgraded independently from the other resources. That means that policies should look at converged systems based on workload and performance metrics--slightly different from traditional capacity planning approaches that plan via individual resource consumption. Some even recommend implementing a type of “reservation system” to maintain control over capacity requirements.

Because converged infrastructure scales so much more quickly, it also makes sense to rework the thresholds and trigger events that determine lead time for provisioning more resources.

2. Operating and maintenance procedures: While maintenance is always complicated, it’s a bit easier to schedule in a legacy environment where storage, compute and network resources are completely separate from each other. In a converged environment, it’s important to coordinate operating procedures related to maintenance, since server, storage and network staff and technology are all working closely together. This requires clearly defined and controlled policies that include prioritization and authority.

3. Change management: Change management processes should be reworked to ensure that they can keep changes being made to one pool of resources from affecting others. Without these policies in place, a configuration change to something at the virtual server level could impact storage capacity for something else.

Before undertaking any of these changes, review all business processes and corporate goals. By mapping those processes and goals to the new data center environment, the most important changes will rise to the top. Once these changes have been made, it’s also important to revisit them each time a new business goal or new technology architecture is implemented.

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.


Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.