[DRE-commits] [vagrant-libvirt] 65/67: Add discussion of management network

Antonio Terceiro terceiro at moszumanska.debian.org
Sun Apr 24 13:56:08 UTC 2016


This is an automated email from the git hooks/post-receive script.

terceiro pushed a commit to annotated tag 0.0.14
in repository vagrant-libvirt.

commit 04c4d32c5d9297b9d91688b2c3642378117b9768
Author: Brian Pitts <brian at polibyte.com>
Date:   Mon Jan 20 15:55:25 2014 -0600

    Add discussion of management network
---
 README.md | 27 +++++++++++++++++----------
 1 file changed, 17 insertions(+), 10 deletions(-)

diff --git a/README.md b/README.md
index 48e9b54..a8d3380 100644
--- a/README.md
+++ b/README.md
@@ -99,8 +99,6 @@ This provider exposes quite a few provider-specific configuration options:
 * `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)
 * `storage_pool_name` - Libvirt storage pool name, where box image and instance snapshots will be stored.
-* `management_network_name` - Name of libvirt network to which all VMs will be connected. If not specified the default is 'vagrant-libvirt'.
-* `management_network_address` - Address of network to which all VMs will be connected. Must include the address and subnet mask. If not specified the default is '192.168.121.0/24'.
 
 ### Domain Specific Options
 
@@ -236,15 +234,24 @@ starts with 'libvirt__' string. Here is a list of those options:
   Default mode is 'bridge'.
 * `:mac` - MAC address for the interface.
 
-## Obtaining Domain IP Address
+### Management Network
+
+Vagrant-libvirt uses a private network to perform some management operations
+on VMs. All VMs will have an interface connected to this network and
+an IP address dynamically assigned by libvirt. This is in addition to any
+networks you configure. The name and address used by this network are
+configurable at the provider level.
+
+* `management_network_name` - Name of libvirt network to which all VMs will be connected. If not specified the default is 'vagrant-libvirt'.
+* `management_network_address` - Address of network to which all VMs will be connected. Must include the address and subnet mask. If not specified the default is '192.168.121.0/24'.
 
-Libvirt doesn't provide standard way how to find out an IP address of running
-domain. But we know, what is MAC address of virtual machine. Libvirt is closely
-connected with dnsmasq server, which acts also as a DHCP server. Dnsmasq server
-makes lease information public in `/var/lib/libvirt/dnsmasq` directory, or in
-`/var/lib/misc/dnsmasq.leases` file on some systems. This is the place, where
-information like which MAC address has which IP address resides and it's parsed
-by vagrant-libvirt plugin.
+You may wonder how vagrant-libvirt knows the IP address a VM received.
+Libvirt doesn't provide a standard way to find out the IP address of a running
+domain. But we do know the MAC address of the virtual machine's interface on
+the management network. Libvirt is closely connected with dnsmasq, which acts as
+a DHCP server. dnsmasq writes lease information in the `/var/lib/libvirt/dnsmasq`
+directory. Vagrant-libvirt looks for the MAC address in this file and extracts
+the corresponding IP address.
 
 ## SSH Access To VM
 

-- 
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