Browse Prior Art Database

Role Based SLA Mechanism for Private Cloud in a Box Solution

IP.com Disclosure Number: IPCOM000238586D
Publication Date: 2014-Sep-04
Document File: 2 page(s) / 41K

Publishing Venue

The IP.com Prior Art Database

Abstract

This invention describes SLA mechanism for private Cloud in a Box solution. Proposed invention takes into different persona that are using such Cloud-in-a-Box solution to build role specific SLAs.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 44% of the total text.

Page 01 of 2

Role Based SLA Mechanism for Private Cloud in a Box Solution

Background:


Private Cloud in a box is an integrated solution providing hardware/middleware/software that spans across the entire Cloud platform.

Because of the nature of such Cloud offerings a variety of users can use the provided solution simultaneously.

For example, a system administrator can manage and configure the physical machines (PM), chassis management modules (CMM), networking and storage elements.

A Cloud provider can setup hypervisors, monitoring and charging policies for IaaS Cloud users.

An IaaS Cloud user can deploy a Virtual Machine (VM) with specific CPU, RAM and disk capacity.

A PaaS user can develop his/her patterns or applications using the provided VMs.

A SaaS user can simply consume the end service, e.g., process transactions, query the databases etc.

Problem:


Since Cloud-in-a-Box can accommodate all these user roles, it is equally important to have service level agreement that can satisfy this broad variety of users/consumers.

While variety of SLAs can be offered as part of the Cloud solution, in this invention, the focus is only on reliability/availability related SLAs.

Existing availability SLAs for Cloud services are agnostic of the specific user role.

For example, 99.95% downtime SLA dictates the instances' availability ONLY to an IaaS user.

Unlike Cloud-in-a-Box type of solution, the full Cloud platform is not offered as a solution in such cases. As a result, it does not encompass all the user roles as described previously.

Another aspect of the same problem is, 99.95% availability on the underlying infrastructure does not necessarily translate to equivalent numbers for the PaaS and SaaS running on top of it.

For any solution built on top of this infrastructure, this number may not be useful.

Hence, violation of SLA becomes too frequent and affects business reputation.

This invention addresses the need for a role-based SLA when an entire Cloud platform is offered as a solution.

Prior Art:
1. Capturing adaptive B2B Service Relationships Management through a Generalized SLA Information Model http://phare.lip6.fr/phare_pub/author/papers/59.pdf
This paper proposes a UML based information model for capturing a generic flexible specification of services and Service Level Agreements.

Proposed UML models are static i.e., the authors do not consider how the system evolves with time.

In the dislcosed approach, analytic models that can capture stochastic behavior of underlying systems are used. Moreover, there is no discussion on how UML models can be applied for Cloud-in-a-Box type of product that integrates multiple Cloud user roles within the same solution.

The invention introduces role base SLA to differentiate the availability of a user's personal scope in a larger multi-tier system. The invention maintains a dependency graph of system components and analyzes workflow requirements of a given role to calculate a role-specific SLA. The SLA can be lever...