[Pacemaker] Fencing of bare-metal remote nodes

[David Vossel]

----- Original Message -----
> 25.11.2014 23:41, David Vossel wrote:
> >
> >
> > ----- Original Message -----
> >> Hi!
> >>
> >> is subj implemented?
> >>
> >> Trying echo c > /proc/sysrq-trigger on remote nodes and no fencing occurs.
> >
> > Yes, fencing remote-nodes works. Are you certain your fencing devices can
> > handle
> > fencing the remote-node? Fencing a remote-node requires a cluster node to
> > invoke the agent that actually performs the fencing action on the
> > remote-node.
> 
> David, a couple of questions.
> 
> I see that in your fencing tests you just stop systemd unit.
> Shouldn't pacemaker_remoted somehow notify crmd that it is being
> shutdown? And shouldn't crmd stop all resources on that remote node
> before granting that shutdown?

yes, this needs to happen at some point.

Right now the shutdown method for a remote-node is to disable the connection
resource and wait for all the resources to stop before killing pacemaker_remoted
on the remote node. That isn't exactly ideal.


> Also, from what I see now it would be natural to hide current
> implementation of remote node configuration under <node/> syntax. Now
> remote nodes do have almost all features of normal nodes, including node
> attributes. What do you think about it?

ha, well. yes. at this point that might make sense. I had originally never
planned on remote-nodes entering the actual <nodes> section, but eventually
that changed. I'd like for usage of remote nodes to mature a bit before I
commit to changing something like this though. I'm still a bit uncertain how
people are going to use baremetal remote nodes. The use cases people come
up with keep surprising me.  Keeping the remote node definition as a resource
gives us a bit more flexibility for configuration.

-- Vossel

> 
> Best,
> Vladislav
> 
> >
> > -- Vossel
> >
> >>
> >> Best,
> >> Vladislav
> >>
> >> _______________________________________________
> >> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >>
> >> Project Home: http://www.clusterlabs.org
> >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> >> Bugs: http://bugs.clusterlabs.org
> >>
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >
> > Project Home: http://www.clusterlabs.org
> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org
> >
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>