Hi Emmanuel,
> i don't see any reason for put libvirtd as primitive in pacemaker
Yes ... well, maybe. During my testing of failure scenarios (in
particular, reboot of the VM host), several times the VM filesystem
ended up corrupted and I needed to reinstall the VM. At least a couple
of these
On 20 Dec 2013, at 1:36 am, Stephane Robin wrote:
> Hi,
>
> This is a follow up on my previous post 'Trouble building Pacemaker from
> source on CentOS 5.10'
> Andrew: Thanks for your pointers.
>
> It turns out Pacemaker 1.1.10 needed more changes to build on CentOS 5.x.
> • revert of
remove the libvirtd from pacemaker and chkconfig libvirtd on every node,
like that the cluster just manage the vm, maybe i wrong but i don't see any
reason for put libvirtd as primitivi in pacemaker
2013/12/19 Bob Haxo
> Hi Emmanuel,
>
> Thanks for the suggestions. It is pretty clear what is t
On 20 Dec 2013, at 2:11 am, Andrew Martin wrote:
> David/Andrew,
>
> Once 1.1.11 final is released, is it considered the new stable series of
> Pacemaker,
yes
> or should 1.1.10 still be used in very stable/critical production
> environments?
>
> Thanks,
>
> Andrew
>
> - Original Mes
Hi Emmanuel,
Thanks for the suggestions. It is pretty clear what is the problem; it's
just not clear what is the fix or the work-around.
Search the Pacemaker email archive for the email of Andrew Beekhof, 12
Oct 2012, "Re: [Pacemaker] chicken-egg-problem with libvirtd and a VM
within cluster",
Maybe the problem is this, the cluster try to start the vm and libvirtd
isn't started
2013/12/19 emmanuel segura
> if don't set your vm to start at boot time, you don't to put in cluster
> libvirtd, maybe the problem isn't this, but why put the os services in
> cluster, for example crond ..
if don't set your vm to start at boot time, you don't to put in cluster
libvirtd, maybe the problem isn't this, but why put the os services in
cluster, for example crond .. :)
2013/12/19 Bob Haxo
> Hello,
>
> Earlier emails related to this topic:
> [pacemaker] chicken-egg-problem with libv
Hello,
Earlier emails related to this topic:
[pacemaker] chicken-egg-problem with libvirtd and a VM within cluster
[pacemaker] VirtualDomain problem after reboot of one node
My configuration:
RHEL6.5/CMAN/gfs2/Pacemaker/crmsh
pacemaker-libs-1.1.10-14.el6_5.1.x86_64
pacemaker-cli-1.1.10-14.el6_
- Original Message -
> From: "Steven Silk - NOAA Affiliate"
> To: "The Pacemaker cluster resource manager"
> Sent: Thursday, December 19, 2013 11:54:36 AM
> Subject: [Pacemaker] Typo? pcs cluster push question
>
> I have been working from
> http://clusterlabs.org/doc/en-US/Pacema
I have been working from
http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/_example.html
at the bottom of the page is :
Now push the configuration into the cluster
# pcs cluster push cib stonith_cfg
This does not work - I believe the proper syntax is
# pcs cluster cib-pus
Anybody have experience with nood scheduler? i know the sbd process is a
real time process, so with default linux io scheduler cfq, the sbd process
works very well on high io heave load.
The noop scheduler only merge the io request in fifo queue, can i have
problem with my cluster using nood sched
David/Andrew,
Once 1.1.11 final is released, is it considered the new stable series of
Pacemaker, or should 1.1.10 still be used in very stable/critical production
environments?
Thanks,
Andrew
- Original Message -
> From: "David Vossel"
> To: "The Pacemaker cluster resource manager"
Hi,
This is a follow up on my previous post 'Trouble building Pacemaker from source
on CentOS 5.10'
Andrew: Thanks for your pointers.
It turns out Pacemaker 1.1.10 needed more changes to build on CentOS 5.x.
* revert of a81d222
* g_timeout_add_seconds not available in libc in
lib/servi
On Wed, 18 Dec 2013 21:21:32 +0100 (CET)
"Rainer Brestan" wrote:
> What i really miss in crmsh is the possibility to specify resource
> parameters which are different on different nodes, so the parameter
> is node dependant. In XML syntax this is existing, Andrew gave me the
> hint as answer to a
14 matches
Mail list logo
