[Linux-cluster] Testing a fence program

[John Anderson]

It looks like fence_xen.pl, by default anyway, uses ssh to login to the
remote xen host and shut down or destroy the instance.  That's what I'm
trying to avoid because of certain rules and regulations I have to
follow.  

I went ahead and wrote a gSOAP/libvirt based fencing agent that doesn't
require any type of shell access and uses SSL client certificate
authentication.  It solves the problems while keeping the regulation
Nazis off my back.

Thanks,

John Anderson

-----Original Message-----
From: linux-cluster-bounces at redhat.com
[mailto:linux-cluster-bounces at redhat.com] On Behalf Of Lon Hohberger
Sent: Wednesday, August 23, 2006 10:42 AM
To: linux clustering
Subject: Re: [Linux-cluster] Testing a fence program

On Tue, 2006-08-22 at 12:42 -0700, John Anderson wrote:
> Greetings,
> 
>  
> 
> I'm in the process of developing a fence_* program that will xm
> shutdown xen instances remotely.  What is a good way to get fenced to
> invoke this program so I can test/debug it.  I don't see any such
> options to fence_tool or fenced, and I'm thinking fence_manual will
> just manually fence the instance without running the configured fence_
> mechanism. 

There's fence_xen already in -head, maybe it does some of what you need
already?

-- Lon



--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster