[Pacemaker] Fencing: Where?

[Michael Schwartzkopff]

Am Montag, 2. Dezember 2013, 13:15:23 schrieb Nikita Staroverov:
> > Hi,
> > 
> > as far as I unterstood RH is going to do all infrastructure in the cman
> > layer and user pacemaker only for resource management. Whith this setup
> > fencing also will be a job of the fenced of the cman package.
> > 
> > This design has its advantages: If descisions are taked on a low level,
> > all
> > parts of the cluster have the chance to know about theses descisions.
> > 
> > BUT: If pacemaker needs to fence a node, it has no possibility to so so
> > any
> > more. Imagine a resource will not stop and pacemaker would like to fence
> > that node to go on. How would that situation be handled with fencing in
> > cman?
> > 
> > Is there any way pacemaker can tell cman about it's wish to fence an other
> > nore?
> > 
> > The only solution I can think of is to delegate the fencing in cman to
> > pacemaker. So both layers are able to fence. But this cannot be a good
> > solution, since we have to setup fencing on two places.
> > 
> > Thanks for fruitful discussion.
> > 
> > 
> > Mit freundlichen Grüßen,
> > 
> > Michael Schwartzkopff
> 
> fence_pcmk does the job. Have you got any troubles with it?

No. I use it now. But setting up fencing in two places
- cman -> links to pacemaker
- pamcemaker

it not very nice to configure fencing in two places.

Is there any way that pacemaker can tell cman about it's fencing descisions?


-- 
Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131202/6d2f159d/attachment-0004.sig>