sgsax at ksu
Apr 25, 2012, 3:23 PM
On 04/25/2012 04:40 PM, William Seligman wrote:
> On 4/25/12 4:53 PM, Seth Galitzer wrote:
>> Can anybody point me to recent docs on how to go about setting this up?
>> I've found several much older posts, but not much current with any
>> kind of helpful detail.
>> This one has a couple of good tips, but doesn't have much depth:
>> This one has a lot of detail, but do I really need to use GFS and CTDB
>> if I just use a common shared FS for both nodes to get locking data from?:
>> I should note that I'm using DRBD+LVM for my node shared storage and
>> also exporting FS shares via NFS (I run heterogeneous systems here with
>> both Linux and Windows clients, so need both available).
> Are you running DRBD+LVM primary-secondary or primary-primary?
This setup is primary/secondary.
> If it's the former, I suggest using the configuration described in "Clusters
> From Scratch":
> the only difference being that instead of running Apache you'd run Samba and
> NFS. If you're exporting your filesystems read/write, I think that's the
> recommended configuration.
I've read through that multiple times. Very good general documentation.
I guess what I'm looking for is a more specific howto doc with example
configs. I find that personally, that helps me to understand what's
going on better.
> I'm running primary-primary and exporting filesystems via NFS (I'm running Samba
> too, but inside a KVM virtual machine exporting its internal filesystem).
> However, I'm exporting them read-only.
So GFS is only really recommended for a primary/primary setup since both
nodes need to write to it at the same time? With my DRBD
primary/secondary setup, other FS (ext4, xfs, etc.) should be fine, correct?
I already have pacemaker with the following resources configured and
working, with appropriate prereqs for each "layer":
I guess I view the resources as being "stacked", each one adding a new
layer, depending on the previous one. So what I'm trying to do now is
add the samba layer, which is probably parallel to exportfs/nfsd in this
stack. Adding the resource is simple enough, and it seems to fail over
correctly, but I see that I need to be able to manage samba's locking
database and other administrata for a seamless failover.
I'm also finding that I might have to do something tricky with "net ads
join" for the nodes, as when you register one, it overwrites the IDs on
the other one in the AD. I guess I didn't mention this also needs Active
Directory integration instead of winbind for client authentication, so
that's another wrinkle.
Computing and Information Sciences
Kansas State University
sgsax [at] ksu
Linux-HA mailing list
Linux-HA [at] lists
See also: http://linux-ha.org/ReportingProblems