1 / 26

The Eucalyptus Open Source Cloud Computing System Daniel Nurmi et al, UCSB

The Eucalyptus Open Source Cloud Computing System Daniel Nurmi et al, UCSB. Presented by: Sanketh Beerabbi University of Central Florida. COP6087 - Cloud Computing. Introduction.

regan-kline
Télécharger la présentation

The Eucalyptus Open Source Cloud Computing System Daniel Nurmi et al, UCSB

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Eucalyptus Open Source Cloud Computing SystemDaniel Nurmi et al, UCSB Presented by: SankethBeerabbi University of Central Florida COP6087 - Cloud Computing

  2. Introduction • A cloud is a collection of networked resources configured such that users can request scalable resources (VMs, platforms, software services) deployed across a variety of physical resources. • Most cloud computing systems are proprietary and rely upon infrastructure that is invisible to the end users.

  3. Cloud Vs Grid • Cloud • Users get small fraction of resources. • No support for federation. • Resources are hidden. • Grid • Users get higher resources. • Federation is supported. • Resources are visible.

  4. Open Source Clouds • Commercial cloud service providers charge CPU time and bandwidth. • For large organizations, it’s more cost effective to purchase the hardware and create own cloud. • Researchers and academia need open standards. • More secure and flexible. • No vendor lock in.

  5. IaaS Platforms • Commercial: • Open Source:

  6. Eucalyptus • Open source architecture for implementing cloud functionality at the IaaS level. • Can be installed and deployed without modification to the existing infrastructure (From laptops to data centers) • Linux based, highly modular and compatible with Amazon AWS (uses AWS APIs).

  7. Architectural Overview 1 - Instances 2 - Networking 3 - Compute nodes 4 - Storage 5 - User interface 6 - Overall cloud platform

  8. Hierarchical Design

  9. Cloud Controller (CLC) • External interface to the cloud for users and administrators. • Performs high level resource scheduling and arbitration. • Lets users manipulate properties of instances and virtual networks. • Monitors system resources and components. • Provides user interface, handles authentication and protocol translation.

  10. CLC Services

  11. Cluster Controller (CC) • Acts as the front end for a cluster of machines within the cloud. • Receives requests from CLC to deploy instances. • Manages instance execution on specific NCs. • Controls virtual network available to instances. • Collects data about resources from a set of NCs.

  12. Node Controller (NC) • Present on every node that is designated for hosting VM instances. • Controls execution, inspection, and termination of VM instances. • Fetches, installs and cleans up local copies of instance images (kernel, the root file system, and the ramdisk image) • Reports physical resource availability and utilization to CCs.

  13. Storage Controller(Walrus) • A put/get storage service (similar to AWS S3) • Stores user data of any type. • Stores machine images and volume snapshots • Is available to any instance in any cluster. • Implements the REST and SOAP interfaces, which are compatible with S3

  14. Walrus Storage

  15. Virtual Networking • Every VM must have network connectivity with every other and partially to public Internet. • Public interface handles communication outside a given set of instances. • Private interface used only for inter-instance communication across availability zones. • Provides Isolation - Users have super user access to VM’s network interface and may cause interference with other VMs if unchecked.

  16. Virtual Networking 3 different modes: • Manually define static MAC and IP for each VM. • Directly attach VM interface to software Ethernet bridge and assign IPs via DHCP. • Fully managed by Eucalyptus: • VMs attach to user defined networks using VLAN tags and IP subnets. • CC acts as router between VM subnets. • Cross cluster VM communication via tunneling.

  17. Virtual Networking

  18. Instantiating process 1-Request a VM. 2-VM image pushed to CN 3- Disk image packaged for Hypervisor 4- The CN provides a virtual NIC with virtual MAC 5-DHCP on head node provides IP 6/7- VM starts/User can login via SSH

  19. Overall Architecture

  20. Perormance

  21. Advantages • Open source and modular- allows components to be modified or replaced. • Compatibility with AWS API allows Amazon EC2 users to transition easily. Existing AWS tools, images and scripts can be used with Eucalyptus. • Hybrid cloud capability: Users can move instances between Eucalyptus private cloud and Amazon public cloud to create a hybrid cloud.

  22. Comparision

  23. Comparison

  24. Comparision

  25. References • The Eucalyptus Open-source cloud computing system, Daniel Nurmi et al. • A Survey on Open-source Cloud Computing Solutions, P. T. Endo et al. • A Comparison and Critique of Eucalyptus, OpenNebula and Nimbus, P Sempolinski, 2010 • Source code available at: www.eucalyptus.com/download/eucalyptus/source

  26. Questions?

More Related