Red Hat ENTERPRISE LINUX 5 - GLOBAL NETWORK BLOCK DEVICE Installationsanleitung Seite 93
- Seite / 134
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
Appendix A. Example of Setting Up
Apache HTTP Server
This appendix provides an example of setting up a highly available Apache HTTP Server on a
Red Hat Cluster. The example describes how to set up a service to fail over an Apache HTTP
Server. Variables in the example apply to this example only; they are provided to assist setting
up a service that suits your requirements.
Note
This example uses the Cluster Configuration Tool (system-config-cluster).
You can use comparable Conga functions to make an Apache HTTP Server
highly available on a Red Hat Cluster.
1. Apache HTTP Server Setup Overview
First, configure Apache HTTP Server on all nodes in the cluster. If using a failover domain ,
assign the service to all cluster nodes configured to run the Apache HTTP Server. Refer to
Section 6, “Configuring a Failover Domain” for instructions. The cluster software ensures that
only one cluster system runs the Apache HTTP Server at one time. The example configuration
consists of installing the httpd RPM package on all cluster nodes (or on nodes in the failover
domain, if used) and configuring a shared GFS shared resource for the Web content.
When installing the Apache HTTP Server on the cluster systems, run the following command to
ensure that the cluster nodes do not automatically start the service when the system boots:
# chkconfig --del httpd
Rather than having the system init scripts spawn the httpd daemon, the cluster infrastructure
initializes the service on the active cluster node. This ensures that the corresponding IP address
and file system mounts are active on only one cluster node at a time.
When adding an httpd service, a floating IP address must be assigned to the service so that
the IP address will transfer from one cluster node to another in the event of failover or service
relocation. The cluster infrastructure binds this IP address to the network interface on the cluster
system that is currently running the Apache HTTP Server. This IP address ensures that the
cluster node running httpd is transparent to the clients accessing the service.
The file systems that contain the Web content cannot be automatically mounted on the shared
storage resource when the cluster nodes boot. Instead, the cluster software must mount and
unmount the file system as the httpd service is started and stopped. This prevents the cluster
83
- Red Hat Cluster for Red 1
- Hat Enterprise Linux 1
- Introduction 7
- 1. Document Conventions 8
- 2. Feedback 9
- Management Overview 11
- 2. Conga 14
- Figure 1.3. luci homebase Tab 15
- Figure 1.4. luci cluster Tab 16
- Figure 1.5. luci storage Tab 17
- 3.2. Cluster Status Tool 20
- Table 1.1. Command Line Tools 21
- Before Configuring a Red Hat 23
- Instant-Off 30
- 5. Configuring max_luns 33
- 7. Multicast Addresses 34
- 1. Configuration Tasks 37
- 2. Starting luci and ricci 38
- 3. Creating A Cluster 39
- 4. Global Cluster Properties 40
- 5. Configuring Fence Devices 42
- 7.1. Adding a Failover Domain 51
- 8. Adding Cluster Resources 53
- Managing Red Hat Cluster With 57
- 2. Managing Cluster Nodes 58
- /etc/cluster/ 59
- /proc/partitions and checks 67
- /bin/sh -c. A return 67
- 4. Configuring Fence Devices 68
- Two Nodes 71
- Than Two Nodes 72
- 6.1. Adding a Failover Domain 76
- 7. Adding Cluster Services 80
- Table 6.1. Members Status 87
- Table 6.2. Services Status 87
- Apache HTTP Server 93
- 2. Configuring Shared Storage 94
- /var/www/html/) 96
- /dev/sda3) 96
- Appendix B. Fence Device 99
- Table B.4. Dell DRAC 100
- Table B.8. IBM Blade Center 101
- Table B.11. Manual Fencing 102
- Table B.12. McData SAN Switch 102
- Table B.15. SCSI Fencing 103
- Table B.17. Vixel SAN Switch 103
- Table B.18. WTI Power Switch 104
- Appendix C. HA Resource 105
- Parameters 105
- Table C.2. Apache Server 106
- Table C.3. File System 107
- Table C.4. GFS 107
- Table C.5. IP Address 108
- Table C.6. LVM 108
- Table C.7. MySQL® 108
- Table C.8. NFS Client 109
- Table C.9. NFS Export 109
- Table C.10. NFS Mount 109
- Table C.11. Open LDAP 110
- Table C.12. Oracle® 10g 110
- Table C.13. PostgreSQL 8 111
- Table C.14. SAP® Database 111
- Table C.15. SAP® Instance 112
- Table C.16. Samba Service 112
- Table C.17. Script 112
- Table C.18. Service 113
- Important 114
- Table C.21. Virtual Machine 115
- /usr/share/cluster of any 117
- /etc/cluster/cluster.conf 117
- Resources 118
- Resource Agent, service.sh 120
- </service> 125
- __independent_subtree 125
- Ordering 126
- Cluster from RHEL 4 to RHEL 5 129
Verwandte Produkte und Handbücher für Server Red Hat ENTERPRISE LINUX 5 - GLOBAL NETWORK BLOCK DEVICE
Server Red Hat LINUX VIRTUAL SERVER - FOR ENTERPRISE LINUX 5.2 REV 05-2008 Bedienungsanleitung
(32 Seiten)
(32 Seiten)
Server Red Hat NETSCAPE ENTERPRISE SERVER 6.1 - NSAPI PROGRAMMER GUIDE Betriebsanweisung
(84 Seiten)
(84 Seiten)
Server Red Hat NETSCAPE ENTERPRISE SERVER 6.0 - NSAPI PROGRAMMER GUIDE Bedienungsanleitung
(66 Seiten)
(66 Seiten)
(60 Seiten)Radio Shack 14-1265 manuels
Manuels d'utilisation et guides de l'utilisateur pour Lecteurs de cassettes Radio Shack 14-1265.
Nous fournissons des manuels en pdf 2 Radio Shack 14-1265 à télécharger gratuitement par type de document : Manuel du propriétaire, Manuel de l'utilisateur
Kommentare zu diesen Handbüchern