lundi 1 juillet 2013

The 3 keys to designing a private cloud -- or data center

A lire sur:

July 01, 2013

Even if you're not ready for a private cloud, its best practices apply to your modern data center today

As much as the public cloud has started to work its way into the fabric of many enterprise computing infrastructures, a wide array of workloads still can't be moved into the cloud. Chief among them are those that center around specific performance requirements, security implications (especially in regulated industries), and getting a hold of and paying for high-speed network access to the cloud. However, even in these cases, it's highly desirable for business units to self-manage their computing resources and pay only for the resources they use.
In these situations, the construction of a private cloud can often satisfy many of the goals of going to the public cloud, while at the same time allowing the enterprise to implement whatever degree of performance capability and security infrastructure it requires. Likewise, maintaining infrastructure on premises removes the need to source potentially expensive WAN connections to the cloud.
Although building a private cloud shares many of the same steps as building an enterprise data center infrastructure, it is different in three key ways.
1. Balanced management capabilities
The most important differentiator between a traditional on-premises virtualization infrastructure and something that can be legitimately called a private cloud is the management layer -- or, perhaps more important, how that the management layer is actually used by IT.
As an example, imagine a traditional IT shop that supports a modern blade-based virtualization infrastructure. Chances are the gear used to put this infrastructure together can support a private cloud. However, the management layer is likely to be completely restricted to IT's use. If a business unit wants to deploy some servers -- even virtual ones -- a request to IT is needed and IT uses whatever management tools it has to complete the request on its own schedule.
Generally speaking, any private cloud infrastructure will offer some level of self-service. That might mean business units can manage all aspects of computing-resource lifecycle management from cradle to grave. Or it may simply automate one portion of the lifecycle that has proven to be a challenge for the organization as it relates to service delivery lead times or support response times.
For example, IT might make available private cloud management tools that allow a business unit to request a computing resource, but might still exercise oversight in approving them. Or it might allow the entire process to be entirely automated and self-service to the point of allowing a business unit to upgrade its "purchased" resources on the fly.

Aucun commentaire:

Enregistrer un commentaire