Hi Takatoshi-san,
On Wed, 21 Aug 2013 13:56:34 +0900
Takatoshi MATSUO matsuo@gmail.com wrote:
Hi Kristoffer
I reproduced the error with latest changest(b5ffd99e).
Thank you, with your description I was able to reproduce and create a
test case for the problem. I have pushed a workaround
Hi Kristoffer
2013/8/22 Kristoffer Grönlund kgronl...@suse.com:
Hi Takatoshi-san,
On Wed, 21 Aug 2013 13:56:34 +0900
Takatoshi MATSUO matsuo@gmail.com wrote:
Hi Kristoffer
I reproduced the error with latest changest(b5ffd99e).
Thank you, with your description I was able to reproduce
Hi!
Suppose you have an application A that needs two filesystems F1 and F2. The
filesystems are on separate LVM VGs VG1 and VG2 with LVs L1 and L2,
respectively. The RAID R1 and R2 provide the LVM PVs.
(Actually we have one group that has 58 primitives in them with both dimensions
being wider
Lars Marowsky-Bree l...@suse.com writes:
Poisoned resources indeed should just fail to start and that should be
that. What instead can happen is that the resource agent notices it
can't start, reports back to the cluster, and the cluster manager goes
Oh no, I couldn't start the resource
Hi,
Our setup uses some cluster wide pieces of meta information. Think
access control lists for resource instances used by some utilities or
some common configuration data used by the resource agents. Currently
this info is stored in local files on the nodes or replicated in each
primitive as
Hi,
man cibadmin says: the tagname and all attributes must match in order
for the element to be deleted, but experience says otherwise: the
primitive is deleted even if it was created with different attributes
than those provided to the --delete call, cf. 'foo' vs 'bar' in the
example below. Do
22.08.2013 15:08, Ferenc Wagner wrote:
Hi,
Our setup uses some cluster wide pieces of meta information. Think
access control lists for resource instances used by some utilities or
some common configuration data used by the resource agents. Currently
this info is stored in local files on
Hi,
I built a Pacemaker cluster to manage virtual machines (VMs). Storage
is provided by cLVM volume groups, network access is provided by
software bridges. I wanted to avoid maintaining precise VG and bridge
dependencies, so I created two cloned resource groups:
group storage dlm clvmd vg-vm
Vladislav Bogdanov bub...@hoster-ok.com writes:
22.08.2013 15:08, Ferenc Wagner wrote:
Our setup uses some cluster wide pieces of meta information.
You may use meta attributes of any primitives for that. Although crmsh
doe not like that very much, it can be switched to a relaxed mode.
OK,
Hi,
On Thu, 22 Aug 2013 18:22:50 +0200 Ferenc Wagner wf...@niif.hu wrote:
I built a Pacemaker cluster to manage virtual machines (VMs). Storage
is provided by cLVM volume groups, network access is provided by
software bridges. I wanted to avoid maintaining precise VG and bridge
On 22/08/2013, at 7:31 PM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de
wrote:
Hi!
Suppose you have an application A that needs two filesystems F1 and F2. The
filesystems are on separate LVM VGs VG1 and VG2 with LVs L1 and L2,
respectively. The RAID R1 and R2 provide the LVM PVs.
On 22/08/2013, at 10:08 PM, Ferenc Wagner wf...@niif.hu wrote:
Hi,
Our setup uses some cluster wide pieces of meta information. Think
access control lists for resource instances used by some utilities or
some common configuration data used by the resource agents. Currently
this info is
On 22/08/2013, at 10:22 PM, Ferenc Wagner wf...@niif.hu wrote:
Hi,
man cibadmin says: the tagname and all attributes must match in order
for the element to be deleted,
for the element to be deleted --- not the children of the element to be
deleted
but experience says otherwise: the
13 matches
Mail list logo
