Welcome!

Release Management Authors: Pat Romanski, Elizabeth White, David H Deans, Liz McMillan, Jnan Dash

Related Topics: Release Management , Java IoT, Industrial IoT, Microservices Expo, Linux Containers, Open Source Cloud, Eclipse, @CloudExpo

Release Management : Blog Post

Enterprise Cloud Computing Requires Service-Level Discipline

Real Time Infrastructure Enables Clouds through Quality of Experience (QofE) Management

Adaptivity at Cloud Expo

Organizations have become increasingly dependent on technical infrastructure to enable customer interactions. As such, the business has a vested interest in making sure its technology partners understand what constitutes good customer experience so that it’s prepared for projected volumes and rapidly knows how to resolve any impediments.

Yet, the industry standard model and best practices for establishing, managing, and measuring contracts via traditional Service Level Agreements (SLAs) has not been successful.

In practice most agreements are based on simple Key Performance Indicators (KPIs) that are grounded in arcane technical concepts and not in the context of the customer consuming services. The result is artificial measurements that lead to IT having a ‘green’ dashboard, but lost business opportunity and irate customers.

The source of this disparity is the traditional agreement which is limited to guarantees of uptime, quantities of dedicated resources, and/or KPIs of utilization. This supply-driven view of the platform does not map back to business events and therefore has limited applicability. Furthermore, this traditional agreement model entirely breaks down when considering the infrastructure in support of a Real Time Enterprise (RTE) operating in the cloud.

To overcome these limitations, a simple truth is offered: the best measure of business performance in the context of a technical system is the balance between the experience of its users, its cost, and its efficiency: its Quality of Experience (QoE).

A successful agreement will act as a lens on the desired QoE as defined by the business and define the policy and controls required to properly measure and manage services provided.

Forging Successful Agreements Based on Quality of Experience
For business and IT to be successful, a new agreement framework is required. This new agreement framework focuses on striking the proper balance of QoE that is realized through a combination of SLAs, Operational Level Agreements (OLAs), and a new agreement type, the Execution Level Agreement (ELA).

See Figure 1 - Relationships between SLAs, OLAs, and ELAs

Furthermore, this framework not only provides an introduction to ELAs, but also adapts the traditional SLA and OLA in order to measure and manage the qualities most important to supporting business demand within a real-time and dynamic operating environment.

Using the new lens of QoE, there are generally three types of agreements that can be forged between an IT consumer and provider.

* Service Level Agreement (SLA)—An agreement, not to be confused with the traditional SLA based on KPIs, that specifies the worst-case limit to the usage characteristics (demand) the consumer will generate and the lower limits of infrastructure characteristics (supply) the provider will provide in context of QoE. The document spells out the consequences of a breach by either party, which can generally be summed up as follows. If the provider is unable meet the service level, then the document spells out the consequences (frequently financial); however, if the upper consumption limits are exceeded, the provider commitment converts to a best effort to meet the demand. This type of agreement is a two-way commitment between the IT entity and its consumer. When entered into with an external entity it may be considered a legally binding contract.

This interpretation of a SLA is based on a different foundation than the traditional SLA. The agreement is two-way, which means it’s possible for either party to breach the SLA. Secondly, the basis for measuring SLA compliance is based on measurable characteristics the business deems important (e.g. response time, transaction time, quantities of users, etc.).

* Operational Level Agreement (OLA)—An OLA is very similar to a SLA, but between internal support groups it is used to solicit guarantees of performance from IT infrastructure components (web service, grid, middleware, storage, network, etc.) that the application or service is dependent on and to formalize relationships and coordinate support efforts. These components may also aggregate multiple resources, each of which can have its own OLA.

This type of agreement is also two-way, in a similar manner as the SLA. OLA compliance is also based on measurable characteristics that are in support of meeting the ultimate business needs (e.g., response time, transaction time, quantities of users, etc.).

* Execution Level Agreement (ELA)—With the advent of Real-Time Infrastructures (RTI), resources are no longer statically assigned to specific tasks. The ELA formalizes the agreement around how resources are allocated dynamically (high-priority systems get resources first, sometimes at the expense of lower-priority systems). The basic premise is that resources are not owned by the consumer, with the goal of right sizing the environment and that there are enough resources to do the job, while eliminating IT waste. In consideration for releasing the resources the consumer gets the added benefit of reduced cost and if their environment spikes unexpectedly the load will likely be manageable. ELAs are supplemental to a SLA or OLA, as the same two parties enter the agreement.

The concept of an ELA is a radical departure from traditional SLAs, which presume a static infrastructure. The flexibility of being able to change the allocation of resources based on business need, commonly referred to as a utility, can dramatically improve IT performance. To capitalize on the opportunity, this new governance enabled by the ELA is needed.

Implemented properly, SLAs, OLAs, and ELAs act as a link between business and IT that provides a means to measure the success (or quality) of IT services. They define the rules that dynamically and proactively apply the proper amount of resources as needed and when needed. At an elementary level, they define escalation rules in the event of service degradation or disruption. The result enables business success and delivers improved IT value to the company.

Creating an Agreement
Too often the qualities of what define a good SLA are left as an afterthought during the deployment process. However, the qualities of an application should be defined during the requirements process and in turn drive the architectural, design, and testing processes. General notions of requirements are insufficient; rather, detailed requirements should be determined and documented for each action of importance in the system. Not only does this lead to systems that are well designed for their intended function, but it will improve IT’s understanding of how to plan for the management of the system.

Requirements need to be gathered at multiple levels of the system hierarchy: individual user experience (e.g., the home page will render in less than 500ms), sub-system interactions (e.g., data transfers will occur at a rate of 200 messages/second), and holistic (e.g., system activity may peak up to 50 active users). Each requirement must map to a metric that is measurable by IT but oriented around QoE. This can include KPI measurements so long as they map to user interactions or sub-system interactions. For example, measuring memory or CPU utilization may be useful for determining why a SLA is being missed, but are not likely part of the SLA guarantee. The SLA definition should be broad in scope and business goal driven, not limited to technology concerns.

Once the business driven aspects of the SLA are well understood, the IT organization should determine under what conditions the customer goals can be met, which become constraints within the SLA. If the consumer violates the constraints, then the SLA is invalidated. For example, consider the case where the business requirement states that the peak active users will be 50 and the system needs to have a response time of 500ms for the home page. Furthermore, IT stipulates there’s a constraint of 200 max active users to meet this goal. When the 201st user becomes active, the SLA guarantee no longer applies. This makes the SLA a two-way agreement between consumer and provider. While many constraints are soft limits, such as concurrent active users, others are hard limits, such as license counts. It simply isn’t reasonable to have the expectation that no constraints exist.

In our example, if there is a need to support 200+ users, then that should be a requirement and the system needs to be architected and engineered to comfortably support that load. RTI clouds can help deploy additional resources only to a point before the fundamental architecture of a system breaks down.

Quantifying Quality of Experience
Services must be designed to meet a range of operational characteristics that can be measured through qualities. The following are the goals of eliciting service qualities.

  • Identify the measurable qualities for the defined services based on the line of business that will consume them.
  • The qualities must be defined in tangible business terms that promote dialog between business and IT, fostering better alignment.
  • Service quality and constraint definitions help avoid the trap of over engineering, which has caused many current datacenter issues.

Achieving QoE means balancing the user experience (e.g., response time, time to market, availability) with cost and efficiency. QoE cannot be achieved by continually spending money on infrastructure as problems arise. Understanding what the business needs and being able to measure those attributes are critical to achieving QoE. Without measurement there is no opportunity to control the environment to meet demand in real-time.

There are many categories of qualities that can be considered, and not all categories will be appropriate for all lines of business. Within these categories there are many quality attributes, and not all of them are applicable for every service or application. Here are some of the key categories for qualities; the nature of your environment may have specific needs so this list should not be considered comprehensive.

  • Performance: Attributes that measure the peak throughput, average throughput, latency (elapsed time), and/or response time of work that is processed. While system to system interactions will clarify data rates, performance should also address user experience aspects (e.g. page load time).
  • Volumetric Measures: Attributes that measure capacity requirements, register/active user counts, log history length, etc.
  • Temporal Events: Periodic events that may or may not be predicable. For example, shifting workloads by time of day; this can radically change resource requirements. (The ELA will benefit most from this quality.)
  • Availability: Uptime considerations are important, but provide only a limited consideration of this quality. For example, importance should be given to quantify sustained throughput over time and frequency of spikes. Furthermore, percent availability can be deceptive (e.g., 99.99 percent), as uptime for a 24/7 application still could mean three-plus hours of downtime in a year.
  • Failure Recovery: The maximum acceptable time to recover during the critical peak time (e.g., recovery in less than one minute for a trading application during trading hours).
  • Speed of Deployment and Change: The amount of time for configuration changes, code deployments, new resources, etc.
  • User Experience by Geography: This attribute will raise issues of time zones, performance, etc.

Scope of Agreement
Generally the agreement documents are a based on a boilerplate document that is completed in collaboration between the consumer and provider. Here are some considerations for data that should be included in the SLA documents:

  • should have clear start and end dates
  • should note all qualities (response time, availability, etc.) including KPIs descriptions and metrics
  • should clearly identify all metrics that will be collected and reported on (with frequency)
  • should be limited to metrics that relate to meeting consumer (user or sub-system) needs
  • should clearly delineate constraints (two-way)
  • should include the terms by which accounting will be processed
  • should clearly show the full scope of possible QoE qualities that are available (including examples) so that the parties completing the SLA aren’t looking at a blank form
  • backup material should denote a complete mapping of dependencies (from SLA to all related OLAs and ELAs)
  • should indicate all geographic locations associated with the consumers
  • should characterize Mean Time to Repair (MTTR) for all the different sub-systems and the overall system
  • should clearly denote the executive level review of the SLA ranking, to make clear where the SLA fits hierarchically with other SLAs. Note: This should not be perceived as a negative, but rather a pre-calculated business risk. Without this priority, all SLAs must be considered equal, which means by letter of the agreement a development environment should get the same priority as a production system.
  • backup material should denote what tooling is required to acquire measurements

Enacting the Agreement
Prior to a cloud system being enabled for production, its SLA should be prioritized (preferably force ranked) by the CIO or an assigned delegate based on business impact. Sharing this information with the service desk will facilitate a proper response in the case of a problem with widespread impact, so that failures in the more important systems are remediated first.

Furthermore, the priorities of any OLA need to be evaluated against the overall SLA. If a system has high priority, but a sub-system has low priority, this can cause unnecessary conflict during recovery (and may be at the root cause of the failure). Any relationships between SLAs, OLAs, and ELAs must be clearly documented and preferably associated with the system in the Enterprise Configuration Management DataBase (CMDB).

Once in production, regular real-time tracking and reporting of SLA metrics and their evaluation against the configured limits becomes critical. This information can be used to manage routine capacity planning and give advanced warning of a system that may be approaching its architectural limits. Often the trending of this information will provide more insight than the raw numbers themselves.

In addition, the system will require automated monitoring. Monitoring is performed on various qualities of the services that comprise the SLA, including but not limited to end-to-end transaction monitoring, application monitoring, security service monitoring, IP connectivity monitoring, etc. These collected statistics, in relationship to the SLA qualities, should be presented in real-time back to the business through a dashboard. Note that the characteristics being measured are business driven (and not technology driven). So, the dashboard will likely provide significant new insights into business operations beyond the monitoring activities.

Financial Considerations
The traditional static infrastructure caused IT to provision dedicated resources able to meet peak load. A RTI with ELAs can be much more efficient with resources using the principles of an IT utility, such that ‘units’ of resources usage can be metered and billed. The SLA facilitates this financial model by defining constraints and the terms by which accounting will be processed.

The monitoring and dashboard of the environment can provide real-time insight into this usage, providing a new level of transparency to the business, such that the business understands the quantity of the resources their actions are consuming. This provides a healthy environment within which to relate business actions with infrastructure expenses. This information can be used to help with justifying infrastructure expenses when making budgeting decisions around systems and services, which has traditionally been poorly understood.

Conclusion
When a company embraces the need to become a Real Time Enterprise operating in the cloud, it will find that migrating toward a Real Time Cloud Infrastructure is inevitable. While there are many technologies that can and should be incorporated, the implementation of these technologies is not enough.

The introduction of a new agreement framework based on Quality of Experience fundamentally changes how agreement is reached and defined. The conversation becomes oriented around business goals, is defined by qualities desired, and is agreed to as equal partners. The buy-in of both parties around a common language sets a reasonable foundation for moving forward.

The introduction of shared resource environments has impacts on datacenter operations. Prioritization of systems and services is required across a business line to ensure that dynamic resource allocation is policy driven based on business need, such that unexpected events are handled properly. The new ELA construct is a key enabler to managing the environment in a cost effective predicable manner.

More Stories By Tony Bishop

Blueprint4IT is authored by a longtime IT and Datacenter Technologist. Author of Next Generation Datacenters in Financial Services – Driving Extreme Efficiency and Effective Cost Savings. A former technology executive for both Morgan Stanley and Wachovia Securities.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@ThingsExpo Stories
As businesses evolve, they need technology that is simple to help them succeed today and flexible enough to help them build for tomorrow. Chrome is fit for the workplace of the future — providing a secure, consistent user experience across a range of devices that can be used anywhere. In her session at 21st Cloud Expo, Vidya Nagarajan, a Senior Product Manager at Google, will take a look at various options as to how ChromeOS can be leveraged to interact with people on the devices, and formats th...
SYS-CON Events announced today that Yuasa System will exhibit at the Japan External Trade Organization (JETRO) Pavilion at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Yuasa System is introducing a multi-purpose endurance testing system for flexible displays, OLED devices, flexible substrates, flat cables, and films in smartphones, wearables, automobiles, and healthcare.
SYS-CON Events announced today that Taica will exhibit at the Japan External Trade Organization (JETRO) Pavilion at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Taica manufacturers Alpha-GEL brand silicone components and materials, which maintain outstanding performance over a wide temperature range -40C to +200C. For more information, visit http://www.taica.co.jp/english/.
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities – ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups. As a result, many firms employ new business models that place enormous impor...
SYS-CON Events announced today that SourceForge has been named “Media Sponsor” of SYS-CON's 21st International Cloud Expo, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. SourceForge is the largest, most trusted destination for Open Source Software development, collaboration, discovery and download on the web serving over 32 million viewers, 150 million downloads and over 460,000 active development projects each and every month.
SYS-CON Events announced today that Dasher Technologies will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Dasher Technologies, Inc. ® is a premier IT solution provider that delivers expert technical resources along with trusted account executives to architect and deliver complete IT solutions and services to help our clients execute their goals, plans and objectives. Since 1999, we'v...
As popularity of the smart home is growing and continues to go mainstream, technological factors play a greater role. The IoT protocol houses the interoperability battery consumption, security, and configuration of a smart home device, and it can be difficult for companies to choose the right kind for their product. For both DIY and professionally installed smart homes, developers need to consider each of these elements for their product to be successful in the market and current smart homes.
SYS-CON Events announced today that MIRAI Inc. will exhibit at the Japan External Trade Organization (JETRO) Pavilion at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. MIRAI Inc. are IT consultants from the public sector whose mission is to solve social issues by technology and innovation and to create a meaningful future for people.
SYS-CON Events announced today that Massive Networks, that helps your business operate seamlessly with fast, reliable, and secure internet and network solutions, has been named "Exhibitor" of SYS-CON's 21st International Cloud Expo ®, which will take place on Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. As a premier telecommunications provider, Massive Networks is headquartered out of Louisville, Colorado. With years of experience under their belt, their team of...
SYS-CON Events announced today that TidalScale, a leading provider of systems and services, will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. TidalScale has been involved in shaping the computing landscape. They've designed, developed and deployed some of the most important and successful systems and services in the history of the computing industry - internet, Ethernet, operating s...
Coca-Cola’s Google powered digital signage system lays the groundwork for a more valuable connection between Coke and its customers. Digital signs pair software with high-resolution displays so that a message can be changed instantly based on what the operator wants to communicate or sell. In their Day 3 Keynote at 21st Cloud Expo, Greg Chambers, Global Group Director, Digital Innovation, Coca-Cola, and Vidya Nagarajan, a Senior Product Manager at Google, will discuss how from store operations...
Widespread fragmentation is stalling the growth of the IIoT and making it difficult for partners to work together. The number of software platforms, apps, hardware and connectivity standards is creating paralysis among businesses that are afraid of being locked into a solution. EdgeX Foundry is unifying the community around a common IoT edge framework and an ecosystem of interoperable components.
In a recent survey, Sumo Logic surveyed 1,500 customers who employ cloud services such as Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). According to the survey, a quarter of the respondents have already deployed Docker containers and nearly as many (23 percent) are employing the AWS Lambda serverless computing framework. It’s clear: serverless is here to stay. The adoption does come with some needed changes, within both application development and operations. Tha...
SYS-CON Events announced today that IBM has been named “Diamond Sponsor” of SYS-CON's 21st Cloud Expo, which will take place on October 31 through November 2nd 2017 at the Santa Clara Convention Center in Santa Clara, California.
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, will lead you through the exciting evolution of the cloud. He'll look at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering ...
Infoblox delivers Actionable Network Intelligence to enterprise, government, and service provider customers around the world. They are the industry leader in DNS, DHCP, and IP address management, the category known as DDI. We empower thousands of organizations to control and secure their networks from the core-enabling them to increase efficiency and visibility, improve customer service, and meet compliance requirements.
Join IBM November 1 at 21st Cloud Expo at the Santa Clara Convention Center in Santa Clara, CA, and learn how IBM Watson can bring cognitive services and AI to intelligent, unmanned systems. Cognitive analysis impacts today’s systems with unparalleled ability that were previously available only to manned, back-end operations. Thanks to cloud processing, IBM Watson can bring cognitive services and AI to intelligent, unmanned systems. Imagine a robot vacuum that becomes your personal assistant tha...
With major technology companies and startups seriously embracing Cloud strategies, now is the perfect time to attend 21st Cloud Expo October 31 - November 2, 2017, at the Santa Clara Convention Center, CA, and June 12-14, 2018, at the Javits Center in New York City, NY, and learn what is going on, contribute to the discussions, and ensure that your enterprise is on the right path to Digital Transformation.
Recently, REAN Cloud built a digital concierge for a North Carolina hospital that had observed that most patient call button questions were repetitive. In addition, the paper-based process used to measure patient health metrics was laborious, not in real-time and sometimes error-prone. In their session at 21st Cloud Expo, Sean Finnerty, Executive Director, Practice Lead, Health Care & Life Science at REAN Cloud, and Dr. S.P.T. Krishnan, Principal Architect at REAN Cloud, will discuss how they b...
SYS-CON Events announced today that mruby Forum will exhibit at the Japan External Trade Organization (JETRO) Pavilion at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. mruby is the lightweight implementation of the Ruby language. We introduce mruby and the mruby IoT framework that enhances development productivity. For more information, visit http://forum.mruby.org/.