- Situation: Consolidation, standardization, and virtualization mean that a x86/x64 server is no longer a stand-alone silo running a single Windows or Linux application; it is now a single processing node, something variously called an utility infrastructure or internal cloud.
- Challenge: Nobody does wholesale server replacement. When it comes time to replace end-of-life servers and/or add new servers, there are a range of tactical choices to be made in terms of configuration and form factor. For example, are blades the future or will traditional rack mount do? How many processors/cores per server is optimal? What is the best configuration for lower total cost per server?
- Solution: This solution set will provide strategy for building a consolidated server infrastructure that will balance maximum capacity and increase efficiency while limiting costs.
Our Advice
Critical Insight
- The transition from an infrastructure of distributed server silos to a consolidation will be evolutionary – progressing as servers come up for refresh or new servers need to be added. Against a consolidation strategy, tactical choices need to be made to meet immediate need while the appropriate building blocks for the cloud are being created.
- Blade servers are typically used in models for the “processing layer” of the consolidated utility infrastructure. Blades are the right choice for certain situations, however rack mounted and perhaps even stand alone servers can also fit into this picture.
- The server acquisition strategy should look at total cost of a particular server configuration and form factor against capacity requirements and current and future workload consolidation (through virtualization).
Impact and Result
This solution set will provide a framework for establishing the form factor and configuration of those building block servers that will be the basis of your utility infrastructure.