Q: The standard cloud model seems to be moving away from the public cloud and toward the private cloud. What do I need to know to get a good start on a private cloud deployment?
A: The key driver toward the private cloud is achieving greater capabilities, such as improved elasticity. With the private cloud, firms can enable user self-service, which is crucial for pooling resources and is becoming increasingly popular as organizations become more comfortable with ceding control to employees. A private cloud allows you to track the allocation of resources across the network.
But the real difference between the public and private clouds is the management tool set that is available for the private cloud. This tool set allows your organization to connect its various SANs for abstraction purposes, as well as to define different networks. System Center 2012 provides Virtual Machine Manager (VMM), Service Manager, App Controller, Orchestrator, and other crucial offerings that enable high-grade private cloud deployment. Orchestrator is essentially the foundation that connects the various other components.
Also useful is Microsoft Cloud Services Process Pack. This set of modules and documents can guide users through the private cloud configuration process. It provides recommended architectures that effectively deliver the private cloud in a box. Although Cloud Services Process Pack isn't necessary, it does offer a more complete solution that can be deployed quickly.
In any event, one of the most important factors to consider in advance of deploying a private cloud is the issue of authorization and allocation. Establish practices concerning who needs to sign off on various cloud-based efforts and which parts of the private cloud a given employee can utilize. Without a clear idea of your organization's processes, the self-service advantages of the private cloud will be undermined.