[DRE-commits] [vagrant-libvirt] 73/77: Update README.md for new config option `uri`
Antonio Terceiro
terceiro at moszumanska.debian.org
Sun Apr 24 13:56:41 UTC 2016
This is an automated email from the git hooks/post-receive script.
terceiro pushed a commit to annotated tag 0.0.17
in repository vagrant-libvirt.
commit acff56864a0d1080722b408dffc340b805247b6d
Author: Jake Teton-Landis <just.1.jake at gmail.com>
Date: Mon Jun 9 00:12:50 2014 -0700
Update README.md for new config option `uri`
Documents changes in justjake at 95a750817f87cbc00c7eff896ca6d6e74b2ca5b1
---
README.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 0e8c29c..ab3293f 100644
--- a/README.md
+++ b/README.md
@@ -113,7 +113,7 @@ Vagrant goes through steps below when creating new project:
### Provider Options
-Although it should work without any configuration for most people, this provider exposes quite a few provider-specific configuration options:
+Although it should work without any configuration for most people, this provider exposes quite a few provider-specific configuration options. The following options allow you to configure how vagrant-libvirt connects to libvirt, and are used to generate the [libvirt connection URI](http://libvirt.org/uri.html):
* `driver` - A hypervisor name to access. For now only kvm and qemu are supported.
* `host` - The name of the server, where libvirtd is running.
@@ -122,6 +122,10 @@ Although it should work without any configuration for most people, this provider
* `password` - Password to access Libvirt.
* `id_ssh_key_file` - The id ssh key file name to access Libvirt (eg: id_dsa or id_rsa or ... in the user .ssh directory)
* `socket` - Path to the libvirt unix socket (eg: /var/run/libvirt/libvirt-sock)
+* `uri` - For advanced usage. Directly specifies what libvirt connection URI vagrant-libvirt should use. Overrides all other connection configuration options.
+
+Connection-independent options:
+
* `storage_pool_name` - Libvirt storage pool name, where box image and instance snapshots will be stored.
Here is an example of how to set these options.
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-ruby-extras/vagrant-libvirt.git
More information about the Pkg-ruby-extras-commits
mailing list