This site is a static archive of the Aegir community site. Documentation has moved to http://docs.aegirproject.org. Other community resources can be found on the Contacting the community page.
Skip navigation

Revision of Web clusters from Wed, 04/25/2012 - 17:11

Help

Web clusters

Tagged:

Cluster module

This module is now (as of Aegir 1.7) deprecated. It is replaced by the "pack" module. Support for the "cluster" module will be dropped in 2.0.

Pack module

A Pack consists of a single server node that is specified as "pack" and any number of server nodes specified as "apache" or "nginx". those The main difference between the Pack functionality and Web Cluster functionality is that Aegir rsync's configuration (Apache & Nginx) to "all" nodes in the Pack and rysnc's the platform and site code to only the "master" node in the Pack. All other "slave" nodes will see the platform and site code via NFS.

Configuring the Pack server node:

The "pack" server node will not be used by Aegir to physically deploy sites or platforms on so consider it more of a virtual server group. When creating it you do not need to supply a valid Server hostname or IP address so choose a naming convention that makes sense in your environment.

Next, select the "pack" radio button option under the web configuration when creating, or editing, the node in order to designate this server node as the "pack" server.

Finally, select the "Master" server from the list of Master servers. The Master server will be the server node that Aegir rsync's the platform and site to. Now select the "Slave" servers from the list of Slave servers. The Slave servers will have the Apache or Nginx config rsync'd to them but not the platform or site code since that will be available to all Slave servers via the NFS share.

Configuring the Web server nodes (Master and Slaves):

Configure all web server nodes using those instructions.

Then mount the files on the remote server.

On the filer:

apt-get install nfs-server
echo "/var/aegir/platforms    10.10.10.0/24(rw,no_subtree_check)" >> /etc/exports

Then on the web servers (Master and Slaves):

apt-get install nfs-client
mount filer01:/var/aegir/platforms /var/aegir/platforms

Add this to your fstab:

10.10.10.31:/var/aegir/platforms /var/aegir/platforms nfs rw 0 0

Creating a Platform on a Pack:

When configuring a Platform to be deployed on a Pack choose the "Pack" server node from the Web server radio group during the Platform node creation.

#1

I am interested in a deployment strategy for Aegir in the context of a web cluster that uses glusterfs to keep the two servers in sync. We have not yet implemented such a cluster, but have been considering it for quite some time. Gluster prevents the single point of failure that nfs creates.

The question is, how can aegir be used to deploy platforms and sites to a gluster cluster?

#2

We are trying to move from deploying code via clustering (rsynch) to pack (writing to a shared NFS). On our Red Hat, Drupal v6 seems to have problems using the NFS file caching. Possibly something about opening files in shared mode which is not compatible with NFS file cache. Does that sound similar to a problem anyone else has experienced ?

Need help?

Documentation

The notebook section provides a way for you to store and share information with your group members. With the book feature you can:

  • Add book pages and organize them hierarchically into different books.
  • Attach files to pages to share them with others.
  • Track changes that others have made and revert changes as necessary.
  • Archive books that are no longer of interest to the group. Archived books can be reactivated later if needed.

The revisions let you track differences between multiple versions of a post.