Formally Verified Scalable Look Ahead Planning For Cloud Resource Management

Abstract

In this paper, we propose and implement a distributed autonomic manager that maintains service level agreements (SLA) for each application’ scenario. The proposed autonomic manager supports SLAs by configuring the bandwidth ratios for each application scenario and uses an overlay network as an infrastructure. The most important aspect of the proposed autonomic manager is its scalability which allows us to deal with geographically distributed cloud-based applications and a large volume of computation. This can be useful in look ahead optimization and in adaptations using complex models, such as machine learning. We formally prove the safety and liveness properties of the implemented distributed algorithms. Through experiments on Amazon AWS cloud, using two different use cases, we demonstrate the elasticity and flexibility of the autonomic manager as a measure of its applicability to different cloud applications with different types of workloads. Experiments also demonstrate that increasing the size of a look ahead window, up to a certain size, improves the accuracy of the adaptation decisions up to 50%.

An AHP based Task Scheduling and Optimal Resource Allocation in Cloud Computing

“…In terms of CPU utilization, preparation time, and energy output, it also achieves preferred execution to the board's current asset management plan [11]. Greedy method named MESA is recommended due to the high computing complexity of addressing the MINLP problem [18] in order to arrive at the best solution [13]. Also, advanced metaheuristic models are in need to proceed with optimal scheduling process.…”

An Autonomous Multi-Agent Framework using Quality of Service to prevent Service Level Agreement Violations in Cloud Environment

“…SLA can be defined as a formal agreement that provides information regarding the quality of every nonfunctional requirement (NFR) of a service [26]. A formal procedure is followed in cloud computing that if there is any SLA violation encountered in the workload execution process, then penalties are provided to the service providers [27]. When there are no violations of SLA for different workload executions, then rewards are provided either to the customers or service providers after evaluations [28].…”