Access your Pro+ Content below.
Defining the right cloud SLA requirements up front
This article is part of the Private Cloud issue of April 2012, Vol. 2 No. 2
Cloud services are moving into the mainstream. They offer elastic IT infrastructure that can respond quickly to new demands, such as business growth or new projects. Cloud models also offer possible cost savings through pay-per-use approaches and economies of scale. But to save money with a cloud model, IT pros have to construct SLAs carefully. Businesses rely on service-level agreements (SLAs) to hold cloud providers accountable for services and to establish a set recourse if a service fails. SLAs specify, for example, the responsibilities of providers, such as the time frame in which a vendor should be able to address a problem and the reparations it should make if downtime occurs and a customer loses business. But, when it comes to cloud SLAs, the devil is in the details. Outlining the terms of customer reimbursement can be problematic, for example. Should customers be reimbursed for lost services, or is it sufficient for an SLA to stipulate a future credit? Not surprisingly, creating solid, realistic SLAs on which both ...
Access this PRO+ Content for Free!
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Features in this issue
Solid technical knowledge, comprehensive tools and a keen business sense are all needed for solid data center capacity planning.
Before signing on the dotted line for cloud services, scrutinize your SLA for unsavory terms. Be wary of these SLA gotchas.
IBM SmartCloud services give enterprises some options to build private and hybrid clouds and may give IBM a chance to improve its lagging cloud image.