Hi,
I'm pretty new to all this stuff, but I've read pretty much all the
documentation on the clusterlabs website. I'm seeking a bit of
clarification/confirmation on how to achieve certain things, in
particular around fencing/STONITH, before we dive into trying to set
this up.
We're using SuSE Linux Enterprise 11, and will probably be buying their
HA Extension, which includes OpenAIS and Pacemaker. We're using Dell
servers, with their DRAC on-board management console.
We have two physical app servers, master and slave. These are behind a
firewall which has some internal load balancing support (at least basic
round-robin).
On master, we will be running:
- an HAProxy software load balancer
- 8 Zope app server processes
- memcached
- PostgreSQL
- A "blob" file store
On slave, we'll have:
- a hot standby HAProxy instance
- 8 further Zope app server processes, which are active
- a hot standby memcached
- PostgreSQL (probably in cold standby)
Also note:
- We intend to use the IPaddr2 resource agent to cluster an IP address
across master and slave.
- I'm not sure we need to use Pacemaker to manage HAProxy on slave; it
will simply not be used until the IP address fails over to slave.
- To deal with sometimes severe peaks in our load, we'll have HAProxy
on master send certain requests to the "live" Zope app server processes
on slave. HAProxy deals with Zope processes going up and down, so we
don't really need to cluster these per se.
- Zope communicates with Postgres. We intend that connection string to
use the floating IP address, so that if Postgres fails over to slave,
Zope will be unaware.
- Memcached is used by Zope to cache certain Postgres database
queries, so it would be similar. We can have this on hot standby (if
that's easier?) since it only manages data in local RAM, but the
memcached connection string would use the floating IP address too.
- Zope writes certain "blob" files to the filesystem. All Zope clients
(across both servers) need a shared blob directory. They do implement
locking on this directory, so concurrent access is not a problem.
Now for the bits I'm less sure about:
- We were thinking to create a DRBD partition with OCFS2 for Postgres
data + blob data. IIUC, that setup handles multiple nodes writing, so
the blob storage should work fine (since Zope will ensure integrity of
the directory
- We were thing to use the pgsql resource agent that comes with
Pacemaker to manage Postgres.
- The postgres data would need fencing when failing over, from what I
understand. I read the notes that using an on-board device like Dell's
DRAC to implemenet STONITH is not a good idea. We don't have the option
at this stage to buy a UPS-based solution (we do have UPS, but it can't
be used to cut power to individual servers). We do have two pairs of
NICs in each server, one of which would be used "crossover" between
master and slave.
Given this, what is the best way to implement fencing in this situation?
Could we use DRBD to just refuse master write access to the slave disk?
Could we accept a bit more risk and say that STONITH will succeed even
if *communication* with the DRAC fails, but will try to use DRAC if it
can reach it? This may solve the "fencing indefinitely" problem when
postgres is failing over due to a power outage on master, and Pacemaker
can't find DRAC to kill master.
- If HAProxy or memcached on master fails (in the software sense),
we'd need to fail over the floating IP address so that the front-end
firewall and the Zope connection strings would continue to work, even
though we have hot standby's on slave. Is this the right thing to do? If
so, I'd appreciate some pointers on how to configure this. There are no
resource agents that ship with Pacemaker I can find for
memcached/HAProxy, though perhaps it'd be better to create them and let
Pacemaker manage everything? In that case, how do we manage the
connection string issue (making sure Zope talks to the right thing) if
not by failing over an IP address?
Thanks a lot!
Martin
_______________________________________________
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
