G-SLAM – The Anatomy of the Generic SLA Manager

Gonzalez, Miguel Angel Rojas; Chronz, Peter; Lu, Kuan; Yaqub, Edwin; Fuentes, Beatriz; Castro, Alfonso Peter; Foster, Howard G.; Rueda, Juan Lambea; Chimeno, Augustín Escámez

doi:10.1007/978-1-4614-1614-2_11

Cited by 3 publications

(1 citation statement)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The GSLAM (Figure 1) provides a generic architecture that can be used across different domains and use cases to manage the entire SLA life cycle, including activities such as SLAs modeling, negotiation, provisioning, resources outsourcing, monitoring and adjustment. Gonzalez et al (2011) argued that the GSLAM is an orchestrator of the generic components. It could provide interoperability and separates the SLAMs from specific representations of an SLA or SLA template.…”

Section: Openstack Sla Management Frameworkmentioning

confidence: 99%

QoS-Based Resource Allocation Framework for Multi-Domain SLA Management in Clouds

Yahyapour

Wieder

et al. 2013

STCC

Self Cite

View full text Add to dashboard Cite

In clouds, current virtualization technologies of IaaS enable the live migration of running VMs to achieve load balancing, fault-tolerance and hardware consolidation in data centers. However, the downtime / service unavailability due to live migration may be substantial with relevance to the customers' expectations on responsiveness, as the latter are declared in established SLAs, which define all relevant aspects of the services between service provider and customer. Moreover, the service unavailability may cause significant (potentially exponential) SLA violation penalties to its associated higher-level domains (e.g., PaaS and SaaS). Therefore, in order to deliver high availability service, VM live migration should be arranged and managed carefully. In this paper, we present the OpenStack version of Generic SLA Manager, alongside its strategies for VM selection and allocation during live migration of VMs. Based on the proposed autonomous SLA violation-filtering framework, we simulate a use case where IaaS (OpenStack-SLAM) and PaaS (OpenShift) are combined; and assess performance and efficiency of the aforementioned VM placement strategies, when a multi-domain SLA pricing & penalty model is involved. We find that our proposal is efficient in managing trade-offs between the operational objectives of service providers (including financial considerations) and the customers' expected QoS requirements.

show abstract

Section: Openstack Sla Management Frameworkmentioning

confidence: 99%