Share
Create bookmark
The Linux Enterprise Cluster
Build a Highly Available Cluster with Commodity Hardware and Free Software
Do you like this document?
Notes
Please login to add notes
- Technical Reviewers
- Acknowledgments
- + Introduction
- + Primer
- PART I: Cluster Resources
-
+
1: Starting Services
-
+
2: Handling Packets
-
+
3: Compiling the Kernel
- PART II: High Availability
-
+
4: Synchronizing Servers with rysnc and SSH
- rsync
- + Open SSH 2 and rsync
-
+
Two-Node SSH Client-Server Recipe
- Create a User Account That Will Own the Data Files
- Configure the Open SSH2 Host Key on the SSH Server
- Create a User Encryption Key for This New Account on the SSH Client
- Copy the Public Half of the User Encryption Key from the SSH Client to the SSH Server
- Test the Connection from the SSH Client to the SSH Server
- Using the Secure Data Transport
- Improved Security
- rsync over SSH
- Copying a Single File with rsync
- rsync over Slow WAN Connections
- Scheduled rsync Snapshots
- ipchains/iptables Firewall Rules for rsync and SSH
- In Conclusion
-
+
5: Cloning Systems with SystemImager
- + SystemImager
-
+
SystemImager Recipe
- Install the SystemImager Server Software on the SystemImager Server
- Using the Installer Program from SystemImager
- Install the SystemImager Client Software on the Golden Client
- Create a System Image of the Golden Client on the SystemImager Server
- Make the Primary Data Server into a DHCP Server
- Create a Boot Floppy for the Golden Client
- Start rsync as a Daemon on the Primary Data Server
- Install the Golden Client System Image on the New Clone
- Post-installation Notes
- + Performing Maintenance: Updating Clients
- In Conclusion
-
+
6: Heartbeat Introduction and Theory
-
+
7: A Sample Heartbeat Configuration
- Recipe
- Preparations
- Step 1: Install Heartbeat
- Step 2: Configure /etc/ha.d/ha.cf
- + Step 3: Configure /etc/ha.d/haresources
- Step 4: Configure /etc/ha.d/authkeys
- Step 5: Install Heartbeat on the Backup Server
- Step 6: Set the System Time
- + Step 7: Launch Heartbeat
- Stopping and Starting Heartbeat
- Monitoring Resources
- In Conclusion
-
+
8: Heartbeat Resources and Maintenance
- + The Haresources File Syntax
- + Load Sharing with Heartbeat
- Operator Alerts: Audible Alarm
- Operator Alerts: Email Alerts
-
+
Heartbeat Maintenance
- Changing Heartbeat Configuration Files
- Server Maintenance and the Heartbeat auto_failback Option
- Forcing the Primary Server into Standby Mode
- Tuning Heartbeat’s Deadtime Value
- Informational Messages in Heartbeat’s Log
- Failover and Respawn (Automatically Restarting Failed Resources)
- License Manager Failover
- In Conclusion
-
+
9: Stonith and ipfail
- PART III: Cluster Theory and Practice
-
+
10: How to Build a Linux Enterprise Cluster
-
+
Steps for Building a Linux Enterprise Cluster
- NAS Server
- Kernel Netfilter and Kernel Packet Routing
- Cloning a Linux Machine
- Cluster Naming Scheme
- Applying System Configuration Changes to All Nodes
- Building an LVS-NAT Cluster
- Building an LVS-DR Cluster
- Installing Software to Remove Failed Cluster Nodes
- Installing Software to Monitor the Cluster Nodes
- Monitoring the Performance of Cluster Nodes
- Updating Software on Cluster Nodes and Servers
- Centralizing User Account Administration
- Installing a Printing System
- Installing a Highly Available Batch Job-Scheduling System
- Purchasing the Cluster Nodes
- In Conclusion
-
+
Steps for Building a Linux Enterprise Cluster
-
+
11: The Linux Virtual Server: Introduction and Theory
-
+
12: The LVS-NAT Cluster
- + 13: The LVS-DR Cluster
-
+
14: The Load Balancer
-
+
15: The High-Availability Cluster
- Redundant LVS Directors
- High-Availability Cluster Design Goals
- The High-Availability LVS-DR Cluster
- + Introduction to ldirectord
-
+
LVS, Heartbeat, and ldirectord Recipe
- Hide the Loopback Interface
- Install the Heartbeat on a Primary and a Backup Director
- Install ldirectord and Its Required Software Components
- Install ldirectord
- Test Your ldirectord Installation
- Create the ldirectord Configuration File
- Create the Health Check Web Page
- Start ldirectord Manually and Test Your Configuration
- Add ldirectord to the Heartbeat Configuration
- Stateful Failover of the IPVS Table
- Modifications to Allow Failover to a Real Server Inside the Cluster
- In Conclusion
-
+
16: The Network File System
- Lock Arbitration
- + The Lock Arbitrator
- The Network Lock Manager (NLM)
- + NLM and Kernel Lock Arbitration
- NFS and File Lock (dotlock) Arbitration
- Finding the Locks Held by the Linux Kernel
- + Performance Issues with NFS-Bottlenecks and Perceptions
- Managing Lock and GETATTR Operations in a Cluster Environment
- Managing Attribute Caching
- + Managing Interactive User Applications and Batch Jobs in a Cluster Environment
- Measuring NFS Latency
- Measuring Total I/O Operations
- Achieving the Best NAS Performance Possible
- + NFS Client Configuration Options
- Developing NFS
- Additional Starting Points for Information on Linux and NFS
- In Conclusion
- PART IV: Maintenance and Monitoring
-
+
17: The Simple Network Management Protocol and Mon
- + Mon
- Where to Run Mon
-
+
Basic Mon Recipe
- Step 1: Compile and Install the fping Package
- Step 2: Install the SNMP Package
- Step 3: Install the Required CPAN Modules for Mon
- Step 4: Install the Mon Software
- Step 5: Create the /etc/mon/mon.cf Configuration File
- Step 6: Test by Running the fping.monitor and mail.alert Scripts Manually
- Step 7: Create the Mon Log Directory and Mon Log File
- Step 8: Start the Mon Program in Debugging Mode and Test
- + Mon and SNMP “Proof of Concept” Recipe
- + Mon and SNMP “Real-World” Recipe
- Email Alerts from Mon
- + Creating Your Own SNMP Script
- Monitoring Your SNMP Script with Mon
- Things to Monitor with SNMP Monitoring Scripts
- Forcing a Stonith Event with Mon
- Forcing a Heartbeat Failover with Mon
- In Conclusion
- + 18: Ganglia
-
+
19: Case Studies in Cluster Administration
- + Administering Accounts Without Active Directory
- + Building a Reliable Cluster Account Authentication Mechanism
-
+
Building a Fault-Tolerant Print Spooler
- Cluster Nodes and Job Ordering
- LPRng: A Linux Enterprise Cluster Printing System
- Cluster Nodes and Print Jobs
- Building the Cluster Printing System Based on LPRng
- Install LPRng on the Central Print Server
- Install LPRng on the Cluster Nodes
- Modify the /etc/printcap.local File on the Cluster Nodes
- Modify the /etc/printcap File on the Central Print Server
- Managing Print Jobs on the Central Print Server
- Managing Print Jobs from the Cluster Nodes
- + Rebooting Nodes for Preventative Maintenance
- Sending and Receiving Email in a Cluster Environment
- + Creating a Batch Job-Scheduling System with No Single Point of Failure
- In Conclusion
-
+
20: The Linux Cluster Environment
- + A: Downloading Software from the Internet (from a Text Terminal)
- B: Troubleshooting with the tcpdump Utility
- + C: Adding Network Interface Cards to Your System
-
+
D: Strategies for Dependency Failures
- E: Other Potential Cluster Filesystems and Lock Arbitration Methods
-
+
F: LVS Clusters and the Apache Configuration File
- Index
- Updates
- About the CD-ROM
- CD License Agreement
The Linux Enterprise Cluster explains how to take a number of inexpensive computers with limited resources, place them on a normal computer network, and install free software so that the computers act together like one powerful server. This makes it possible to build a very inexpensive and reliable business system for a small business or a large corporation. The book includes information on how to build a high-availability server pair using the Heartbeat package, how to use the Linux Virtual Server load balancing software, how to configure a reliable printing system in a Linux cluster environment, and how to build a job scheduling system in Linux with no single point of failure. The book also includes information on high availability techniques that can be used with or without a cluster, making it helpful for System Administrators even if they are not building a cluster. Anyone interested in deploying Linux in an environment where low cost computer reliability is important will find this book useful.
Your free to read time expires in minutes. After that you have to pause for an hour.
Book Details
Authors
Publishers
Publication year : 2005
License: All rights reserved ©
Times read: 98
