On Mon, Feb 25, 2008 at 12:10 PM, Dejan Muhamedagic <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>  On Mon, Feb 25, 2008 at 11:27:38AM -0700, Serge Dubrouski wrote:
>  > I would love to do that and already tried it. Though we didn't come to
>  > agreement on how configuration parameters should look like.
>
>  Why? Was there a discussion on the list about it? The
>  configuration is a bit unusual. Other stonith agents take named
>  parameters. Though this kind of configuration also works, I'd
>  prefer something similar to the others, e.g.

Yes there was a discussion
http://lists.community.tummy.com/pipermail/linux-ha-dev/2007-February/

See "new stonith external plugin". The config parameter hostslist is
actually derived from original ssh plugin. I needed to have a full
list of all controlled nodes and preferred to have it as one
parameter.

>
>  hostname dom0 (or xenhost) config
>

That would work if I needed just a dom0 host, but I also need a list
of controlled nodes and probably configuration files.

>  Thanks,
>
>  Dejan
>
>
>
>  > So if you wish and have time please review it, let me know your
>  > thoughts and I'll be glad to make any changes. Allan already have my
>  > form submitted.
>
>  > On Mon, Feb 25, 2008 at 11:22 AM, Dejan Muhamedagic <[EMAIL PROTECTED]> 
> wrote:
>  > > Hi Serge,
>  > >
>  > >
>  > >  On Mon, Feb 25, 2008 at 10:27:10AM -0700, Serge Dubrouski wrote:
>  > >  > Plugin is attached. Put it into /usr/lib/stonith/plugins/external/.
>  > >
>  > >  Do you feel like contributing the thing? If so, you know the
>  > >  drill :)
>  > >
>  > >  Thanks,
>  > >
>  > >  Dejan
>  > >
>  > >
>  > >
>  > >  > And here is an example how to use it:
>  > >  >
>  > >  >        <clone id="DoFencing">
>  > >  >          <instance_attributes id="fence_attributes">
>  > >  >            <attributes>
>  > >  >              <nvpair id="fence_clone_max" name="clone_max" value="2"/>
>  > >  >              <nvpair id="fence_clone_node_max" name="clone_node_max" 
> value="1"/>
>  > >  >            </attributes>
>  > >  >          </instance_attributes>
>  > >  >          <primitive id="child_DoFencing" class="stonith"
>  > >  > type="external/xen0" provider="heartbeat">
>  > >  >            <operations>
>  > >  >              <op id="fence_monitor" name="monitor" interval="5s"
>  > >  > timeout="20s" prereq="nothing"/>
>  > >  >              <op id="fence_start" name="start" timeout="20s" 
> prereq="nothing"/>
>  > >  >            </operations>
>  > >  >            <instance_attributes id="fence_inst_attr">
>  > >  >              <attributes>
>  > >  >                <nvpair id="ssh_hostlist" name="hostlist"
>  > >  > value="fc-node1:home:/opt/xen/fedora-fc5/fc-node1.cfg
>  > >  > fc-node2:home:/opt/xen/fedora-fc5/fc-node2.cfg"/>
>  > >  >              </attributes>
>  > >  >            </instance_attributes>
>  > >  >          </primitive>
>  > >  >        </clone>
>  > >  >
>  > >  > You'll have to change this line:
>  > >  >
>  > >  > <nvpair id="ssh_hostlist" name="hostlist"
>  > >  > value="fc-node1:home:/opt/xen/fedora-fc5/fc-node1.cfg
>  > >  > fc-node2:home:/opt/xen/fedora-fc5/fc-node2.cfg"/>
>  > >  >
>  > >  > Here:
>  > >  > fc-node1/2 - name of Xen nodes,
>  > >  > home - name of Xen0 node,
>  > >  > /opt/xen/fedora-fc5/fc-node1/2.cfg - Path to config files for Xen
>  > >  > nodes. This can be skipped if config files are in /etc/xen directory
>  > >  > and named as node_name.cfg
>  > >  >
>  > >  > Sorry this syntax is kind of complex but it works for me.
>  > >  >
>  > >  >
>  > >  > On Mon, Feb 25, 2008 at 10:11 AM, Lino Moragon
>  > >  > <[EMAIL PROTECTED]> wrote:
>  > >  > > Serge Dubrouski schrieb:
>  > >  > >
>  > >  > > > I have a such plugin if you are interested in it.
>  > >  > >  I'm very interested in it :-) That would be very nice. Would you 
> post or
>  > >  > >   attach it?
>  > >  > >
>  > >  > >  Thanks,
>  > >  > >   Lino
>  > >  > >
>  > >  > >
>  > >  > >
>  > >  > >
>  > >  > >
>  > >  > >
>  > >  > >  > On Mon, Feb 25, 2008 at 8:35 AM, Lino Moragon <[EMAIL 
> PROTECTED]> wrote:
>  > >  > >  >> Hi List,
>  > >  > >  >>
>  > >  > >  >>  I've got a 2 Node HA-cluster running on a XEN Host.
>  > >  > >  >>  To fence the nodes I wanted to implement the external/ssh 
> plugin in
>  > >  > >  >>  order to fence the node if both configured heartbeat links on 
> 2 NICs
>  > >  > >  >>  went down.
>  > >  > >  >>
>  > >  > >  >>  My question: Is it possible to configure the plugin, so that 
> the good
>  > >  > >  >>  node, that has got network connectivity could connect through 
> ssh on the
>  > >  > >  >>  Xen Host and from there issue a 'xm destroy badnode' command?
>  > >  > >  >>
>  > >  > >  >>  I mean, if both NICs are down on the badnode there isn't a 
> posibility to
>  > >  > >  >>  connect through ssh, so only available solution would be to 
> connect to
>  > >  > >  >>  the xen-host.
>  > >  > >  >>
>  > >  > >  >>  Has anyone ever configured a plugin like that? Is there 
> perhaps a better
>  > >  > >  >>  option / solution?
>  > >  > >  >>
>  > >  > >  >>  Would I have to set up a resource clone or a set of 2 
> external/ssh
>  > >  > >  >>  resources on each node one?
>  > >  > >  >>
>  > >  > >  >>  Thanks for any hints, advice, suggestions.
>  > >  > >  >>
>  > >  > >  >>  Lino
>  > >  > >  >>
>  > >  > >  >>  _______________________________________________
>  > >  > >  >>  Linux-HA mailing list
>  > >  > >  >>  Linux-HA@lists.linux-ha.org
>  > >  > >  >>  http://lists.linux-ha.org/mailman/listinfo/linux-ha
>  > >  > >  >>  See also: http://linux-ha.org/ReportingProblems
>  > >  > >  >>
>  > >  > >  >
>  > >  > >  >
>  > >  > >  >
>  > >  > >
>  > >  > >  _______________________________________________
>  > >  > >  Linux-HA mailing list
>  > >  > >  Linux-HA@lists.linux-ha.org
>  > >  > >  http://lists.linux-ha.org/mailman/listinfo/linux-ha
>  > >  > >  See also: http://linux-ha.org/ReportingProblems
>  > >  > >
>  > >  >
>  > >  >
>  > >  >
>  > >  > --
>  > >  > Serge Dubrouski.
>  > >
>  > >
>  > >  > _______________________________________________
>  > >  > Linux-HA mailing list
>  > >  > Linux-HA@lists.linux-ha.org
>  > >  > http://lists.linux-ha.org/mailman/listinfo/linux-ha
>  > >  > See also: http://linux-ha.org/ReportingProblems
>  > >  _______________________________________________
>  > >  Linux-HA mailing list
>  > >  Linux-HA@lists.linux-ha.org
>  > >  http://lists.linux-ha.org/mailman/listinfo/linux-ha
>  > >  See also: http://linux-ha.org/ReportingProblems
>  > >
>  >
>  >
>  >
>  > --
>  > Serge Dubrouski.
>  > _______________________________________________
>  > Linux-HA mailing list
>  > Linux-HA@lists.linux-ha.org
>  > http://lists.linux-ha.org/mailman/listinfo/linux-ha
>  > See also: http://linux-ha.org/ReportingProblems
>  _______________________________________________
>  Linux-HA mailing list
>  Linux-HA@lists.linux-ha.org
>  http://lists.linux-ha.org/mailman/listinfo/linux-ha
>  See also: http://linux-ha.org/ReportingProblems
>



-- 
Serge Dubrouski.
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to