High Availability in 37 Easy Steps
•Télécharger en tant que ODP, PDF•
16 j'aime•6,785 vues
High Availability can be a curiously nebulous term, and most people probably don't care about it until they can't access their online banking service, or their plane crashes. This presentation examines some of the considerations necessary when building highly available computer systems, then focuses on the HA infrastructure software currently available from the Corosync/OpenAIS, Linux-HA and Pacemaker projects. Originally presented at Linux Users Victoria in April 2010 (http://luv.asn.au/2010/04/06)
![High Availability in 37 Easy Steps Tim Serong Senior Clustering Engineer [email_address]](https://image.slidesharecdn.com/highavailabilityin37easysteps-100407061928-phpapp02/85/high-availability-in-37-easy-steps-1-320.jpg)
![Agenda ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à High Availability in 37 Easy Steps
Similaire à High Availability in 37 Easy Steps (20)
Dernier
Dernier (20)
High Availability in 37 Easy Steps
- 1. High Availability in 37 Easy Steps Tim Serong Senior Clustering Engineer [email_address]
- 5. What is High Availability?
- 6. What is High Availability? “ High availability is a system design protocol and associated implementation that ensures a certain degree of operational continuity during a given measurement period.” http://en.wikipedia.org/wiki/High_Availability
- 8. Decrease MTTR (redundant hardware + software) What is High Availability? Availability = MTTF MTTF + MTTR
- 9. What is High Availability? (hopefully your hardware is better than this)
- 12. High Availability in 37 Easy Steps
- 14. High Availability in 37 Easy Steps
- 15. High Availability is a Process, not a Product
- 16. What is High Availability? (hopefully you hired this sysadmin) http://xkcd.com/705/
- 19. How good is your system already?
- 20. Within what limits can you operate?
- 21. Please, for the love of Eris, keep it simple.
- 22. System Design Considerations Dual F/C Ethernet RAID File Server Client Network
- 23. System Design Considerations Dual F/C Ethernet Reasonably Highly Available, Most of the Time RAID File Server Client Network
- 27. Software can still fail
- 28. System Design Considerations Dual F/C Ethernet Dual F/C Ethernet Private Network “ File Server” RAID Node 1 Client Network Node 2
- 29. System Design Considerations Dual F/C Ethernet Dual F/C Ethernet Private Network “ File Server” Node 2 takes over when Node 1 fails RAID Node 1 Client Network Node 2
- 31. Who's the boss if the two nodes get confused?
- 32. STONITH to the rescue
- 35. Set STONITH action to power off (not reset).
- 36. Get a third node.
- 37. Test, test , test!
- 50. HA Clustering Software http://clusterlabs.org/wiki/Architecture
- 53. Pacemaker 1.x on Corosync 1.x (+ OpenAIS 1.x)
- 54. HA Clustering Software Linux Kernel (SUSE only) (diagram courtesy of Lars Marowsky-Brée) ext3, XFS OCFS2 cLVM2 Local Disks SAN FC(oE), iSCSI DRBD Multipath IO DLM SCTP TCP UDP multicast UDP multicast Ethernet Infiniband Bonding SAP MySQL libvirt Xen Apache iSCSI Filesystems IP address DRBD clvmd Ocfs2_controld dlm_controld YaST2 c DRBD c OpenAIS MPIO LVS Resource Agents LSB init STONITH LRM ... DRAC iLO SBD Fencing Web GUI Python GUI CRM Shell CIB Policy Engine Pacemaker OpenAIS
- 56. ...and vastly more flexible # crm configure show primitive IP ocf:heartbeat:IPaddr params ip="192.168.1.50" op monitor interval="5min" primitive FS ocf:heartbeat:Filesystem params device="/dev/sda1" directory="/data1" fstype="ext3" op monitor interval="60s" group ip-with-fs IP FS location prefer-node1 ip-with-fs 100: node1
- 57. HA Clustering Software Network Links Clients Storage (diagram courtesy of Lars Marowsky-Brée) Kernel Xen VM 1 LAMP Apache IP ext3 Kernel Kernel Corosync + openAIS Pacemaker DLM cLVM2+OCFS2 Xen VM 2
- 59. crm(live)# cib new sandbox
- 60. INFO: sandbox shadow CIB created
- 61. crm(sandbox)# cib cibstatus load live
- 62. crm(sandbox)# cib cibstatus op monitor IP not_running
- 64. ptest[12971]: 2010/04/05_07:43:36 WARN: unpack_rsc_op: Processing failed op IP_monitor_300000 on hex-14: not running (7)
- 67. Package state
- 68. DLM/OCFS2 state
- 70. CIB history
- 71. Parses core dump reports (needs debuginfo packages!)
- 72. ...into a single tarball for subsequent analysis
- 74. #linux-cluster
- 76. Heartbeat in maintenance mode