Patent Application
20140244311
Embodiments of the present invention relate generally to protecting (e.g., insuring) against data loss/service level agreement (SLA) failures. Specifically, the present invention relates to risk-based insuring of computing workload processing in a networked computing environment (e.g., a cloud computing environment).
The networked computing environment (e.g., cloud computing environment) is an enhancement to the predecessor grid environment, whereby multiple grids and other computation resources may be further enhanced by one or more additional abstraction layers (e.g., a cloud layer), thus making disparate devices appear to an end-consumer as a single pool of seamless resources. These resources may include such things as physical or logical computing engines, servers and devices, device memory, and storage devices, among others.
Many cloud providers offer “production-ready” cloud services coupled with a set of service level agreements (SLAB) for cloud consumers to readily implement. While cloud providers may provide some type of remuneration in the event of SLA failures, challenges may exist when a cloud consumer contracts with a cloud provider who does not. In such situations, the cloud consumer may be left with no immediate recourse if a job/workload is not performed according to predetermined standards (e.g., SLA terms).
In general, embodiments of the present invention relate to an approach for protecting (e.g., insuring) against data loss (e.g., due to SLA failures) in a networked computing environment (e.g., a cloud computing environment). In a typical embodiment, a risk table is created that associates cloud/solution providers with a corresponding risk factor and a cost of insuring the providers based on the risk factors. The risk factors are typically calculated using historical data that is based on (among other things), each provider's historical capability of honoring SLA terms, expected performance levels, etc. In any event, each provider may be associated with a cost of insuring that provider against failing to perform/process one or more future jobs/workloads. This allows a consumer who needs a workload to be processed to: view the risk table, select a provider, and/or insure against any failure to properly and/or timely process the workload.
A first aspect of the present invention provides a computer-implemented method for protecting against data loss in a networked computing environment, comprising: identifying a set of providers for processing a computing workload; determining a capability of each provider of the set of providers to process the computing workload according to a predetermined standard; calculating a risk score and an insurance cost for each provider based on the capability of each provider to process the computing workload according to the predetermined standard; generating a risk table that associates the risk score and the insurance cost with each corresponding provider, the risk table being stored in a computer storage device; selecting a particular provider of the set of providers to process the computing workload based on the risk table; and requesting an insurance policy based on the insurance cost associated with the particular provider in the risk table.
A second aspect of the present invention provides a system for protecting against data loss in a networked computing environment, comprising: a memory medium comprising instructions; a bus coupled to the memory medium; and a processor coupled to the bus that when executing the instructions causes the system to: identify a set of providers for processing a computing workload; determine a capability of each provider of the set of providers to process the computing workload according to a predetermined standard; calculate a risk score and an insurance cost for each provider based on the capability of each provider to process the computing workload according to the predetermined standard; generate a risk table that associates the risk score and the insurance cost with each corresponding provider, the risk table being stored in a computer storage device; select a particular provider of the set of providers to process the computing workload based on the risk table; and request the insurance policy based on an insurance cost associated with the particular provider in the risk table.
A third aspect of the present invention provides a computer program product for protecting against data loss in a networked computing environment, the computer program product comprising a computer readable storage media, and program instructions stored on the computer readable storage media, to: identify a set of providers for processing a computing workload; determine a capability of each provider of the set of providers to process the computing workload according to a predetermined standard; calculate a risk score and an insurance cost for each provider based on the capability of each provider to process the computing workload according to the predetermined standard; generate a risk table that associates the risk score and the insurance cost with each corresponding provider, the risk table being stored in a computer storage device; select a particular provider of the set of providers to process the computing workload based on the risk table; and request an insurance policy based on the insurance cost associated with the particular provider in the risk table.
A fourth aspect of the present invention provides a method for deploying a system for protecting against data loss in a networked computing environment, comprising: providing a computer infrastructure being operable to: identify a set of providers for processing a computing workload; determine a capability of each provider of the set of providers to process the computing workload according to a predetermined standard; calculate a risk score and an insurance cost for each provider based on the capability of each provider to process the computing workload according to the predetermined standard; generate a risk table that associates the risk score and the insurance cost with each corresponding provider, the risk table being stored in a computer storage device; select a particular provider of the set of providers to process the computing workload based on the risk table; and request an insurance policy based on the insurance cost associated with the particular provider in the risk table.
These and other features of this invention will be more readily understood from the following detailed description of the various aspects of the invention taken in conjunction with the accompanying drawings in which:
The drawings are not necessarily to scale. The drawings are merely schematic representations, not intended to portray specific parameters of the invention. The drawings are intended to depict only typical embodiments of the invention, and therefore should not be considered as limiting the scope of the invention. In the drawings, like numbering represents like elements.
Illustrative embodiments will now be described more fully herein with reference to the accompanying drawings, in which embodiments are shown. This disclosure may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the scope of this disclosure to those skilled in the art. In the description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of this disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Furthermore, the use of the terms “a”, “an”, etc., do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced items. The term “set” is intended to mean a quantity of at least one. It will be further understood that the terms “comprises” and/or “comprising”, or “includes” and/or “including”, when used in this specification, specify the presence of stated features, regions, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, regions, integers, steps, operations, elements, components, and/or groups thereof.
As indicated above, embodiments of the present invention relate to an approach for protecting (e.g., insuring) against data loss (e.g., due to SLA failures) in a networked computing environment (e.g., a cloud computing environment). In a typical embodiment, a risk table is created that associates cloud/solution providers with a corresponding risk factor and a cost of insuring the providers based on the risk factors. The risk factors are typically calculated using historical data that is based on (among other things), each provider's historical capability of honoring SLA terms, expected performance levels, etc. In any event, each provider may be associated with a cost of insuring that provider against failing to perform/process one or more future jobs/workloads. This allows a consumer who needs a workload to be processed to: view the risk table, select a provider, and/or insure against any failure to properly and/or timely process the workload.
In performing one or more of these functions, the aspects described herein allow both a cloud provider and/or cloud consumer to procure an insurance policy to protect against data loss/SLA failures within a computing infrastructure. Such a function may involve multiple elements such as: the ability to assess different insurance providers through the use of a ‘risk provider’ table, and then automatically apply an insurance policy to a workload processing request based on the results of this table.
It is understood in advance that although this disclosure includes a detailed description of cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.
Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.
Characteristics are as follows:
On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed, automatically without requiring human interaction with the service's provider.
Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).
Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active consumer accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.
Service Models are as follows:
Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited consumer-specific application configuration settings.
Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application-hosting environment configurations.
Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
Deployment Models are as follows:
Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.
Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.
Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).
A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.
Referring now to
In cloud computing node 10, there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.
Computer system/server 12 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.
As shown in
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.
Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.
System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM, or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
The embodiments of the invention may be implemented as a computer readable signal medium, which may include a propagated data signal with computer readable program code embodied therein (e.g., in baseband or as part of a carrier wave). Such a propagated signal may take any of a variety of forms including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium including, but not limited to, wireless, wireline, optical fiber cable, radio-frequency (RF), etc., or any suitable combination of the foregoing.
Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation. Memory 28 may also have an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.
Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a consumer to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via I/O interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.
Referring now to
Referring now to
Hardware and software layer 60 includes hardware and software components. Examples of hardware components include mainframes. In one example, IBM® zSeries® systems and RISC (Reduced Instruction Set Computer) architecture based servers. In one example, IBM system p® systems, IBM System x® servers, IBM BladeCenter® systems, storage devices, networks, and networking components. Examples of software components include network application server software. In one example, IBM WebSphere® application server software and database software. In one example, IBM DB2® database software. (IBM, system x, System p, System x, BladeCenter, WebSphere, and DB2 are trademarks of International Business Machines Corporation registered in many jurisdictions worldwide.)
Virtualization layer 62 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers; virtual storage; virtual networks, including virtual private networks; virtual applications and operating systems; and virtual clients.
In one example, management layer 64 may provide the functions described below. Resource provisioning provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and pricing provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. Consumer portal provides access to the cloud computing environment for consumers and system administrators. Service level management provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment provides pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA. Further shown in management layer is data loss protection, which represents the functionality that is provided under the embodiments of the present invention.
Workloads layer 66 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation; software development and lifecycle management; virtual classroom education delivery; data analytics processing; transaction processing; and consumer data storage and backup. As mentioned above, all of the foregoing examples described with respect to
It is understood that all functions of the present invention as described herein typically may be performed by the data loss protection functionality (of management layer 64, which can be tangibly embodied as modules of program code 42 of program/utility 40 (
It is reiterated that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, the embodiments of the present invention are intended to be implemented with any type of networked computing environment now known or later developed.
Referring now to
Along these lines, engine 70 may perform multiple functions similar to a general-purpose computer. Specifically, among other functions, engine 70 may (among other things): identify a set of providers 88A-N for processing a computing workload 74 (requested for processing by user/consumer 78); determine a capability (e.g., based on historical data 82A-N stored in one or more computer storage devices 80A-N) of each provider of the set of providers 88A-N to process the computing workload 74 according to a predetermined standard (e.g., SLA(s) 84A-N stored in computer storage device(s) 80A-N); calculate a risk score (e.g., based on an algorithm having factors such as a failure rate of each provider 88A-N, an importance of the computing workload 74, etc.) and an insurance cost for each provider 88A-N based the capability of each provider 88A-N o process the computing workload 74 according to the predetermined standard; 84A-N; generate a risk table 90 that associates the risk score and the insurance cost with each corresponding provider, the risk table being stored in a computer storage device (e.g., 80A-N); select a particular provider 88A of the set of providers 88A-N to process the computing workload 74 based on the risk table 90; and request an insurance policy (e.g., automatically based on a previous indication by consumer 78) based on an insurance cost associated with the particular provider 88A in the risk table 90.
This section will describe the above-discussed teachings in the context of an illustrative example. It is understood that this example (e.g., the values, etc., recited herein) are intended to be illustrative and that other embodiments may exist within the teachings described herein.
One aspect of the present invention involves the generation of a risk table. In a typical embodiment, the performance of multiple cloud providers (historical data loss, performance, SLA attainments, customer satisfaction, etc.) may be collected/tabulated and utilized for the calculation of a risk score (described below). When a job/workload is submitted for processing, a cross-reference may be performed against service level requirements for processing the workload. Along these lines, it may be determined what a consumer is willing to accept before seeking remuneration (e.g., filing an insurance claim). For example, a consumer may be willing to accept a 95.5% level of processor availability from a provider. Although the provider may theoretically be capable of providing a 97% level of availability, such a level may have been historically achieved in only one in every 20 occasions. Regardless, using such factors such as these, engine 70 will calculate a risk score for each provider. In so doing, an overall provider risk score may be calculated for each provider based on workload processing requirements, current provider availability/capacity, historical provider performance (e.g., for similar workloads), physical attributes such as weather in the location that the cloud provider is hosted, storms, hurricanes, etc.
In general, the calculation of a risk score may be made using a predetermined algorithm. Shown below is an illustrative example of one possible algorithm:
(% failures)+(difference of accepted SLA measures against provider documented SLA measures)+(the remuneration that the provider credits the consumer with in the case of failure)+(criticality of the cloud job submission)
This algorithm may then be normalized and scaled as appropriate to create a linear scale for comparison (e.g., an integer scale of 1 to 10). In any event, cost of insuring the providers (e.g., per workload, etc.) may then be determined. This can be determined based on independent insurance carriers and/or by cloud network itself.
It is understood that table 90 can be updated (e.g., in real time as workloads/jobs are received or on a periodic basis based on a sampling of prior performance over time). Regardless, table 90 may be sorted from lowest risk to highest risk (e.g., or any other sorting method), and the engine/system may be configured to select a provider having the lowest risk score. The system/engine may be further configured to automatically purchase insurance if a selected provider has a risk score above a predetermined threshold (e.g., “5” or greater) set by the consumer or the system/engine.
Referring now to
While shown and described herein as a data loss protection solution, it is understood that the invention further provides various alternative embodiments. For example, in one embodiment, the invention provides a computer-readable/useable medium that includes computer program code to enable a computer infrastructure to provide data loss protection functionality as discussed herein. To this extent, the computer-readable/useable medium includes program code that implements each of the various processes of the invention. It is understood that the terms computer-readable medium or computer-useable medium comprise one or more of any type of physical embodiment of the program code. In particular, the computer-readable/useable medium can comprise program code embodied on one or more portable storage articles of manufacture (e.g., a compact disc, a magnetic disk, a tape, etc.), on one or more data storage portions of a computing device, such as memory 28 (
In another embodiment, the invention provides a method that performs the process of the invention on a subscription, advertising, and/or fee basis. That is, a service provider, such as a Solution Integrator, could offer to provide data loss protection functionality. In this case, the service provider can create, maintain, support, etc., a computer infrastructure, such as computer system 12 (
In still another embodiment, the invention provides a computer-implemented method for data loss protection. In this case, a computer infrastructure, such as computer system 12 (
As used herein, it is understood that the terms “program code” and “computer program code” are synonymous and mean any expression, in any language, code, or notation, of a set of instructions intended to cause a computing device having an information processing capability to perform a particular function either directly or after either or both of the following: (a) conversion to another language, code, or notation; and/or (b) reproduction in a different material form. To this extent, program code can be embodied as one or more of: an application/software program, component software/a library of functions, an operating system, a basic device system/driver for a particular computing device, and the like.
A data processing system suitable for storing and/or executing program code can be provided hereunder and can include at least one processor communicatively coupled, directly or indirectly, to memory elements through a system bus. The memory elements can include, but are not limited to, local memory employed during actual execution of the program code, bulk storage, and cache memories that provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution. Input/output and/or other external devices (including, but not limited to, keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening device controllers.
Network adapters also may be coupled to the system to enable the data processing system to become coupled to other data processing systems, remote printers, storage devices, and/or the like, through any combination of intervening private or public networks. Illustrative network adapters include, but are not limited to, modems, cable modems, and Ethernet cards.
The foregoing description of various aspects of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed and, obviously, many modifications and variations are possible. Such modifications and variations that may be apparent to a person skilled in the art are intended to be included within the scope of the invention as defined by the accompanying claims.
