Profiling SLAs for cloud system infrastructures and user interactions

PeerJ Computer Science

Valentín Valero¹  M. Emilia Cambronero¹  Adrián Bernal¹  Pablo C. Cañizares²  Alberto Núñez³ 

[1] Albacete Research Institute of Informatics, Department of Computer Science, University of Castilla La Mancha, Albacete, Spain;School of Informatics, Autonomous University of Madrid, Madrid, Spain;School of Informatics, Complutense University of Madrid, Madrid, Spain;

关键词: Cloud;    SLAs;    Profit improvement;    Model development;    Design and simulation tools;   

DOI  :  10.7717/peerj-cs.513

来源: DOAJ

【 摘 要 】

Cloud computing has emerged as a cutting-edge technology which is widely used by both private and public institutions, since it eliminates the capital expense of buying, maintaining, and setting up both hardware and software. Clients pay for the services they use, under the so-called Service Level Agreements (SLAs), which are the contracts that establish the terms and costs of the services. In this paper, we propose the CloudCost UML profile, which allows the modeling of cloud architectures and the users’ behavior when they interact with the cloud to request resources. We then investigate how to increase the profits of cloud infrastructures by using price schemes. For this purpose, we distinguish between two types of users in the SLAs: regular and high-priority users. Regular users do not require a continuous service, so they can wait to be attended to. In contrast, high-priority users require a constant and immediate service, so they pay a greater price for their services. In addition, a computer-aided design tool, called MSCC (Modeling SLAs Cost Cloud), has been implemented to support the CloudCost profile, which enables the creation of specific cloud scenarios, as well as their edition and validation. Finally, we present a complete case study to illustrate the applicability of the CloudCost profile, thus making it possible to draw conclusions about how to increase the profits of the cloud infrastructures studied by adjusting the different cloud parameters and the resource configuration.

【 授权许可】

Unknown