20
Highly available infrastructures based on Xen Björn Brundert

High Availability and Xen

Embed Size (px)

DESCRIPTION

Björn Brundert Presentation on High Availability

Citation preview

Page 1: High Availability and Xen

Highly available infrastructures based on Xen Björn Brundert

Page 2: High Availability and Xen

2

Disclaimer

- All statements given in this presentation do not represent

the opinion of the speakers company but only the

personal opinion and experience of the speaker himself

Page 3: High Availability and Xen

3

Introduction, overview and scope

1) Virtualization and high availability

2) Hardware requirements and planning

3) Available solutions today

4) Future prospect

5) Summary

6) Q&A

Page 4: High Availability and Xen

4

1) Virtualization and high availability

- Standalone server does not meet HA-SLAs

- HA means redundancy clustering

- Cluster means higher complexity: building and operating

- Dedicated hardware per HA-service becomes more and

more expensive

- Hardware, infrastructure components, ETH/FC ports,

rackspace, power, cooling

- Active/passive cluster unused ressources

Page 5: High Availability and Xen

- How to achieve HA

1) Virtualization and high availability

ApplicationApplication

Operating SystemOperating System

HardwareHardware

ApplicationApplication

Operating SystemOperating System

HardwareHardwareXen-HypervisorXen-Hypervisor Xen-HypervisorXen-Hypervisor

Black BoxBlack Box Black BoxBlack Box0101

0202

0303

0404

0505

0606

0707

0808

0909

1010

1111

1212

1313

1414

1515

1616

Page 6: High Availability and Xen

6

1) Virtualization and high availability

- Virtualization offers enourmous benefits

- Consolidation: multiple services on one hardware

- Higher flexibility through VM encapsulation and hardware

independence

- Application does not require to be „cluster-ready“

Page 7: High Availability and Xen

7

2) Hardware requirements and planning

- Key rules when thinking about HA

- Be as paranoid as you want

- There is never enough redundancy

- Murphy is with you

- Identify single points-of-failure

- Consolidation means also higher impact in case of an

outage

Page 8: High Availability and Xen

- Server:

HPProLiant

DL380G5

UID 1 2

1 2 3 4 5 6 7 8

DIMMS

PCIRISERCAGE

FANS

PROCPROC

PP

M

PP

M

INTERLOCK

OVERTEMP

MIRROR

ONLINESPARE

POWERSUPPLY

POWERSUPPLY

8

2) Hardware requirements and planning

HPProLiant

DL380G5

UID 1 2

1 2 3 4 5 6 7 8

DIMMS

PCIRISERCAGE

FANS

PROCPROC

PP

M

PP

M

INTERLOCK

OVERTEMP

MIRROR

ONLINESPARE

POWERSUPPLY

POWERSUPPLY

Page 9: High Availability and Xen

9

2) Hardware requirements and planning

HPProLiantDL380G5

UID 1 2

1 2 3 4 5 6 7 8

DIMMS

PCIRISERCAGE

FANS

PROCPROC

PP

M

PP

M

INTERLOCK

OVERTEMP

MIRROR

ONLINESPARE

POWERSUPPLY

POWERSUPPLY

HPProLiant

DL380G5

UID 1 2

1 2 3 4 5 6 7 8

DIMMS

PCIRISERCAGE

FANS

PROCPROC

PP

M

PP

M

INTERLOCK

OVERTEMP

MIRROR

ONLINESPARE

POWERSUPPLY

POWERSUPPLY

5 8

1 4Bla

deSyste

mc3000

Enclo

sure

HP

OA2

OA1

Rese

tActive

UID

NIC1

NIC2

UID

HP ProLiantBL465c G6

NIC1

NIC2

UID

HP ProLiantBL465c G6= ?

No!

Page 10: High Availability and Xen

10

2) Hardware requirements and planning

- I/O Cards:

NC340TFC1143 NC340TFC1143

FC NIC

Page 11: High Availability and Xen

11

2) Hardware requirements and planning

- Server

- Harddisk: RAID-configuration, spare

- Redundant I/O cards

- Redundant power supplies, redundant power cabeling and

redundant power circuits

- Redundant heartbeat-interconnect between nodes

Page 12: High Availability and Xen

12

2) Hardware requirements and planning

- Network components

- Redundant cabeling to server NICs- Active/passive bonding needs to be set up in OS

- Redundant switch or redundant switch modules

Page 13: High Availability and Xen

13

2) Hardware requirements and planning

- Storage components:

- RAID configuration with hot-spare harddrives

- Redundant controllers

- Redundant cabeling to every node

- Terminating on different HBAs

- Storage based replication

Page 14: High Availability and Xen

14

3) Available solutions today

- Several implementations of Xen in the wild

- XenServer by Citrix- Bundeled Hypervisor, out-of-the-box solution, including HA-

mechanism- Version 5.5 released on June 16- Free since Feburary 2009

- Xen in Linux-Distributions- different implementations of HA-mechanisms like Red Hat

Cluster Suite

Page 15: High Availability and Xen

15

4) Future prospect

- HA was only the first step

- Encapsulation is the key to more flexibility

- Fault-Tolerance is entering the market

- Xen Summit 2008: Demonstration of Kemari

- Marathon everRun VM: Available

- VMworld 2009 Europe: Announcement of VMware FT

Page 16: High Availability and Xen

16

4) Future prospect

- What is meant by FT?

- Virtual machine is running on two nodes simultaneously

- Primary machine is visible to the outside world

- Secondary machine is running as a shadow instance that

can take over any time no need for restarting the VM

HardwareHardware HardwareHardware

Xen-HypervisorXen-Hypervisor Xen-HypervisorXen-Hypervisor

VM 1VM 1 VM 2VM 2 VM 1VM 1 VM 2VM 2

Page 17: High Availability and Xen

17

4) Future prospect

- FT-mechanisms are on the roadmap for Xen 4.0

- Kemari (NTT, Japan): Unsupported version available

- Remus (UBC, Canada): Initial port to Xen unstable (3.4.0)

completed

Page 18: High Availability and Xen

18

5) Summary

- Virtualization brings more complexity to the infrastructure

- But: virtualization also brings more flexibility to the

infrastructure

- Obligatory redundant infrastructure for traditional cluster

systems can be „recycled“ and used for multiple OS

- High availability through encapsulation and hardware-

independence of OS as a virtual machine

- Fault-tolerance mechanisms are going to revolutionize

availability of stand-alone-servers

Page 19: High Availability and Xen

19

6) Q&A

- Any questions?

Page 20: High Availability and Xen

20

Thank you for your attention

For further questions feel free to contact me at

[email protected]