• Share
  • Email
  • Embed
  • Like
  • Private Content
What's Inside Your Cloud? IaaS Architecture and Implementation
 

What's Inside Your Cloud? IaaS Architecture and Implementation

on

  • 1,226 views

 

Statistics

Views

Total Views
1,226
Views on SlideShare
1,226
Embed Views
0

Actions

Likes
1
Downloads
24
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

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.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    What's Inside Your Cloud? IaaS Architecture and Implementation What's Inside Your Cloud? IaaS Architecture and Implementation Presentation Transcript

    • What’s Inside Your Cloud? IaaS Architecture and Implementation Rich Wolski, CTO Eucalyptus Systems May 22, 2012© 2012 Eucalyptus Systems, Inc. -- confidential
    • Exciting Weather Forecasts 315 M 1.0 B 16 M© 2012 Eucalyptus Systems, Inc. -- confidential
    • Is Cloud Computing ComputerScience?•  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•  Build from mature open source technologies –  J2EE, MySQL, Web Services are high quality and scalable as open source© 2012 Eucalyptus Systems, Inc. -- confidential
    • Eucalyptus - What’s in a Name?•  Elastic Utility Computing Architecture Linking Your Programs To Useful Systems•  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.”© 2012 Eucalyptus Systems, Inc. -- confidential
    • Eucalyptus ServiceComponents•  Cloud Controller (CLC) –  User request processing (except for Walrus), Credentials management, VM (instance) state management•  Walrus (S3) –  S3 user request processing, Append-only, Put/Get object storage•  Cluster Controller (CC) –  VM inventory, Network provisioning/security group implementation•  Storage Controller (SC) –  Block level, network attached storage (SAN and Linux)•  Node Controller (NC) –  Hypervisor interface and control, VM launch/decommissioning•  VMWare Broker –  Gateway between CC and ESX and/or vSphere for VMWare© 2012 Eucalyptus Systems, Inc. -- confidential
    • Service Architecture Service User Requests Delivery CLC Walrus CC SC CC SC CC SC NC/ NC/ NC/ NC/ NC/ VMWareB VMWareB VMWareB VMWareBVMWareB © 2012 Eucalyptus Systems, Inc. -- confidential
    • Eucalyptus Generations•  Eucalyptus 1.X (June 08 through Sep. 10) –  University code•  Eucalyptus 2.X (June 10 through Feb. 11) –  Commercial focus, early production•  Eucalyptus 3.X (present - ) –  Production operational improvements –  Full commercial feature set (almost)•  Few, if any features deprecated –  BitTorrent?© 2012 Eucalyptus Systems, Inc. -- confidential
    • Enterprise Cloud Features•  High-availability (HA) of the Eucalyptus Service –  Hot fail-over and repair for all components except NC•  AWS Identity and Access Management (IAM) API plus extensions for private clouds –  Quotas and metering•  Eucalyptus Block Storage improvements –  AWS Volume-backed instance API (persistent instances) “bootable” –  NetApp and JBOD support added to existing Dell Equallogic•  Full support for Windows images –  Seven different versions, AWS compatible authentication, sysprep, ephemeral disk•  Accounting/Usage reporting –  Charge-back interface linked to quotas© 2012 Eucalyptus Systems, Inc. -- confidential
    • Platform Features•  Image caching –  Fast instance starts using copy-on-write•  VMWare support –  Image preparation, support for vSphere 4.X, improved scale, more extensive deployment topologies•  Linux distro support –  RHEL 5 and RHEL 6, packages for Canonical LTS (Ubuntu 10.04)•  Automated QA –  Full QA sequence is 5 days (features + distros + hypervisors + deployment topologies + networking modes)•  Admin webUI•  Scriptable command-line admin tools•  Packaging, upgrade and dependency management•  Installation mechanism (package repositories) © 2012 Eucalyptus Systems, Inc. -- confidential
    • Web Service Stack Java Enterprise Bus (Mule) Object Persistence API L1 Object Cache (Hibernate) L2 Object Cache (Tree Cache) Object Persistence (Hibernate) DB Connections (Proxool) Distributed DB Connection (HA-JDBC) Local DB Connection (JDBC)© 2012 Eucalyptus Systems, Inc. -- confidential
    • High Availability•  Eliminate single point of failure –  Host failure –  Network connectivity failure (including network partitions)•  Tolerate as many multiple failure cases as possible•  Avoid data loss at all costs –  Fail stop is better than data loss•  Availability of the services that Eucalyptus offers –  Eucalyptus requests –  VM connectivity and storage –  Not VM HA -> application level•  Distributed Bootstrap layer for Group Management© 2012 Eucalyptus Systems, Inc. -- confidential
    • HA Web Service Architecture•  All Eucalyptus components are implemented as Web Services –  CLC, Walrus, SC, VMWare Broker– Java –  CC and NC - C•  CC and NC are each implemented in separate Axis2c service container•  CLC, Walrus, SC, and VMWare Broker share a web service stack and JVM when co-located© 2012 Eucalyptus Systems, Inc. -- confidential
    • PoC Configuration VM VM SC SC Wb Wb Walr Walr CLC us CLC us Web Service Web Service DB management DB management CC CC Linux Linux NC NC NC NC NC© 2012 Eucalyptus Systems, Inc. -- confidential Linux Linux Linux Linux Linux
    • Multi-component Failure VM VM SC SC Wb Wb Walr Walr CLC us CLC us Web Service Web Service DB management DB management CC CC Linux Linux NC NC NC NC NC© 2012 Eucalyptus Systems, Inc. -- confidential Linux Linux Linux Linux Linux
    • Production DeploymentCLC CLC Wal Wal CC CC VM VM SC SC b b NC NC NC NC NC Linux Linux Linux Linux Linux© 2012 Eucalyptus Systems, Inc. -- confidential
    • Group Membership andHeartbeat•  HA is from the perspective of the “master” CLC•  Jgroups determines which machines are “up” –  The network connecting the “up” machines is unpartitioned•  Heartbeat determines which services are available within the “up” group•  Back-up CLC monitors the “up” group to determine if it contains a master –  If not, it becomes the master•  Master and Back-up DBs kept synced –  Resync when failed CLC is restored© 2012 Eucalyptus Systems, Inc. -- confidential
    • Interesting Wrinkles•  CLC and Walrus have externally visible URLs –  DNS remapping service is built into the CLC•  What happens if the master loses connectivity with the user? –  Back-up may have an alternative path to user –  If DNS remaps, and the back-up becomes active, the system may experience a “split brain” •  Fail stop •  Arbitrator service•  Multi-failure can cause split brain –  Master fails over, new master fails before original back, original then brought up => fail stop© 2012 Eucalyptus Systems, Inc. -- confidential
    • What’s Next?•  Eucalyptus 3.1 (Q2) –  Refactoring for packaged plug-ins –  Postgres support•  Eucalyptus 3.2 (Q4) –  Feature release –  Possibilities •  ELB, Cloudwatch, Autoscaling •  Tags•  Eucalyptus 4 in 2013 and Eucalyptus 5 in 2014 –  Application features -> services and API –  Operational features -> ease of use, maintenance, performance•  Please help! – tell us what Eucalyptus needs and when it needs it© 2012 Eucalyptus Systems, Inc. -- confidential
    • Thanks! Questions?•  rich@eucalyptus.com•  @richwolski© 2012 Eucalyptus Systems, Inc. -- confidential