I'm looking at implementing a RHEL 6 based cluster using DRBD. For this I plan to have a dedicated fast bonded network between the two nodes for the backend DRBD Storage Network (SN), well a 10Gb with a 1Gb failover.
Most examples I've seen of doing this seem to use the SN as ringnumber 1 in totem, does it make more sense to be ringnumber 0. I assume this could be accomplished by setting the hostnames associated with SN network IPs as the node names in cluster.conf. And put the altname in as the hostname associated with the main network IPs.
My reasons for thinking of doing this are that my SN network will be back to back wired so more reliable than a switch based network but more importantly it's performance will be higher for GFS2 locking etc
Does this make sense to do (anyone else do this)?
Does this make management harder at all say from a central off cluster luci, that the node names are not themselves are not resolveable from the main network DNS (the altname's will be). Any other nastyness that might arise?
One thing I don't like is the machine hostnames will not be their network DNS names. Would the cluster suite be happy if the hostname of the node matches the "altname" but not the "clusternode name"?
As a quick aside, I've only played with clustering on RHEL5 before so on RHEL6 does corosync.conf get generated from cluster.conf. If not, what would happen if I hand craft a corosync.conf for doing my config above ?
Would this upset things with regards using keeping things the right way around in cluster.conf with regards "clusternode name" and "altname"?
Thanks for any info
This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify the sender and delete the original.