SYNOPSIS ON Going Back and Forth: Efficient Multi deployment and Multi snapshotting on Clouds
SAMEER BANSOD NIKHIL RATHOD MUKESH BURADKAR KAMLESH ADHAU
UNDER THE GUIDANCE OF MR. SAGAR BADHIYE
DEPARTMENT OF COMPUTER TECHNOLOGY YESHWANTRAO CHAVAN COLLEGE OF ENGINEERING HINGNA ROAD, WANADONGRI, NAGPUR-441110 YEAR 2013-2014
2.4 Application State 5.1 Existing System 4. 3. Scope 5.2 Disadvantages 4.3 Cloud Infrastructure 4.Table of Contents
Title 1. Problem Definition Abstract Aim & Objective Literature Review 4. High Level Design 6. 4. 8. Plan of Action Software & Hardware Requirements
Page No.1 Data flow diagram 6.2 System Architecture 7.1 Advantage 6. 3 4 5 6 7 8 8 9 11 11 12
15 16 17
. starting from a set of VM images previously stored in a persistent fashion
Multisnapshotting : Many VM images that were locally modified need to be concurrently transferred to stable storage with the purpose of capturing the VM’s state for later use (e. for check pointing or off-line migration) to another cluster or cloud ..g.1. Problem Definition
To provide the basic functionalities for the use of Virtual Machine’s (VM’s) over the cloud given as: •
Multideployment : The operation of Infrastructure As A Service (IaaS) is the need to deploy a large number of VMs on many nodes of a datacentre at the same time.
. another challenge is to simultaneously take a snapshot of many images and transfer them to persistent storage to support management tasks. such as suspend-resume and migration. One of those challenges is the need to deploy a large number (hundreds or even thousands) of VM instances simultaneously. With datacenters growing rapidly and configurations becoming heterogeneous. It is based on a lazy transfer scheme coupled with object versioning that handles snapshotting transparently in a hypervisor-independent fashion. ensuring high portability for different configurations. Once the VM instances 1are deployed. This new model raises new challenges in the design and development of IaaS middleware.2. This paper addresses these challenges by proposing a virtual file system specifically optimized for virtual machine image storage. it is important to enable efficient concurrent deployment and snapshotting that are at the same time hypervisor independent and ensure a maximum compatibility with different configurations.Abstract
Infrastructure as a Service (IaaS) cloud computing has transform the way we think of acquiring resources by introducing a simple change: allowing users to lease computational resources from the cloud provider’s datacenter for a short time by deploying virtual machines (VMs) on these resources.
We want to reduce the contention on current system & allow maximum number of user to access VM’s with quick resume. Our aim is to create and implement load balancing mechanisms. restart & suspend operation.by anticipating their requirements we provide them without confliction. One resource can be available to the all the users .
.2. for managing numbers of users at the same time and within the context of time slices. A focus on the use of reusable frameworks to provide cost and times benefits. They’re focused on coming up with solutions that serve customer requirements today and anticipate future needs. we are creating cloud infrastructure which allows users to lease computational resources from cloud provider. Aim and Objectives
In this project.
a similar challenge applies to snapshotting the deployment: many VM images that were locally modified need to be concurrently transferred to stable storage with the purpose of capturing the VM state for later use (e. Since the user has complete control over the configuration of the VMs using on-demand deployments. For example. IaaS leasing is equivalent to purchasing dedicated hardware but without the long-term commitment and cost. Conventional snapshotting techniques rely on custom VM image file formats to store only incremental differences in a new file that depends on the original VM image as the backing file.g. Literature Survey
In recent years. Custom image formats are not standardized and can be used with specific hypervisors only. One of the commonly occurring patterns in the operation of IaaS is the need to deploy a large number of VMs on many nodes of a datacentre at the same time. When taking frequent snapshots for a large number of VMs. This can make the response time of the IaaS installation much longer than acceptable and erase the ondemand benefits of cloud computing. Infrastructure as a Service (IaaS) cloud computing has emerged as a viable alternative to the acquisition and management of physical resources. We refer to this pattern as multisnapshotting. for check pointing or off-line migration to another cluster or cloud).4. since it enables users to expand or shrink their resources according to their computational needs. multisnapshotting must be handled in a transparent and portable
. This problem is particularly acute for VM images used in scientific computing where image sizes are large (from a few gigabytes up to more than 10 GB). this pattern occurs when the user wants to deploy a virtual cluster that executes a distributed application or a set of environments to support a workflow. With IaaS. starting from a set of VM images previously stored in a persistent fashion. Furthermore. which limits the ability to easily migrate VMs among different hypervisors. We refer to this pattern as multideployment. by using external resources to complement their local resource base. The on-demand nature of IaaS is critical to making such leases attractive.. configurations are becoming more and more heterogeneous. Such a large deployment of many VMs at once can take a long time. Therefore. A typical deployment consists of hundreds or even thousands of such images. such approaches generate a large number of files and interdependencies among them. This emerging model leads to new challenges relating to the design and development of IaaS systems. Conventional deployment techniques broadcast the images to the nodes before starting the VM instances. a process that can take tens of minutes to hours. Once the VM instances are running. which are difficult to manage and which interfere with the ease-of-use rationale behind clouds. Leasing of computation time is accomplished by allowing users to deploy virtual machines (VMs) on the datacentre’s resources. not counting the time to boot the operating system itself. with growing datacentre trends and tendencies to federate clouds. users can lease storage and computation time from large datacentre’s.
One such requirement is the need to efficiently cope with massive unstructured data (organized as huge sequences of bytes .3 Cloud infrastructure IaaS platforms are typically built on top of clusters made out of loosely-coupled commodity hardware that minimizes per unit cost and favours low power over maximum speed. Cloud Computing is a “buzz word” around a wide variety of aspects such as deployment. Since the patterns are complementary. fine-grain data accesses . provisioning. Disk storage (cheap hard-drives with
. The role of virtualization in Clouds is also emphasized by identifying it as a key component. and network traffic consumption. It is not possible to build a scalable. Moreover. we investigate them in conjunction. 4.fashion that hides the interdependencies of incremental differences and exposes standalone VM images.2 Disadvantages To give less performance and storage space. Network traffic consumption also very high due to non concentrating on application status. these patterns may also generate high network traffic that interferes with the execution of applications on leased resources and generates high utilization costs for the user.1 Existing system The huge computational potential offered by large distributed systems is hindered by poor data sharing scalability. In addition to incurring significant delays and raising manageability issues. We addressed several major requirements related to these challenges. while keeping maximum portability among different hypervisor configurations. high-performance distributed data-storage service that facilitates data sharing at large scale. load balancing.BLOBs that can grow to TB) in very large-scale distributed systems while maintaining a very high data throughput for highly concurrent. This paper proposes a distributed virtual file system specifically optimized for both the multideployment and multisnapshotting patterns. and data and processing outsourcing. raw image files (understood by most hypervisors) to the outside. 4. storage space. Clouds have been defined just as virtualized hardware and software plus the previous monitoring and provisioning technologies. Our proposal offers a good balance between performance. while handling snapshotting transparently and exposing standalone. 4.
In order to provide persistent storage. which is used to store only minimal information about the state. Model 2 can further be simplified such that the VM state is represented only by the virtual disk attached to it (Model 3). there is an acute need for scalable storage. under the assumption that a fault-tolerant networking protocol is used that is able to re. the general case is usually simplified such that the application state is reduced to the sum of states of the VM instances . CPU registers. While several methods have been established in the virtualization community to capture the state of a running VM (CPU registers. in-transit network packets.store communication channels and resend lost information. Thus.capacities in the order of several hundred GB) is attached to each machine. Even so. saving the application state implies saving both the state of all VM instances and the state of all active communication channels among them.4 Application state The state of the VM deployment is defined at each moment in time by two main components: the state of each of the VM instances and the state of the communication channels between them (opened sockets. since the contents of RAM. such that they are able to host the VMs. Any in-transit network traffic is discarded. 4. RAM.). etc. such as configuration files that describe the environment and temporary files that were generated by the application. download. a dedicated repository is deployed either as centralized or as distributed storage service running on dedicated storage nodes. virtual topology. saving 2 GB of RAM for 1. in terms of both hardware and software. and so forth. delete. and the like does not need to be saved. in the most general case . The repository is responsible for storing the VM images persistently in a reliable fashion and provides the means for users to manipulate them: upload.compatible between different hypervisors. The machines are configured with proper virtualization technology. etc.000 VMs consumes 2 TB of space.
. Such an approach has two important practical benefits: (i) Huge reductions in the size of the state. while the machines are interconnected with standard Ethernet links. and (ii) Portability since the VM can be restored on another host without having to worry about restoring the state of hardware devices that are not supported or are in. Therefore. This information is then later used to reboot and reinitialize the software stack running inside the VM instance. which is unacceptable for a single one. state of devices.point-in-time deployment checkpoint. In order to avoid this issue.). the issue of capturing the global state of the communication channels is difficult and still an open problem. the necessary storage space can explode to huge sizes. For example. for VM instances that need large amounts of memory. With the recent explosion in cloud computing demands.
we describe an implementation on top of Blob Seer.5. Scope
A distributed virtual file system specifically optimized for both the multi deployment and multi snapshotting patterns. a versioning storage service specifically designed for high throughput under concurrency. We introduce a series of design principles that optimize multi deployment and multi snapshotting patterns and describe how our design can be integrated with IaaS infrastructures. Our proposal offers a good balance between performance. 5. To illustrate this point. raw image files. raw image files (understood by most hypervisors) to the outside.
. while handling snapshotting transparently and exposing standalone. storage space. and network traffic consumption. we investigate them in conjunction.1 ADVANTAGE A good balance between performance. Since the patterns are complementary. storage space. while handling snapshotting transparently and exposing standalone. and network traffic consumption. We show how to realize these design principles by building a virtual file system that leverages versioningbased distributed storage services.
SYSTEM FLOW DIAGRAM
RESOURCES RESOURCE1.6. High Level Design
GETTING AUTHORIZATION TO STORE RESOURCES
CONTROL API HYPERVISOR Request Requesting files LOCAL DISK FIG 1. SYSTEM ARCITECTURE
. RESOURCE 2
CENTRALIZED DATA STORAGE
and snapshotting individual VM instances or the whole set. Once a clone is created for each VM instance. let’s assume a scenario where a complex. followed by COMMIT. they can be either collectively or independently analyzed and modified in an attempt to
. However. subsequent global snapshots are performed by is. telling it when to start and stop VMs.7.Plan of Action
The simplified architecture of a cloud that integrates our approach is depicted in Figure 1. The typical elements found in the cloud are illustrated with a light background.suing each mirroring module a COMMIT to its corresponding clone. is performed in the following fashion. the cloud client interacts with the cloud middleware through a control API that enables a variety of management tasks. Running the application repeatedly and waiting for it to reach the point where the bug happens might be prohibitively expensive. and when to persistently store its local modifications (COMMIT) . when to create a new image clone (CLONE) . Since all image snapshots are independent entities. The cloud middleware interacts directly with both the hypervisor. For ex-ample. A global snapshot of the whole application. Both CLONE and COMMIT are control primitives that result in the generation of a new. The cloud middleware  in turn coordinates the compute nodes to achieve the afore-mentioned management tasks. A distributed versioning storage service that supports cloning and shadowing is deployed on the compute nodes and consolidates parts of their local disks into a common storage pool. The cloud client has direct access to the storage service and is allowed to upload and download images from it. CLONE is broadcast to all mirroring modules. and the mirroring module. the application right before the bug happens. Every uploaded image is automatically striped. telling it what image to mirror from the repository. The first time the snap-shot is taken. This approach enables snapshotting to be leveraged in interesting ways. which is responsible for ondemand mirroring and snapshotting and relies on both the local disk and the distributed versioning storage service to do so. fully independent VM image that is globally accessible through the storage service and can be deployed on other compute nodes or manipulated by the client. Each compute node runs a hypervisor  that is responsible for running the VMs. The reads and writes of the hypervisor are trapped by the mirroring module . including deploying an image on a set of compute nodes. Furthermore. distributed application needs to be debugged. while the elements that are part of our proposal are highlighted by a darker background. CLONE and COMMIT can also be exposed by the cloud middleware at the user level through the control API for fine-grained control over snapshotting. which involves taking a snapshot of all VM instances in parallel. dynamically adding or removing compute nodes from that set.
fix the bug. If the attempt was not successful.
. Such an approach is highly useful in practice at large scale because complex synchronization bugs  tend to appear only in large deployments and are usually not triggered during the test phase. the approach can continue iteratively until a fix is found. the application can safely resume from the point where it left. which is usually performed at smaller scale. Once this fix is made.
1 Hardware requirement : CPU type Clock speed Ram size Hard disk capacity : Dual Core : 2.6) : MS-Access : Ms-Office
.8.65 GHz : 2 GB : 40 GB
8. Software And Hardware Requirements
8.2 Software requirement : Operating System: Windows Language Back End Documentation : JAVA(JDK-1.
Freeman. R. Zaharia. G. 2000.inria.I.adaptive deployment of remote executions. Rabkin. Afshin Rostamizadeh. R. Patterson. G.fr/docs/00/57/06/82/PDF/final-paper. pages 91 K. Joseph. In CCA’08: Proceedings of the 1st Conference on Cloud Computing and Its Applications. Griffith. Katz.Ameet Talwalkar (2012) Foundations of Machine Learning.4. B.pdf Mehryar Mohri.A. ACM. Keahey and T. Konwinski.References :
Going Back and Forth: Efficient Multi deployment and Multi snapshotting on Clouds: www. Taktuk. the MIT Press ISBNhttp://hal. D. Armbrust. In HPDC’09: Proceedings of the 18th ACM International Symposium on High Performance Distributed Computing.A. A view of cloud computing. GA.nimbusproject. Atlanta. Richard.53:50 327.org/files/nicolae_hpdc2011. Huard. Claudel. and O. Fox. A.pdf M.com/blog/2013/09/19/red-hat-teams-up-with-dotcloud-topromote-open-hyperviper-alternative/
. 2008. A.  Hypervisor Alternative: http://siliconangle. Stoica. Science clouds: Early experiences in cloud computing for scientific applications. Commun.USENIX Association. Lee. and M.
Number of copies -. Bottom : 1. Page nos. Subtitles Times New Roman 12. Written matter – Times New Roman 12 (justified) Line spacing – 1. should be at the center of bottom of each page. The paper should be A4 size with margins: Top: 1”.5 Paragraph spacing – 2 lines 4.5” .Guidelines
1.02 (Project guide + Project Coordinator)
. 2.25” 5. Report should be spiral bound with white plastic cover pages only. 3. Right : 1. bold. Headings in the chapters should have size Times New Roman 14.2” . bold. left aligned. 6. center. Left : 1.
.7. Seminar report should be as per the guidelines only.