The up.time IT Systems Management Blog

Posts Tagged ‘cloud cost’

How Real-Time Cost Monitoring can Save Real IT Budget

Tuesday, August 7th, 2012

Rule No. 1 Never lose money.
Rule No. 2 Never forget rule No. 1
-Warren Buffet

The benefits of flexibility and scalability are abundant when your IT department deploys your servers into a virtual cloud setting.

When running at optimal efficiency, this type of infrastructure can provide your company with unexpected improvements over your old on-site servers. Increased agility, increased physical and operational security, along with statistically less downtime can add to the list of benefits.

For most companies, the “big move” to the cloud is all about a better allocation of assets.

Saving money with virtual cloud servers starts with the relief of not having to shell out thousands of dollars in capital spend for equipment and space to house and maintain it.

After that, the regular monthly savings will come typically from personnel watching the resource consumption over time and attempting to gauge or predict future usage.

Unfortunately, this is where cloud can get complicated. Today, companies are stuck with inaccurate forecasts and very time consuming methods to calculate costs and usage mid-stream. The end result is wasted time and unexpected costs that aren’t seen until the bill is delivered a month later.

Gone are the days of the good ol’ guesstimate.

However, with the addition of “real time” cloud monitoring to an Amazon AWS deployment, companies can easily see how resources are being used, and the cost of those resources, with up-to-the-minute metrics that allow for a more informed and efficient cloud management process.

And now that you no longer have to try to balance cloud costs blindly, you can do the following three things better…

1. This little piggy went we-we-we all the way to the bank

If a certain part of your system (or a certain department) is “hogging” cloud services or driving up costs, it is clearly visible. This type of insight helps IT ask the right questions, like “ Is this an area we are wasting resources?” or “Is this additional cost justified?” Real-time monitoring and alerting lets you have this conversation immediately, before costs escalate out of control. The other option is to wait for the end of the month bill and then let the arguments (and firings) begin…

2. When in need, it’s allocation indeed

With plain view of your metrics, maybe it’s the other way around. You can ask questions like: “Is this something we’ve neglected in the past, but is obviously a big part of our business?”, “Should we invest more in this part of our business?” or “Is the additional cloud cost of this project/application/department justified?”.

3. Your own cloud cost management crystal ball

With this data, you can now predict what resources you’ll use more. You can also accurately predict your monthly cloud costs quickly and easily. It will make your executives happy and keep the CFO off your back.

In conclusion, it’s this “Zen-like” balance between cost and performance that you’ll need to find. Without truly understanding the cost side of that equation, you’re forever guessing and off-balance. How long can you keep that up and still hope to be successful?

The Cost of Cloud – Part 3: Testing in the Cloud

Wednesday, June 1st, 2011

Cloud Capacity and Cloud TestinAs the conclusion to my 3 part Cost of Cloud Follow-up (click here to read part 1, click here for part 2), I wanted to focus on development and testing in the cloud and what questions you need to answer before beginning any tests.

 

Example #3 – Development and Testing in the Cloud: Although spinning up new test and development environments in the cloud improves agility, the essential questions to ask are:

 

  • Internal or Cloud: Is it more cost-effective to host the application or service internally or in the cloud? Can IT prove its decision?
  • Which Cloud is Best: Which cloud vendor should be chosen?
  • How Much will it Cost: How much will this service/workload cost month over month?
  • Failsafe Cloud Alerting and Reports: Additionally, the added problem of developers forgetting to de-commission cloud infrastructure and services drives major cost overruns. Proper notification of these ‘cloud zombies’ is essential to prevent large bills over time.  While services like Amazon’s AWS are an incredible boon to being able to create development and test environments in a few clicks, there are latent costs which aren’t always readily apparent – stopped instances still consume storage resources (and cost), snapshots linger even when volumes are deleted (and add more cost), just to name a few. IT needs better visibility.

As stated earlier (part 1), there are no tools that can help IT (or LOBs) model the cost of their cloud needs, predict their workload costs or notify when costs are escalating. However, there are tools coming in the future.

The most fundamental aspect of optimizing performance monitoring in the cloud is to understand the relationship between application/infrastructure performance and cost. Presently, the industry is just beginning to understand how to monitor the performance of applications in the cloud, yet it lacks a cloud costing dashboard necessary for IT managers to make smart budget related decisions. How can organizations understand the cost of cloud computing without a deeper level of visibility? It has become crucial for IT to tie cloud success to cost analysis, as well as overall system performance.

Conclusion: So to Cloud or Not to Cloud? How will you tie your cloud decisions to cost for justification to senior management? Or will you just deploy and cross your fingers?

Alex

The Cost of Cloud – Part 2: Applications in the Cloud

Wednesday, May 25th, 2011

As part 2 of my Cost of Cloud Follow-up (click here to read part 1), I wanted to focus on applications in the cloud and what you need to see, report on and predict future cloud costs.

 

Example #2 – Applications in the Cloud:

  • See Cloud Cost: IT needs to see a clear monthly workload cost of their entire Amazon AWS deployment (by server, application or service) before they get the bill. For those companies that have deployed in AWS, the anxiousness and pain associated with the monthly AWS bill can be quite frustrating.
  • Predict Cloud Cost: Reports are needed that can estimate or predict the cost of running an application or service in AWS before it’s deployed. Predicting cloud cost based on individual workloads, applications or services is essential.
  • Identify Cloud Ready Applications: Reporting that can show which workloads are prime candidates for cloud deployment would be extremely helpful to IT departments wrestling with how to use cloud most effectively.

If you have any questions about how you accomplish any of the above, let me know by posting a comment.

Alex.

The Cost of Cloud – Part 1: Cloud Cost Analysis

Wednesday, May 18th, 2011

Clost of Cloud, Cloud CostAs a follow-up to my cost of cloud computing post that had a large response, I decided to do a follow-up cloud cost analysis. This is part 1 of a 3 part series that will be posted over the next few weeks.

The ultimate goal of deploying application or dynamic infrastructure to the cloud is the truly agile and cost-competitive nature of running and managing applications and infrastructure. However, cost can increase exponentially without proper cloud monitoring and cloud cost modeling. It has become crucial for IT to tie cloud success to cost analysis, in addition to overall system performance. This article will provide some common pitfalls and pains around current gaps in cloud costing and deployment, as well as a key set of questions to help IT make smart cloud decisions.

Up to now, the success of applications in cloud, virtual and physical environments have been viewed in only two dimensions – availability and performance. However, perhaps the most important dimension is cost, and it’s cost that will dramatically influence what, when and where IT organizations deploy to the cloud. Presently a major gap is in tooling, where no cloud monitoring tools can help IT and LOBs monitor their cloud costs, predict workload/application cost, notify when costs are escalating, as well as provide standard cloud performance and availability monitoring. However, we do see this tooling issue changing in the near future.

To date, companies have been oblivious to the workload cost of an application running in the cloud, apart from unclear monthly billing. We are entering a new era where performance and availability will be baseline requirements, but workload cost efficiency will be the new key to success. This will be the age of ‘economic compute’ and will be defined by how and where companies can run workloads at the best cost (assuming performance and availability remain constant). It won’t matter if it’s internally run on physical or virtual servers, or in the cloud, as the economics will drive this decision. However, the lynch pin to this costing decision model is missing…

To responsibly manage IT budgets, companies need visibility to the cost and performance data of workloads, applications and dynamic infrastructure services. However, the industry is missing a complete toolset or product suite that can help IT easily see and predict the cost of cloud deployment. Applications and services can be deployed on cloud infrastructure (assuming it returns acceptable performance and availability), but it’s essential for IT to have clear visibility to what the workloads will cost comparatively, across different cloud vendors or even the cost of an internally run workload. How can IT make a cost-conscious decision without the basic cost data of an application, workload or service? Quite simply, it can’t. This is part one of a three part series where the idea of the economic cloud comes into play:

Example #1 – Dynamic Infrastructure Services:

  • Ensure IT Doesn’t Overpay: A company may have provisioned a $500 per month system, but if its CPU is only consumed 10 percent of the time, then one is largely over paying. Now scale that scenario out to a company that is running many services, applications and servers in the cloud.
  • Companies with Many Separate Cloud Accounts: For IT managers trying to understand the cumulative costs of many developers or departments (LOBs) with cloud accounts, it can be almost impossible, with no clear means of reconciling usage (until it’s too late).
  • Manage Cost Across Geographically Dynamic Workloads: For more advanced scenarios, there are now a number of services that allow the creation of cloud instances in specific geographic regions, which enables a new generation of smartphone or mobile applications to exist.  There are millions of smartphone users in the world in non-North American geographies, such as Latin America – imagine if you could dynamically and geographically provision cloud resources that are compute heavy, or can service the requests of these remote smartphone clients, in a cost effective manner.  This reduces bandwidth requirements, increases the response time and can be done on cheaper, temporarily available compute resources. This kind of dynamism is incredibly powerful, yet monitoring the changing costs and performance of these cloud resources is going to be a difficult problem to solve.

Stay tuned over the next few weeks for more examples of where the economic cloud comes into play and please, let me know your feedback/questions by posting a comment.

Until next week…

Alex