Eucalyptus: An Open-source Infrastructure for Cloud Computing
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


Eucalyptus: An Open-source Infrastructure for Cloud Computing






Total Views
Views on SlideShare
Embed Views



1 Embed 1 1


Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Why has this uptake occurred?

Eucalyptus: An Open-source Infrastructure for Cloud Computing Presentation Transcript

  • 1. Eucalyptus: An Open-source Infrastructure for Cloud Computing Rich Wolski Eucalyptus Systems Inc.
  • 2. Exciting Weather Forecasts
  • 3. Commercial Cloud Formation Eucalyptus - Confidential
  • 4. What is a cloud? SLAs Web Services Virtualization
  • 5. Cloudy issues
    • Public clouds are opaque
      • What applications will work well in a cloud?
    • Many of the advantages offered by Public Clouds appear useful for “on premise” IT
      • Self-service provisioning
      • Legacy support
      • Flexible resource allocation
    • What extensions or modifications are required to support a wider variety of services and applications?
      • Data assimilation
      • Multiplayer gaming
      • Mobile devices
  • 6. Open-source Cloud Infrastructure
    • Idea : Develop an open-source, freely available cloud platform for commodity hardware and software environments
      • Stimulate interest and build community knowledge
      • Quickly identify useful innovations
      • Act to dampen the “hype”
    • First-principles cloud implementation
      • Not a refactorization of previously developed technology
    • Linux or Anti-Linux?
      • Linux: open-source platform supporting all cloud applications changes the software stack in the data center
      • Anti-Linux: transparency of the platform makes it clear that clouds do not belong in the data center
  • 7. What’s in a name?
    • E lastic U tility C omputing A rchitecture L inking Y our P rograms T o U seful S ystems
    • Web services based implementation of elastic/utility/cloud computing infrastructure
      • Linux image hosting ala Amazon
    • How do we know if it is a cloud?
      • Try and emulate an existing cloud: Amazon AWS
    • Functions as a software overlay
      • Existing installation should not be violated (too much)
    • Focus on installation and maintenance
      • “ System Administrators are people too.”
  • 8. Goals for Eucalyptus
    • Foster greater understanding and uptake of cloud computing
      • Provide a vehicle for extending what is known about the utility model of computing
    • Experimentation vehicle prior to buying commercial services
      • Provide development, debugging, and “tech preview” platform for Public Clouds
    • Homogenize local IT environment with Public Clouds
      • AWS functionality locally makes moving using Amazon AWS easier, cheaper, and more sustainable
    • Provide a basic software development platform for the open source community
      • E.g. the “Linux Experience”
    • Not designed as a replacement technology for AWS or any other Public Cloud service
  • 9. Open-source Cloud Anatomy
    • Extensibility
      • Simple architecture and open internal APIs
    • Client-side interface
      • Amazon’s AWS interface and functionality (familiar and testable)
    • Networking
      • Virtual private network per cloud
      • Must function as an overlay => cannot supplant local networking
    • Security
      • Must be compatible with local security policies
    • Packaging, installation, maintenance
      • system administration staff is an important constituency for uptake
  • 10. Eucalyptus Infestation
  • 11. The EC2 API
    • Create and terminate virtual machines
      • Create == provision and not boot
      • Terminate == destroy and not halt
    • Image
      • initial root file system
    • Instance
      • Image + kernel + ramdisk + ephemeral disk + private IP + public IP
    • Create an image: upload a root file system
    • Run an instance: launch a VM with a specific
      • Image that has been uploaded (into S3)
      • Kernel and ramdisk that Amazon provides
      • Ephemeral disk that gets created and attached
  • 12. The S3 API
    • Bucket store: buckets and objects
      • Bucket: container for objects
      • Object: unit of storage/retrieval
      • Buckets are Created and Destroyed
      • Object are either Put or Get
    • Object storage is transactional
      • Last write prevails
    • Eventually consistent
      • Object writes will eventually be propagated
    • Buckets are access controlled
  • 13. The EBS API
    • Persistent Storage volumes that can be attached by VMs
      • Raw block devices (must be formatted by owner/user)
      • Persist across VM creation and termination
      • Cannot be shared by multiple VMs simultaneously
      • Not accessible across “availability zones” (virtual data centers)
    • Persistent virtual local disk
  • 14. All Together Now REST/SOAP EC2 S3 EBS EBS Availability Zone Availability Zone VM VM VM VM VM -- Public IP -- Security Groups -- Put/Get storage -- Eventual consistency
  • 15. RDMA and Cloud
    • RDMA between hosted Virtual Machines
      • Sockets are the only inter-VM IPC as of today
      • Requires virtualization support for RDMA for isolation
        • Hypervisors
        • libvirt
    • RDMA in the cloud platform: EBS
      • EBS performance and reliability is critical
      • Current connection is via iSCSI to SAN/JBOD
      • Requires authentication interface for RDMA
      • Also requires virtualization support
    • Suggestion: RDMA support in virtIO and XCP
      • Will speed adoption for on-premise clouds
  • 16. Thanks!
    • Thanks to our original research sponsors…
    • … and to our new commercial friends 805-845-8000 [email_address]