14 Motivation (contd.) Cloud in Grid: Virtual Machine as a Node Job Requirement: Custom Execution Environment: Operating system Specific libraries Administrator Privilege But user need to submit the Virtual Machine each time he wants to run job.

15 Objective Provide custom environment to users to run their jobs through virtual machine. Users will be able to reuse their virtual machines. Only user will be able to use the virtual machine.

16 State of Art Globus Virtual Workspaces User request to power on virtual machine

17 State of Art(contd.) CernVM Minimal OS: contains only a minimal operating system required to bootstrap and initiate the experiment software. CernVM-FS: decouples the operating system from the experiment software life cycle. Pre-built and configured experiment software releases are centrally published. The releases are distributed efficiently on a large scale via a hierarchy of proxy servers or content delivery networks. Configuration and contextualization interfaces: configures the virtual machines to run correctly on the remote system. It mounts the software repositories before running the job.

25 Experimentations & Results (contd.) Making Virtual Machine Node Private: Condor checks START attribute from the configuration to decide when to start running jobs. START is modified to enforce that only jobs submitted from user s node can be executed on the virtual machine.

27 Experimentations & Results (contd.) Scenario 1: Remote Transfer Time to be live on the pool: As in this scenario, virtual machine image need to be transferred to the execution node, it takes 15 minutes on average to be live on the pool.

29 Experimentations & Results (contd.) Scenario 1: Remote Transfer Fault Tolerance: The virtual machine runs as a condor job. In case of The virtual machine runs as a condor job. In case of high load or low memory, condor can power off or migrate the virtual machine. Condor can checkpoint virtual machines.

30 Experimentations & Results (contd.) Scenario 1: Remote Transfer Pros: Powering on and powering off is simple. User is the owner. Privatizing is easy. Fault-tolerance. Cons: Time to join the pool. High network bandwidth. Limited to LAN.

32 Experimentation & Results Scenario 2: Pre- configured The virtual machine is shared between users. So, high mutual understanding between users is needed. The time to become live on pool is small. The virtual machine needs to be made private dynamically. Network bandwidth usage is normal.

33 Experimentations & Results (contd.) Scenario 2: Pre- configured Fault Tolerance: The virtual machine runs completely separated from the host operating system. They do not know each others load or usage. So, in case of high load on host system both the virtual machine and the host will crash.

35 Summary: Experimentations & Results (contd.) Scenario 1 Scenario 2 Power On Time to be live on Pool Privatizing Power Off Fault-Tolerance Network Usage Other user s influence NONE YES

36 Conclusions & Future Work Conclusions: Virtualization can be used in Grid to offer custom job execution environment to the users. The virtual machine can be submitted as a job or can be configured previously on execution node. Transparent method is required to power on, power off and privatize the virtual machine.

University of Victoria Faculty of Engineering Winter 2010 Work Term Report Dynamic Resource Distribution Across Clouds Department of Physics University of Victoria Victoria, BC Michael Paterson V00214440

Simulation and user analysis of BaBar data in a distributed cloud A. Agarwal, University of Victoria M. Anderson, University of Victoria P. Armstrong, University of Victoria A. Charbonneau, National Research

Dynamic Extension of a Virtualized Cluster by using Cloud Resources CHEP 2012 Thomas Hauth,, Günter Quast IEKP KIT University of the State of Baden-Wuerttemberg and National Research Center of the Helmholtz

First Workshop on Automated Control for Datacenters and Clouds (ACDC09) June 19th, Barcelona, Spain Elastic Management of Cluster based Services in the Cloud Rafael Moreno Vozmediano, Ruben S. Montero,

CLOUD COMPUTING When It's smarter to rent than to buy Is it new concept? Nothing new In 1990 s, WWW itself Grid Technologies- Scientific applications Online banking websites More convenience Not to visit

New Paradigms: Clouds, Virtualization and Co. EGEE08, Istanbul, September 25, 2008 An Introduction to Virtualization and Cloud Technologies to Support Grid Computing Distributed Systems Architecture Research

University of Victoria Faculty of Engineering Fall 2009 Work Term Report Evaluation of Nagios for Real-time Cloud Virtual Machine Monitoring Department of Physics University of Victoria Victoria, BC Michael

Cloud computing: utility computing over the Internet Taneli Korri Helsinki University of Technology tkorri@hut.fi Abstract Cloud computing has become a hot topic in the IT industry, as it allows people

The CC1 system Solution for private cloud computing 1 Outline What is CC1? Features Technical details Use cases By scientist By HEP experiment System requirements and installation How to get it? 2 What

5. Implementation Implementation of the trust model requires first preparing a test bed. It is a cloud computing environment that is required as the first step towards the implementation. Various tools

Research Challenges Overview May 3, 2010 Table of Contents I 1 What Is It? Related Technologies Grid Computing Virtualization Utility Computing Autonomic Computing Is It New? Definition 2 Business Business

Cloud Computing #6 - Virtualization Main source: Smith & Nair, Virtual Machines, Morgan Kaufmann, 2005 Today What do we mean by virtualization? Why is it important to cloud? What is the penalty? Current

The CC1 system Solution for private cloud computing 1 Outline What is CC1? Features Technical details System requirements and installation How to get it? 2 What is CC1? The CC1 system is a complete solution