nocontrold: Eliminating ocfs2_controld v4
Get series with b4
b4 am 20131018230658.GC4490@localhostVersions newest first
- v1 Latest0 of 6 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 6 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Ocfs2-devel] [PATCH 0/6] nocontrold: Eliminating ocfs2_controld v4
Quoted 29 lines · Andrew Morton
Quoted 27 lines · On Fri, 18 Oct 2013 09:44:54 -0500 Goldwyn Rodrigues <[email protected]> wrote:
This is an effort of removing ocfs2_controld.pcmk and getting ocfs2 DLM handling up to the times with respect to DLM (>=4.0.1) and corosync (2.3.x). AFAIK, cman also is being phased out for a unified corosync cluster stack.
fs/dlm performs all the functions with respect to fencing and node management and provides the API's to do so for ocfs2. For all future references, DLM stands for fs/dlm code.
The advantages are:
+ No need to run an additional userspace daemon (ocfs2_controld)
+ No contrrold devince handling and controld protocol
+ Shifting responsibilities of node management to DLM layerFor backward compatibility, we are keeping the controld handling code. Once enough time has passed we can remove a significant portion of the code.
This feature requires modification in the userspace ocfs2-tools. The changes can be found at:
https://github.com/goldwynr/ocfs2-tools branch: nocontrold Currently, not many checks are present in the userspace code, but that would change soon.These changes were developed on linux-stable 3.11.y. However, the changes are applicable to the current upstream as well. If you wish to give the entire kernel a spin, the link is:
Quoted 5 lines
Quoted 1 line
https://github.com/goldwynr/linux-stable branch: nocontrold
I queued this up so it will get some linux-next exposure when Stephen gets back to his desk. But I don't feel I can take it further without suitable input from the other ocfs2 developers (please).
I thought I'd been pretty clear on the previous rounds. The code had some significant issues in its approach to compatibility (it wasn't). I haven't had a chance to look at this round yet, but I intend to soon.
Please do not forward this code without an explicit Acked-by from Mark or I.
Joel
Signature · 6 lines
Viro's Razor: Any race condition, no matter how unlikely, will occur just often enough to bite you. http://www.jlbec.org/ jlbec at evilplan.org