Un planificador de tres niveles para la ejecución de experimentos científicos en Clouds federados (A Three-level Scheduler to Execute Scientific Experiments on Federated Clouds)

Elina Pacini (epacini@gmail.com)1, Cristian Mateos (cmateos@conicet.gov.ar)2, Carlos García Garino (cgarcia@itu.uncu.edu.ar)3


1ITIC Research Institute, Facultad de Ciencias Exactas y Naturales, UNCuyo University & CONICET, Mendoza, Argentina
2ISISTAN-CONICET, UNICEN University, Tandil, Buenos Aires, Argentina
3ITIC Research Institute & Facultad de Ingeniería, UNCuyo University, Mendoza, Argentina

This paper appears in: Revista IEEE América Latina

Publication Date: Oct. 2015
Volume: 13,   Issue: 10 
ISSN: 1548-0992


Abstract:
For executing current simulated scientific experiments it is necessary to have huge amounts of computing power. A solution path to this problem is the federated Cloud model, where custom virtual machines (VM) are scheduled in appropriate hosts belonging to different providers to execute such experiments, minimizing response time. In this paper, we study schedulers for federated Clouds. Scheduling is performed at three levels. First, at the broker level, datacenters are selected by their network latencies via three policies ‑Lowest-Latency-Time-First, First-Latency-Time-First, and Latency-Time-In-Round‑. Second, at the infrastructure level, two Cloud VM schedulers based on Ant Colony Optimization (ACO) and Particle Swarm Optimization (PSO) are implemented. At this level the scheduler is responsible for mapping VMs to datacenter hosts. Finally, at the VM level, jobs are assigned for execution into the preallocated VMs. We evaluate, through simulated experiments, how the proposed three-level scheduler performs w.r.t. the response time delivered to the user as the number of Cloud machines increases, a property known as horizontal scalability.

Index Terms:
Scientific experiments, Federated Cloud, Scheduling, Ant colony optimization, Particle swarm optimization   


Documents that cite this document
This function is not implemented yet.


[PDF Full-Text (525)]