On 02/16/2015 04:59 AM, Daniel P. Berrange wrote:
Introduce some basic docs describing the virtlockd setup.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com> --- docs/locking-lockd.html.in | 160 +++++++++++++++++++++++++++++++++++++++++++++ docs/locking.html.in | 2 +- docs/sitemap.html.in | 4 ++ 3 files changed, 165 insertions(+), 1 deletion(-) create mode 100644 docs/locking-lockd.html.in
+ <p> + The virtlockd daemon is a single purpose binary which + focus exclusively on the task of acquiring and holding
s/focus/focuses/
+ locks on behalf of running virtual machines. It is + designed to offer a low overhead, portable locking + scheme can be used out of the box on virtualization + hosts with minimal configuration overheads. It makes + use of the POSIX fcntl advisory locking capability + to hold locks, which is supported by the majority of + commonly used filesystems
s/$/./
+ </p> + + <h2><a name="sanlock">virtlockd daemon setup</a></h2> + + <p> + In most OS, the virtlockd daemon itself will not require + any upfront configuration work. It is installed by default + when libvirtd is present, and a systemd socket unit is + registered such that the daemon will be automatically + started when first required. With OS that predate systemd + though, it will be neccessary to start it at boot time,
s/neccessary/necessary/
+ <p> + The default behaviour of the lockd plugin is to acquire locks + directly on the virtual disk images associated with the guest + <disk> elements. This ensures it can run out of the box + with not configuration, providing locking for disk images on
s/not/no/ -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org