On Tue, Jun 28, 2011 at 11:10:57AM -0600, Eric Blake wrote:
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?
max_hosts is dead now, so the range is 1->2000 as the docs
say here, instead of the previous '1->max_hosts'.
Daniel
--
|:
http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|:
http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|