What Eucalyptus High Availability Will Provide YOU - Lightning Webinar Series #3
 

What Eucalyptus High Availability Will Provide YOU - Lightning Webinar Series #3

on

  • 956 views

 

Statistics

Views

Total Views
956
Views on SlideShare
956
Embed Views
0

Actions

Likes
1
Downloads
16
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 Eucalyptus High Availability Will Provide YOU - Lightning Webinar Series #3 What Eucalyptus High Availability Will Provide YOU - Lightning Webinar Series #3 Presentation Transcript

    • What Eucalyptus High Availability Will Provide YOU Tim Cramer VP Engineering1 © 2012 Eucalyptus Systems, Inc.
    • Eucalyptus Multi-tiered Service Architecture Service User Requests Delivery User Transactions Inventory and Inventory and Inventory and Scheduling Scheduling SchedulingActualization Actualization Actualization Actualization Actualization2 © 2012 Eucalyptus Systems, Inc.
    • Eucalyptus Components • 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 VMWare3 © 2012 Eucalyptus Systems, Inc.
    • Component Architecture Service User Requests Delivery CLC Walrus CC SC CC SC CC SC NC/VMWareB NC/VMWareB NC/VMWareB NC/VMWareBNC/VMWareB4 © 2012 Eucalyptus Systems, Inc.
    • 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 level5 © 2012 Eucalyptus Systems, Inc.
    • 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-located6 © 2012 Eucalyptus Systems, Inc.
    • 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 Linux Linux Linux Linux Linux7 © 2012 Eucalyptus Systems, Inc.
    • 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 Linux Linux Linux Linux Linux8 © 2012 Eucalyptus Systems, Inc.
    • Production CLC CLC SC SC CC CC Wal Wal VMb VMb NC NC NC NC NC Linux Linux Linux Linux Linux9 © 2012 Eucalyptus Systems, Inc.
    • Group Membership and Heartbeat • HA is from the perspective of the “master” CLC • Jgroups determines which machines are “up” • 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 restored10 © 2012 Eucalyptus Systems, Inc.
    • Eucalyptus 3.1 – Repo Structure11 © 2012 Eucalyptus Systems, Inc.
    • Thank you. Questions? Tim Cramer tjcramer@eucalyptus.com© 2012 Eucalyptus Systems, Inc.
    • 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 stop13 © 2012 Eucalyptus Systems, Inc.