| By John Gannon |
Article Rating: |
|
| October 28, 2008 11:00 PM EDT |
Reads: |
4,945 |
John Gannon's Blog
Although cloud computing provides financial benefits like reduction of CAPEX and the ability to pay-as-you-go, organizations will still need a reasonable amount of granularity in the reporting of cloud usage and the ability to map that usage into a financial chargeback model that makes sense. 
Amazon has gone live with Windows support in the EC2 cloud while at the same time announcing a private beta for some new scaling and load balancing features. These features will certainly be useful for the smaller customers of EC2, but my guess is that those features were driven by a desire to make the Amazon cloud more “enterprise friendly”. And speaking of enterprise friendly…
In an earlier post I discussed some areas that Amazon and the other cloud providers will need to address before they’ll see mass enterprise adoption. One area I did not discuss, but that is also important, is cloud financial management (cloud “chargeback”).
Chargeback methodologies and technologies are used to help medium-to-large enterprise IT departments meter usage of key IT resources (storage, network, compute) and then allocate usage back to individual business units, applications, etc.
Although cloud computing provides financial benefits like reduction of CAPEX and the ability to pay-as-you-go, organizations will still need a reasonable amount of granularity in the reporting of cloud usage and the ability to map that usage into a financial chargeback model that makes sense. Knowing which applications and departments are driving IT expenses is critical now, and will continue to be critical as cloud computing goes mainstream in the enterprise. Therefore, any cloud chargeback solution should integrate with the chargeback framework that the company uses to manage their physical assets.
I can also see forecasting of cloud computing demand within enterprises becoming more important as greater usage variability drives expense variability. Avoiding CAPEX is a great thing, but if you’re unable to predict OPEX, you’re going to have other problems. Traditionally, capacity planning and demand forecasting has been a dark art (at least in the distributed systems world), but I think the industry as a whole needs to think about new ways to address the problem in a hybrid cloud/non-clouded world.
Subscribe to Ruby-On-Rails Email News Alerts
Subscribe via RSS
