|By Dan Ushman||
|May 14, 2013 01:21 PM EDT||
When you're dealing with something as critical as your business infrastructure, you want to be sure that you'll get what you signed up for. If a company promises something, and you promise your colleagues something based on it, you want it to happen. That's where the service level agreement comes in. It's part of your contract that tells you what to expect and what happens if the company fails to meet those marks. Simple enough, right? Wrong.
Not all service level agreements are created equal. At a minimum, an SLA will formally define the services in a contract. In their highest forms, SLAs embody the values and capabilities of an entire organization, and they provide a clear benchmark for employee performance and customer satisfaction. If you are comparing IT service providers, it's time to set the bar high. Simply put, you want an SLA that is transparent, accountable, holistic, and logical for the provider. Here's how to spot it.
Typical SLAs are buried in 20 pages of legalese. If you can find it, and cut through all the jargon, you might gain a vague idea of what will happen when your service provider fails you. And when your service experiences a disruption - which will eventually happen in one form, no matter which provider you choose - it will fall on you to translate the SLA and request credit, and of course, the company will make it as tiresome as possible to get your money.
Few customers actually get rebated by companies like this, and that, I can assure you, is a business strategy. If you provide a strong service, you don't need to hide behind a labyrinth of legal jargon. And if you are a customer, you do not want to entrust your IT infrastructure or assets with a company that is opaque, indifferent, and irresponsible.
Good providers tell their customers exactly what they're going to get, and tell them exactly what is going on at all times. This is all that customers ask. Speed, though desirable, can never compensate for unpredictability and deceptiveness. An enlightened SLA needs to detail specific, measurable commitments that tell customers what service they will receive, how quickly they're going to receive it, and what happens if they don't get that service.
Let me give a clear example from my experience with IT infrastructure hosting and cloud computing at SingleHop. We have an SLA we call the "Customer Bill of Rights." It more or less anchors every facet of our service. It is in fact an extension of our entire system. We operate on a principle called "Operational Transparency." This means that if a server goes down, we update affected clients in real time. If they wonder "have our servers gone down? If so, how long have they been down this quarter?" or "how much time do I wait for a response from tech support?" they can view a digital Report Card that details each item in their SLA and shows continuously updated data on how SingleHop is performing relative to each agreement. That is transparency. When you combine operational transparency with a detailed SLA, it turns all the usual mirrors around into clear glass.
What happens when a company messes up? Well, several things can happen:
- Irate customers cancel their contract.
- Irate customers invite their provider to a brawl in the legal ring.
- Irate customers watch their provider take responsibility and then respect them for it.
Everyone should prefer option #3. Cancelling a contract and shifting providers is costly and legal battles are very expensive. Migrations are dangerous and can disrupt business. You want an SLA that holds your provider accountable for any failures - be they outages or just slow responses. You should know the exact deployment time for a server and know exactly how much you will be credited if your service provider exceeds that time. You should know the expected response time from tech support, and know exactly how much you will be compensated if they take longer.
You know all this information not because you've been timing your service provider, but because they offer this information upfront. Don't work with a company that you must lasso and tie-down for a rebate.
How many interactions does the SLA cover? And, do items in the SLA conflict? For example, if an SLA promises support updates every three hours, but does not give a first response time, what good is the SLA? You could still bleed money for eight hours before getting a life raft. Great SLAs are comprehensive and holistic. They encourage customer-provider symbiosis. The best SLAs actually play into the interests of the provider - remember, they want lots of happy, sustainable customers.
As a customer, map out your anticipated interactions. If the SLA covers each interaction, it is holistic. If not, you can do or request better.
Understanding What's Not Mentioned
There are a lot of different aspects to an IaaS SLA that should but are not always mentioned. These are obvious to providers but not all customers see them right away. How fast does it take to replace a broken hard drive? Does the company keep replacement parts in stock or does it need to order them? Is there a senior tech available at all hours, and if so, how fast do escalations take? Make a list of the concerns you have, talk to people who have been through it and ask lots of questions. Sometimes when something is omitted, it's omitted for a reason.
Finally, a great SLA should be good for the receiver and the provider. If you are the customer, you should want transparency, accountability, and comprehensiveness to be in the interest of your service provider. Why? Because in an ideal world, you can rely on the same IT infrastructure for years and years, and frankly, that means your provider must succeed. And, if meeting the SLA is in the interest of the provider, then the provider will probably use it to evaluate their employees, sift out the bad eggs, and measure company-wide improvement. If, however, the SLA is against the interests of the company, then your provider may in fact discourage its employees from being too forthcoming and helpful.
Think about an SLA as the ‘moral' code for a company. If being "good" actual falls in line with a company's desire for profit, then that company is more likely to follow their code. If being "good" exacts cruel and unusual punishment on a company, then they will prefer to be "bad." Look for alignment between a company's interests and SLA. If they disagree, run for the hills.
Be Fruitful and Provide
A Service Level Agreement is a template for how a business intends to interact with customers. If it is transparent, accountable, holistic, and business-savvy, it is a winner. If you need a machete and $400 per hour guide to find it in the legal jungle and understand it, it is time to explore other options.
"We've just seen a huge influx of new partners coming into our ecosystem, and partners building unique offerings on top of our API set," explained Seth Bostock, Chief Executive Officer at IndependenceIT, in this SYS-CON.tv interview at 16th Cloud Expo, held June 9-11, 2015, at the Javits Center in New York City.
Aug. 2, 2015 10:00 PM EDT Reads: 676
Take the Long View with Digital Transformation By @IoT2040 | @ThingsExpo #IoT #M2M #API #Microservices #InternetOfThings
Digital Transformation is the ultimate goal of cloud computing and related initiatives. The phrase is certainly not a precise one, and as subject to hand-waving and distortion as any high-falutin' terminology in the world of information technology. Yet it is an excellent choice of words to describe what enterprise IT—and by extension, organizations in general—should be working to achieve. Digital Transformation means: handling all the data types being found and created in the organizat...
Aug. 2, 2015 06:00 PM EDT Reads: 1,124
SYS-CON Events announced today that HPM Networks will exhibit at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. For 20 years, HPM Networks has been integrating technology solutions that solve complex business challenges. HPM Networks has designed solutions for both SMB and enterprise customers throughout the San Francisco Bay Area.
Aug. 2, 2015 05:45 PM EDT Reads: 505
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
Aug. 2, 2015 04:30 PM EDT Reads: 273
The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin,...
Aug. 2, 2015 03:00 PM EDT Reads: 545
Aug. 2, 2015 02:00 PM EDT Reads: 323
Alibaba, the world’s largest ecommerce provider, has pumped over a $1 billion into its subsidiary, Aliya, a cloud services provider. This is perhaps one of the biggest moments in the global Cloud Wars that signals the entry of China into the main arena. Here is why this matters. The cloud industry worldwide is being propelled into fast growth by tremendous demand for cloud computing services. Cloud, which is highly scalable and offers low investment and high computational capabilities to end us...
Aug. 2, 2015 11:00 AM EDT Reads: 200
One of the ways to increase scalability of services – and applications – is to go “stateless.” The reasons for this are many, but in general by eliminating the mapping between a single client and a single app or service instance you eliminate the need for resources to manage state in the app (overhead) and improve the distributability (I can make up words if I want) of requests across a pool of instances. The latter occurs because sessions don’t need to hang out and consume resources that could ...
Aug. 2, 2015 10:30 AM EDT Reads: 257
Approved this February by the Internet Engineering Task Force (IETF), HTTP/2 is the first major update to HTTP since 1999, when HTTP/1.1 was standardized. Designed with performance in mind, one of the biggest goals of HTTP/2 implementation is to decrease latency while maintaining a high-level compatibility with HTTP/1.1. Though not all testing activities will be impacted by the new protocol, it's important for testers to be aware of any changes moving forward.
Aug. 2, 2015 09:45 AM EDT Reads: 202
This week, I joined SOASTA as Senior Vice President of Performance Analytics. Given my background in cloud computing and distributed systems operations — you may have read my blogs on CNET or GigaOm — this may surprise you, but I want to explain why this is the perfect time to take on this opportunity with this team. In fact, that’s probably the best way to break this down. To explain why I’d leave the world of infrastructure and code for the world of data and analytics, let’s explore the timing...
Aug. 1, 2015 07:45 PM EDT Reads: 420
[slides] Storage for Docker Containers By @OnModulus | @DevOpsSummit #DevOps #Docker #Containers #Microservices
Learn how to solve the problem of keeping files in sync between multiple Docker containers. In his session at 16th Cloud Expo, Aaron Brongersma, Senior Infrastructure Engineer at Modulus, discussed using rsync, GlusterFS, EBS and Bit Torrent Sync. He broke down the tools that are needed to help create a seamless user experience. In the end, can we have an environment where we can easily move Docker containers, servers, and volumes without impacting our applications? He shared his results so yo...
Jul. 31, 2015 11:45 PM EDT Reads: 796
Modern DevOps Tool Kit By @Logentries and @NewRelic | @DevOpsSummit #DevOps #Containers #Microservices
Auto-scaling environments, micro-service architectures and globally-distributed teams are just three common examples of why organizations today need automation and interoperability more than ever. But is interoperability something we simply start doing, or does it require a reexamination of our processes? And can we really improve our processes without first making interoperability a requirement for how we choose our tools?
Jul. 31, 2015 11:15 PM EDT Reads: 431
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Jul. 31, 2015 10:00 PM EDT Reads: 1,357
The Internet of Things. Cloud. Big Data. Real-Time Analytics. To those who do not quite understand what these phrases mean (and let’s be honest, that’s likely to be a large portion of the world), words like “IoT” and “Big Data” are just buzzwords. The truth is, the Internet of Things encompasses much more than jargon and predictions of connected devices. According to Parker Trewin, Senior Director of Content and Communications of Aria Systems, “IoT is big news because it ups the ante: Reach out ...
Jul. 31, 2015 07:00 AM EDT Reads: 419
Where the Network Got Invited to the Party By @LMacVittie | @DevOpsSummit #DevOps #Docker #Containers #Microservices
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Jul. 30, 2015 08:15 PM EDT Reads: 1,779
Designing the IT Architecture of the Future with Adrian Cockcroft | @DevOpsSummit #DevOps #Docker #Containers #Microservices
Our guest on the podcast this week is Adrian Cockcroft, Technology Fellow at Battery Ventures. We discuss what makes Docker and Netflix highly successful, especially through their use of well-designed IT architecture and DevOps.
Jul. 30, 2015 08:00 PM EDT Reads: 797
[slides] A New Architecture for the Internet of Things By @JKirklan | @ThingsExpo @RedHatNews #IoT #M2M #InternetOfThings
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Arch...
Jul. 30, 2015 07:30 PM EDT Reads: 1,421
[slides] Workloads and Public Cloud at @CloudExpo By @utollwi | @ProfitBricksUSA #DevOps #Containers #Microservices
Public Cloud IaaS started its life in the developer and startup communities and has grown rapidly to a $20B+ industry, but it still pales in comparison to how much is spent worldwide on IT: $3.6 trillion. In fact, there are 8.6 million data centers worldwide, the reality is many small and medium sized business have server closets and colocation footprints filled with servers and storage gear. While on-premise environment virtualization may have peaked at 75%, the Public Cloud has lagged in adop...
Jul. 30, 2015 04:00 PM EDT Reads: 2,234
MuleSoft has announced the findings of its 2015 Connectivity Benchmark Report on the adoption and business impact of APIs. The findings suggest traditional businesses are quickly evolving into "composable enterprises" built out of hundreds of connected software services, applications and devices. Most are embracing the Internet of Things (IoT) and microservices technologies like Docker. A majority are integrating wearables, like smart watches, and more than half plan to generate revenue with ...
Jul. 30, 2015 02:30 PM EDT Reads: 140
[session] DevOps State of Mind By @RedHatNews | @DevOpsSummit #DevOps #PaaS #Jenkins #Kubernetes #Docker
Rapid innovation, changing business landscapes, and new IT demands force businesses to make changes quickly. The DevOps approach is a way to increase business agility through collaboration, communication, and integration across different teams in the IT organization. In his session at DevOps Summit, Chris Van Tuin, Chief Technologist for the Western US at Red Hat, will discuss: The acceleration of application delivery for the business with DevOps
Jul. 30, 2015 12:45 PM EDT Reads: 1,139