Re: [PATCH 4/4] Add documentation for configuration lock managers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/24/2011 07:02 AM, Daniel P. Berrange wrote:
> Add a page which documents how to configure lock managers,
> focusing on use of sanlock with the QEMU/KVM driver
> 
> * docs/locking.html.in: Docs about lock managers
> * docs/sitemap.html.in: Add lock manager config to
>   the deployment section
> ---
>  docs/locking.html.in |  212 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  docs/sitemap.html.in |    4 +
>  2 files changed, 216 insertions(+), 0 deletions(-)
>  create mode 100644 docs/locking.html.in

Docs are always nice!

> +    <p>
> +      Once the sanlock daemon is running, the next step is to
> +      configure the libvirt sanlock plugin. There is a separate
> +      configuration file for each libvirt driver that is using
> +      sanlock. For QEMU, we will edit <code>/etc/libvirt/qemu-sanlock.conf</code>
> +      There is one mandatory parameter that needs to be set,
> +      the <code>host_id</code>. This is a integer between
> +      1 and 2000, which must be set to a <strong>unique</strong>
> +      value on each host running virtual machines

How does this fit in with the max_hosts configuration value?

> +    <p>
> +      The sanlock plugin needs to create leases in a directory
> +      that is on a filesystem shared between all hosts running
> +      virtual machines. Obvious choices for this include NFS,
> +      or GFS2. The libvirt sanlock plugin expects its lease

When listing two items, no comma is necessary: s/NFS,/NFS/

> +    <p>
> +      The QEMU/KVM driver is fully integrated with the lock
> +      manager framework as of release <span>0.9.3</span>.
> +      The out of the box configuration, however, currently
> +      uses the <strong>nop</strong> lock manager plugin.
> +      To get protection for disks, it is thus neccessary

s/neccessary/necessary/

> +    <p>
> +      It should be obvious that for locking to work correctly, every
> +      host running virtual machines should have storage configured
> +      in the same way. The easiest way todo this is to use the libvirt

s/todo/to do/

ACK with nits fixed.

-- 
Eric Blake   eblake@xxxxxxxxxx    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]