[Cluster-devel] [fence-virt PATCH] backend plugin for monitoring a host's status

Kazunori INOUE inouekazu at intellilink.co.jp
Wed Oct 5 08:56:11 UTC 2011


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
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: add_general_backend.patch
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20111005/746fa8b5/attachment.ksh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: overview.PNG
Type: image/png
Size: 23810 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20111005/746fa8b5/attachment.png>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: vm-client
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20111005/746fa8b5/attachment-0001.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: fence_virt.conf
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20111005/746fa8b5/attachment.conf>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pm-monitor.conf
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20111005/746fa8b5/attachment-0001.conf>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: host.cli
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20111005/746fa8b5/attachment-0002.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: VM.cli
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20111005/746fa8b5/attachment-0003.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mon-host.txt
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20111005/746fa8b5/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mon-VM.txt
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20111005/746fa8b5/attachment-0001.txt>


More information about the Cluster-devel mailing list