Michelle Streeter
> ASC2 MCS - SDE/ACL/SDL/EDL OKC Software Engineer
> The Boeing Company
>
> Date: Mon, 24 Aug 2015 17:52:01 +
> From: "Streeter, Michelle N"
> To: "users@clusterlabs.org"
> Subject: [ClusterLabs] Cluster.conf
> Message-ID:
>
neer
The Boeing Company
Date: Mon, 24 Aug 2015 17:52:01 +
From: "Streeter, Michelle N"
To: "users@clusterlabs.org"
Subject: [ClusterLabs] Cluster.conf
Message-ID:
<9a18847a77a9a14da7e0fd240efcafc2504...@xch-phx-501.sw.nos.boeing.com>
Content-Type: text/plain; cha
On 24/08/15 17:52 +, Streeter, Michelle N wrote:
> If I have a cluster.conf file in /etc/cluster, my cluster will not
> start. Pacemaker 1.1.11, Corosync 1.4.7, cman 3.0.12, But if I do
> not have a cluster.conf file then my cluster does start with my
> current configuration.
I don't think
The cluster.conf is needed by cman, and in RHEL 6, pacemaker needs to
use cman as the quorum provider. So you need a skeleton cluster.conf and
it is different from cib.xml.
If you use pcs/pcsd to setup pacemaker on RHEL 6.7, it should configure
everything for you, so you should be able to go strai
If I have a cluster.conf file in /etc/cluster, my cluster will not start.
Pacemaker 1.1.11, Corosync 1.4.7, cman 3.0.12, But if I do not have a
cluster.conf file then my cluster does start with my current configuration.
However, when I try to stop the cluster, it wont stop unless I have my
On 31/07/15 16:44 -0400, Digimer wrote:
> On 31/07/15 04:26 PM, Streeter, Michelle N wrote:
>> The previous administrator setup our cluster using the cman version and
>> the cluster.conf file. I we want to upgrade to pacemaker 1.9 on our
>> rhel 6.6 and so I have been testing this upgrade. But
On 31/07/15 04:26 PM, Streeter, Michelle N wrote:
> The previous administrator setup our cluster using the cman version and
> the cluster.conf file. I we want to upgrade to pacemaker 1.9 on our
> rhel 6.6 and so I have been testing this upgrade. But I noticed that
> the cib.xml does not reflec
The previous administrator setup our cluster using the cman version and the
cluster.conf file. I we want to upgrade to pacemaker 1.9 on our rhel 6.6 and
so I have been testing this upgrade. But I noticed that the cib.xml does not
reflect what we have in the cluster.conf file. Is there a t
