09/17/2012 – By Rob Clyde
When it took months to get a new server, few people bothered unless it was really important. Now that it’s easy, people provision new servers all the time to test new infrastructure or run pilot projects. Without any accounting, there is no incentive to be act responsibly. Resources are over-provisioned and then left running long after they are no longer needed because there is no incentive to turn them off. The private cloud quickly runs out of resources. The IT department must either purchase more resources (which is expensive) or must deny new service requests. Denying service requests is a good way to draw negative attention to your shiny new private cloud.
Luckily, there is a simple solution: Don’t deploy a private cloud without usage accounting. When users are charged for the resources they use, they are more careful and responsible. Users think twice about what resources they really need, and virtual machines are more likely to be turned off when they are no longer needed. When users pay for the services they consume, necessary funds become available to maintain and grow the private cloud. This path is proven to work in many real-world deployments.