Il 27-07-2017 03:59 Digimer ha scritto:
To clarify; The clustered locking in clvmd doesn't do anything to
restrict access to the storage, it's job is only to inform other nodes
that something changing on the underlying shared storage when it makes
a
change.
Hi Digimer,
yes, I am full aware of that.
To make sure a VM runs on only one node at a time, then you must use
pacemaker to handle that (and stonith to prevent split-brains, but I am
sure you know that already).
If you use clvmd on top on DRBD, make your life simple and don't use it
below DRBD at the same time. It's technically possible but it is
needless complexity. You seem to already be planning this, but just to
make it clear.
Also note; If you don't use clvmd, then you will probably need to do a
pv/vg/lvscan to pick up changes. This is quite risky though and
certainly not recommended if you run DRBD in dual-primary.
Thanks for your input. I also read your excellent suggestions on link
Igor posted.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.da...@assyoma.it - i...@assyoma.it
GPG public key ID: FF5F32A8
_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user
