at 11:20 AM, David Vossel dvos...@redhat.com wrote:
- Original Message -
From: Lindsay Todd rltodd@gmail.com
To: The Pacemaker cluster resource manager
Pacemaker@oss.clusterlabs.org
Sent: Tuesday, October 22, 2013 4:19:11 PM
Subject: [Pacemaker] Asymmetric cluster, clones
I am getting rather unexpected behavior when I combine clones, location
constraints, and remote nodes in an asymmetric cluster. My cluster is
configured to be asymmetric, distinguishing between vmhosts and various
sorts of remote nodes. Currently I am running upstream version b6d42ed. I
am
/09/2013, at 6:18 AM, Lindsay Todd rltodd@gmail.com wrote:
We've been attempting to set up an asymmetric pacemaker cluster using
remote cluster nodes, with pacemaker 1.1.10 (actually, building from git
lately, currently at a4eb44f). We use location constraints to enable
resources to start
Beekhof and...@beekhof.net wrote:
On 04/09/2013, at 6:18 AM, Lindsay Todd rltodd@gmail.com wrote:
We've been attempting to set up an asymmetric pacemaker cluster using
remote cluster nodes, with pacemaker 1.1.10 (actually, building from git
lately, currently at a4eb44f). We use location
We've been attempting to set up an asymmetric pacemaker cluster using
remote cluster nodes, with pacemaker 1.1.10 (actually, building from git
lately, currently at a4eb44f). We use location constraints to enable
resources to start on nodes they should start on, and rely on asymmetry to
otherwise
(ocf::ccni:xcatVirtualDomain): Started cvmh04
DummyOnVM (ocf::pacemaker:Dummy): Stopped
On Wed, Jul 10, 2013 at 6:43 PM, Lindsay Todd rltodd@gmail.com wrote:
Yes, it avoids the crashes. Thanks! But I am still seeing spurious VM
migrations/shutdowns when I stop/start a VM
@oss.clusterlabs.org
Sent: Wednesday, July 3, 2013 4:20:37 PM
Subject: Re: [Pacemaker] Pacemaker remote nodes, naming, and attributes
- Original Message -
From: Lindsay Todd rltodd@gmail.com
To: The Pacemaker cluster resource manager
pacemaker@oss.clusterlabs.org
Sent
10, 2013 at 12:42 PM, Lindsay Todd rltodd@gmail.com wrote:
Thanks! But there is still a problem.
I am now working from the master branch and building RPMs (well, I have to
also rebuild from the srpm to change the build number, since the RPMs built
directly are always 1.1.10-1). The patch
.
On Wed, Jul 10, 2013 at 2:12 PM, David Vossel dvos...@redhat.com wrote:
- Original Message -
From: Lindsay Todd rltodd@gmail.com
To: The Pacemaker cluster resource manager
pacemaker@oss.clusterlabs.org
Sent: Wednesday, July 10, 2013 12:11:00 PM
Subject: Re: [Pacemaker
traceback from the core file that crmd dumped, into bug 5164.
On Tue, Jul 2, 2013 at 8:40 PM, David Vossel dvos...@redhat.com wrote:
- Original Message -
From: Lindsay Todd rltodd@gmail.com
To: The Pacemaker cluster resource manager
pacemaker@oss.clusterlabs.org
Sent: Tuesday
:58 PM
Subject: Re: [Pacemaker] Pacemaker remote nodes, naming, and attributes
- Original Message -
From: Lindsay Todd rltodd@gmail.com
To: The Pacemaker cluster resource manager
Pacemaker@oss.clusterlabs.org
Sent: Wednesday, June 19, 2013 4:11:58 PM
Subject
I built a set of rpms for pacemaker 1.1.0-rc4 and updated my test cluster
(hopefully won't be a test cluster forever), as well as my VMs running
pacemaker-remote. The OS everywhere is Scientific Linux 6.4. I am wanting
to set some attributes on remote nodes, which I can use to control where
Yes! The handshaking is working now. I'll hopefully have time
tomorrow to create some services on a few VMs and see how that all
goes. Thanks!
On Fri, May 24, 2013 at 4:28 PM, David Vossel dvos...@redhat.com wrote:
Try this patch.
Working on this problem further...
On Tue, May 21, 2013 at 5:14 PM, David Vossel dvos...@redhat.com wrote:
I'd suggest this. Try running the pacemaker_remote regression test and see
what happens. This will start up
an instance of pacemaker_remote locally and issue client commands to it to
a
username with PSK authentication?
/Lindsay
On Thu, May 16, 2013 at 6:47 PM, David Vossel dvos...@redhat.com wrote:
- Original Message -
From: Lindsay Todd rltodd@gmail.com
To: The Pacemaker cluster resource manager
Pacemaker@oss.clusterlabs.org
Sent: Thursday, May 16
I've built pacemaker 1.1.10rc2 and am trying to get the pacemaker-remote
features working on my Scientific Linux 6.4 system. It almost works...
The /etc/pacemaker/authkey file is on all the cluster nodes, as well as my
test VM (readable to all users, and checksums are the same everywhere). I
-remote. So VM migration
is still really needed.
/Lindsay
On Tue, May 14, 2013 at 4:26 AM, Lars Marowsky-Bree l...@suse.com wrote:
On 2013-05-13T12:28:17, Lindsay Todd rltodd@gmail.com wrote:
Folks: On my cluster built on SL6.4, I need to deploy some VMs that depend
on other VMs:
- db0
Folks: On my cluster built on SL6.4, I need to deploy some VMs that depend
on other VMs:
- db0 has no dependendencies
- ldap01,ldap02 require db0 to be running -- ordering constraint, but no
collocation (other than we'll use a collocation constraint to recommend
ldap01, ldap02 run on
-remote in production?
Documentation seems a bit sparse (though I think enough to set it up)...
/Lindsay
On Mon, May 13, 2013 at 3:19 PM, Vladislav Bogdanov bub...@hoster-ok.comwrote:
13.05.2013 19:28, Lindsay Todd wrote:
Folks: On my cluster built on SL6.4, I need to deploy some VMs
19 matches
Mail list logo
