[DRE-commits] [vagrant-libvirt] 63/77: Reorganize README to put porject creation steps together

[Antonio Terceiro]

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 11e29d04692e787c8fa44bd17ca8d29e4cce9766
Author: Brian Pitts <brian at polibyte.com>
Date:   Sun May 11 14:46:45 2014 -0500

    Reorganize README to put porject creation steps together
---
 README.md | 63 +++++++++++++++++++++++++++++++++++----------------------------
 1 file changed, 35 insertions(+), 28 deletions(-)

diff --git a/README.md b/README.md
index b75e0e5..43681e5 100644
--- a/README.md
+++ b/README.md
@@ -53,6 +53,8 @@ In RedHat, Centos, Fedora, ...
 
 ## Vagrant Project Preparation
 
+### Add Box
+
 After installing the plugin (instructions above), the quickest way to get
 started is to add Libvirt box and specify all the details manually within
 a `config.vm.provider` block. So first, add Libvirt box using any name you
@@ -62,6 +64,8 @@ want. This is just an example of Libvirt CentOS 6.4 box available:
 $ vagrant box add centos64 http://kwok.cz/centos64.box
 ```
 
+### Create Vagrantfile
+
 And then make a Vagrantfile that looks like the following, filling in your
 information where necessary. In example below, VM named test_vm is created from
 centos64 box.
@@ -74,7 +78,37 @@ Vagrant.configure("2") do |config|
 end
 ```
 
-### Libvirt Configuration Options
+### Start VM
+
+In prepared project directory, run following command:
+
+```
+$ vagrant up --provider=libvirt
+```
+
+Vagrant needs to know that we want to use Libvirt and not default VirtualBox.
+That's why there is `--provider=libvirt` option specified. Other way to tell
+Vagrant to use Libvirt provider is to setup environment variable
+`export VAGRANT_DEFAULT_PROVIDER=libvirt`.
+
+### How Project Is Created
+
+Vagrant goes through steps below when creating new project:
+
+1.	Connect to Libvirt localy or remotely via SSH.
+2.	Check if box image is available in Libvirt storage pool. If not, upload it to
+	remote Libvirt storage pool as new volume.
+3.	Create COW diff image of base box image for new Libvirt domain.
+4.	Create and start new domain on Libvirt host.
+5.	Check for DHCP lease from dnsmasq server.
+6.	Wait till SSH is available.
+7.	Sync folders and run Vagrant provisioner on new domain if
+	setup in Vagrantfile.
+
+
+### Libvirt Configuration
+
+### Provider Options
 
 Although it should work without any configuration for most people, this provider exposes quite a few provider-specific configuration options:
 
@@ -129,33 +163,6 @@ Vagrant.configure("2") do |config|
   # ...
 ```
 
-## Create Project - Vagrant up
-
-In prepared project directory, run following command:
-
-```
-$ vagrant up --provider=libvirt
-```
-
-Vagrant needs to know that we want to use Libvirt and not default VirtualBox.
-That's why there is `--provider=libvirt` option specified. Other way to tell
-Vagrant to use Libvirt provider is to setup environment variable
-`export VAGRANT_DEFAULT_PROVIDER=libvirt`.
-
-### How Project Is Created
-
-Vagrant goes through steps below when creating new project:
-
-1.	Connect to Libvirt localy or remotely via SSH.
-2.	Check if box image is available in Libvirt storage pool. If not, upload it to
-	remote Libvirt storage pool as new volume.
-3.	Create COW diff image of base box image for new Libvirt domain.
-4.	Create and start new domain on Libvirt host.
-5.	Check for DHCP lease from dnsmasq server.
-6.	Wait till SSH is available.
-7.	Sync folders and run Vagrant provisioner on new domain if
-	setup in Vagrantfile.
-
 ## Networks
 
 Networking features in the form of `config.vm.network` support private networks

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-ruby-extras/vagrant-libvirt.git