Hi Rasto,
Note that on RHEL
6/CentOS 6, you should run the Pacemaker through CMAN and not
a Corosync plugin
Not glad to hear that... We are using Pacemaker+Corosync
everywhere (SuSe, CentOS, OracleLinux servers).
Is there any
On Fri, Apr 19, 2013 at 9:11 AM, Alexandr A. Alexandrov
shurr...@gmail.com wrote:
Hi Rasto,
Note that on RHEL 6/CentOS 6, you should run the Pacemaker through CMAN and
not a Corosync plugin
I wonder if that's still true, but better be safe than sorry.
Not glad to hear that... We are using
Hi Chris,
No, you're definitely not missing anything. The 'pcs cluster cib'
output isn't pretty.
why there is an approach to build a new config-tool at all?
Why not use the crmsh? Why it was dropped in the RHEL-build?
Does it have some relevant disadvantages?
--
To Answer please replace
Hi,
Because the nodes are located in different networks, each node needs
it's own route-ressource, that is only valid if the node is passive and
will be removed when this node goes active and gets the default route
for the cluster-ip.
I did not found any solution for this, so I'm going the
I don't know why redhat doesn't give to the users the alternatives to use
what they want
sorry for my ugly english :-)
Thanks
2013/4/19 T. nos...@godawa.de
Hi Chris,
No, you're definitely not missing anything. The 'pcs cluster cib'
output isn't pretty.
why there is an approach to
On Fri, Apr 19, 2013 at 11:15 AM, Alexandr A. Alexandrov
shurr...@gmail.com wrote:
Hi!
I do not need CMAN config to be created, since I do not use CMAN...
It's possible, you would have to on RHEL6 system.
I tried LCMC, it seems to recognize cluster/drbd settings.
However, when I was
Hi David,
Why can't both your cluster nodes have 10.20.10.1 as their default
route all the time?
because the different locations have different networks, routers,
IP-addresses etc. But to be always reachable from the outside, they need
one common IP-address, that is valid on the active node.
Guys,
I can't get rid of following warnings:
Apr 19 19:00:37 node2 crmd: [32230]: WARN: start_subsystem: Client pengine
already running as pid 32240
Apr 19 19:00:44 node2 pengine: [32240]: WARN: unpack_status: Node node1 in
status section no longer exists
Apr 19 19:00:44 node2 pengine:
Given:
host1# crm node attribute host1 show foo
scope=nodes name=foo value=bar
Why doesn't this return anything:
host1# crm_attribute --node host1 --name foo --query
host1# echo $?
0
cibadmin -Q confirms the presence of the attribute:
node id=host1 uname=host1
