Cost and Benefit of the SLA Mapping Approach for Defining Standardized Goods in Cloud Computing Markets
Due to the large variety in computing resources and, consequently, the large number of different types of Service Level Agreements (SLAs), any market for computing resources faces the potential problem of a low market liquidity. To counteract this problem, offering a set of standardized computing resources is appropriate. Each of these standardized computing resources is defined through an SLA template. An SLA template defines the structure of an SLA, the attributes, the names of the attributes, and the attribute values. Since these SLA templates are currently static, they cannot reflect changes in users' needs. To address this shortcoming, we present the novel approach of adaptive SLA matching. This approach adapts SLA templates based on SLA mappings by allowing Cloud users to define mappings between public SLA templates, which are available in the Cloud market, and their private SLA templates, which are used for various in-house business processes of the Cloud user. Besides showing how public SLA templates adapt to the demand of users, we also analyze the benefits and costs of this approach. Costs are incurred every time a user has to define a new SLA mapping to a public SLA template due to its adaptation. In particular, within this paper, we investigate the cost depending on the use of different public SLA template adaptation methods. The simulation results show that the use of heuristics within adaptation methods helps balancing the cost and benefit of the SLA mapping approach.
|Date of creation:||Dec 2010|
|Date of revision:||Dec 2010|
|Publication status:||Published in UCC 2010, International Conference on Utility and Cloud Computing, Chennai, India, December 2010.|
|Contact details of provider:|| Postal: 599 Gwanak-Ro, Gwanak-Gu, Seoul 151-744|
Web page: http://temep.snu.ac.kr/
More information through EDIRC
When requesting a correction, please mention this item's handle: RePEc:snv:dp2009:201069. See general information about how to correct material in RePEc.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: (Jorn Altmann)
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
If references are entirely missing, you can add them using this form.
If the full references list an item that is present in RePEc, but the system did not link to it, you can help with this form.
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your profile, as there may be some citations waiting for confirmation.
Please note that corrections may take a couple of weeks to filter through the various RePEc services.