Re: [Pacemaker] pacemaker + cman - node names and bind address
On 05/12/13 02:28, Nikola Ciprich wrote:
> Hello,
>
> not sure whether this shouldn't be asked in some different
> conference, if so, I'm sorry in advance..
>
> Since this seems to be recommended solution for RHEL6 and since I
> need to use CLVMD, I switched my cluster from corosync + pacemaker
> to cman+pacemaker.
>
> I usually use two-nodes clusters, where hostnames resolve to lan
> uplink addresses, and nodes are interconnected using crosslink (to
> be exact, multiple crosslinks with bonding).
>
> I'd like to use hostnames as cluster node names, but I'd like
> cluster communication to go over crosslinks. Is there a way I could
> force this in cluster.conf?
>
> cluster.conf manpage is quite brief on this..
>
> Could somebody please give me an advice?
>
> thanks a lot in advance
>
> BR
>
> nik
Hello,
This list is fine to ask.
I speak mainly as a cman user, but I will make an educated guess on
the pacemaker side of things.
First, cman does not replace corosync. Both pacemaker and cman use
corosync for cluster communications and membership. The difference is
that cman configures and starts corosync for you, behind the scenes.
The node names you set in cluster.conf's " ... "
(an-c05n01.alteeve.ca in this case) is resolved to an IP address. This
IP address/subnet is then looked for of your network and, once found,
the associated network card is used.
Generally, it's advised that you set the cluster names to match each
node's 'uname -n' hostname. If you did that, then the following bit of
bash will tell you which interface will be used for the cluster (on
RHEL/CentOS 6, anyway);
ifconfig |grep -B 1 $(gethostip -d $(uname -n)) | grep HWaddr | awk '{
print $1 }'
Once you've identified the network, you will want to make sure that,
if it is bonded, it is a supported bond mode. Prior to 6.3 (iirc),
only mode=1 (active/passive) bonding was supported. With 6.4, mode=0
and mode=2 support was added. All other bond modes are not supported
under corosync.
As for pacemaker integration; Be sure to setup stonith in pacemaker
and make sure it is working. Then use the 'fence_pcmk' fence agent in
cluster.conf itself. This way, should cman detect a node failure, it
will call pacemaker and ask it to fence the target node, saving you
from having to keep the real fencing configured in two places at once.
hth
digimer
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
[Pacemaker] pacemaker + cman - node names and bind address
Hello, not sure whether this shouldn't be asked in some different conference, if so, I'm sorry in advance.. Since this seems to be recommended solution for RHEL6 and since I need to use CLVMD, I switched my cluster from corosync + pacemaker to cman+pacemaker. I usually use two-nodes clusters, where hostnames resolve to lan uplink addresses, and nodes are interconnected using crosslink (to be exact, multiple crosslinks with bonding). I'd like to use hostnames as cluster node names, but I'd like cluster communication to go over crosslinks. Is there a way I could force this in cluster.conf? cluster.conf manpage is quite brief on this.. Could somebody please give me an advice? thanks a lot in advance BR nik -- - Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28.rijna 168, 709 00 Ostrava tel.: +420 591 166 214 fax:+420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: ser...@linuxbox.cz - pgprBCrIex_wz.pgp Description: PGP signature ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Minor buffer overflow..
I was idly wondering why the SMTP and SNMP modules were disabled by default on the RHEL builds, and was in the middle of writing a shell script to duplicate them when I noticed there was a tiny buffer overflow in crm_mon. This may be why it's disabled by default? Patch: https://github.com/xrobau/pacemaker/commit/b1515e3f83fceeac951de8823d718bdf13e4a093 --Rob ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] catch-22: can't fence node A because node A has the fencing resource
On 2013-12-03T19:47:41, "Brian J. Murrell" wrote: > So given all of the above, and given the log I supplied showing that the > fencing was just not being attempted anywhere other than the node to be > fenced (which was down during that log) any clues as to where to look > for why? As far as I saw in your logs, you got a timeout (when host2 tried to fence host1). That doesn't seem to be related to this change. > It explains the differences, but unfortunately I'm still not sure why it > wouldn't get run somewhere else, eventually, rather than continually > being attempted on the node to be killed (which as I mentioned, was shut > down at the time the log was made). I think there was a fix related to this in post-1.1.10 git. Perhaps you can try that? Regards, Lars (For the record, this change in semantics and behaviour has caused quite some support questions here too. I didn't really like it either, but apparently, I'm just a whiner ;-) -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
