cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Kazunori INOUE <inouekazu@intellilink.co.jp>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [fence-virt PATCH] backend plugin for monitoring a host's status
Date: Thu, 13 Oct 2011 17:52:38 +0900	[thread overview]
Message-ID: <4E96A6D6.0@intellilink.co.jp> (raw)
In-Reply-To: <CAEDLWG0bnxqMTOb03T-aTw+93GjQ+a9_cHv_Ddc=QdkOrj_d3g@mail.gmail.com>

Hi, Andrew

We (NTT) will participate in the HA Mini-Conference,
please let we explain at that time.

Best Regards

(2011/10/12 10:40), Andrew Beekhof wrote:
> Was making host connectivity information available to the guests the
> goal here or just something to demonstrate the concept?
> Interesting idea :-)
>
> 2011/10/5 Kazunori INOUE<inouekazu@intellilink.co.jp>:
>> Hi all,
>>
>> I think that the communication function of fence-virt is flexible,
>> so I want to use it more effectively.
>>
>> Therefore I made backend plugin for a guest to get the host's status
>> using the communication facility of fence-virt,
>> and I changed to allow specifying one more backend (for fencing, and
>> replying the host's status).
>>
>> I created the backend "pm-monitor" which has met the following
>> configurations / requirements.
>> - Both hosts and VMs, cluster (Pacemaker) have been configured.
>>
>> Here's an overview of function. Please refer to attached 'overview.png'.
>> (*) pingd resource notifies the status of connection with a specific
>>     host to pacemaker, and pacemaker manages the result.
>> (1) resource (vm-client) which requires the host's status is executed.
>> (2) vm-client requests 'host_status (result of pingd)' to the host
>>     with fence_virt.
>> (3) use the serial listener,
>> (4) fence_virtd (pm-monitor backend) gets the 'result of pingd' from
>>     pacemaker and answers it after conversion.
>>     - the conversion rule is set in /etc/pm-monitor.conf
>>
>> Here's a description of the attached files.
>> * add_general_backend.patch
>>   - add the server/pm-fence.c
>>   - change the configure.in and server/Makefile.in
>> * overview.png
>>   - figure of the overview.
>> * vm-client
>>   - Resource Agent for VM.
>>   - I'm going to post this RA to the appropriate community
>>     (https://github.com/ClusterLabs/resource-agents).
>> * fence_virt.conf
>>   - sample configuration.
>> * pm-monitor.conf
>>   - sample configuration for pm-monitor.so
>>
>> * host.cli, mon-host.txt
>>   - sample configuration file of a host cluster,
>>     and mon-host.txt is an output of the crm_mon command.
>> * VM.cli, mon-VM.txt
>>   - sample configuration file of a VM cluster,
>>     and mon-VM.txt is an output of the crm_mon command.
>>
>> Best Regards



  reply	other threads:[~2011-10-13  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05  8:56 [Cluster-devel] [fence-virt PATCH] backend plugin for monitoring a host's status Kazunori INOUE
2011-10-12  1:40 ` Andrew Beekhof
2011-10-13  8:52   ` Kazunori INOUE [this message]
2011-10-13 23:18     ` Andrew Beekhof
2011-10-26  1:35 ` Lon Hohberger
2011-10-31  8:19   ` Kazunori INOUE

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=4E96A6D6.0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).