From: Kazunori INOUE <inouekazu@intellilink.co.jp>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [fence-virt PATCH] backend plugin for Pacemaker
Date: Tue, 22 Nov 2011 18:29:21 +0900 [thread overview]
Message-ID: <4ECB6B71.2010307@intellilink.co.jp> (raw)
In-Reply-To: <4EAA7148.9080805@intellilink.co.jp>
(11.10.28 18:09), Kazunori INOUE wrote:
> Hi, Lon
>
> (2011/10/26 9:54), Lon Hohberger wrote:
>> On 09/20/2011 03:40 AM, Kazunori INOUE wrote:
>>> Hi,
>>>
>>> I created the backend "pm-fence" which has met the following
>>> configurations / requirements.
>>> - Both hosts and VMs, cluster (Pacemaker) have been configured.
>>> * This backend has STONITH (fencing) function of the VM cluster.
>>> - The VMs are managed as resources (RA is VirtualDomain) by the host cluster.
>>> * In this configuration, in order to stop a VM,
>>> it is necessary to stop the resource through the host cluster.
>>> When the VM was stopped without through the host cluster
>>> (e.g., run the 'virsh destory'), the host cluster considers that
>>> VM resource failed.
>>>
>>
>> This patch is good, but the server/Makefile.in needs to use pkg-config
>> --cflags / --libs glib-2.0 rather than static definitions. I have
>> included an updated patch.
>>
> OK. But please correct the target of 'pkg-config -libs' to ncurses.
>
> # diff 0001-backend-plugin-for-Pacemaker.patch mod
> 64c64
> < +PACEMAKER_LIBS=-lcib -lpe_status `pkg-config --libs glib-2.0`
> ---
>> +PACEMAKER_LIBS=-lcib -lpe_status `pkg-config --libs ncurses`
> #
>
> When glib-2.0 is the target, it fail in load.
>
> # pkg-config --libs glib-2.0
> -lglib-2.0
> #
> # fence_virtd -d99 -F
> :
> Loading plugin from /DEV/fence-virt/plugins/pm-fence.so
> Could not dlopen /DEV/fence-virt/plugins/pm-fence.so:
> /usr/lib64/libpe_status.so.2: undefined symbol: stdscr
>
>> Otherwise, I do like this patch quite a lot.
>>
>> The only question I had is why there needs to be an external STONITH
>> plugin; I was of the impression that fence_virt and fence_xvm work out
>> of the box with Pacemaker 1.1.x. That doesn't affect this particular
> We do not know how to do it...
>
>> patch, as far as I can tell (it looks like just a glue wrapper between
>> pacemaker and fence_virt itself).
>>
> That's right. The purpose of this STONITH plugin is to adapt
> the request from a pacemaker to usage of fence_virt/fence_xvm.
>
> Best Regards,
> Kazunori INOUE
Hi,
Is there a plan to merge this patch?
To that end, what do I need to do?
Regards,
Kazunori INOUE
next prev parent reply other threads:[~2011-11-22 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 7:40 [Cluster-devel] [fence-virt PATCH] backend plugin for Pacemaker Kazunori INOUE
2011-10-26 0:54 ` Lon Hohberger
2011-10-28 9:09 ` Kazunori INOUE
2011-11-22 9:29 ` Kazunori INOUE [this message]
2012-02-07 23:18 ` Lon Hohberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ECB6B71.2010307@intellilink.co.jp \
--to=inouekazu@intellilink.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.