Move vagrant stuff to extras/ 93/6293/3
authorDamjan Marion <damarion@cisco.com>
Thu, 20 Apr 2017 09:43:56 +0000 (11:43 +0200)
committerNeale Ranns <nranns@cisco.com>
Thu, 20 Apr 2017 12:57:33 +0000 (12:57 +0000)
Change-Id: I7e3d6ecc3f23d862004c273e23e36e234ceb6015
Signed-off-by: Damjan Marion <damarion@cisco.com>
12 files changed:
README.md
build-root/vagrant [new symlink]
extras/vagrant/.gitignore [moved from build-root/vagrant/.gitignore with 100% similarity]
extras/vagrant/README [moved from build-root/vagrant/README with 100% similarity]
extras/vagrant/Vagrantfile [moved from build-root/vagrant/Vagrantfile with 100% similarity]
extras/vagrant/WELCOME [moved from build-root/vagrant/WELCOME with 100% similarity]
extras/vagrant/build.sh [moved from build-root/vagrant/build.sh with 100% similarity]
extras/vagrant/clearinterfaces.sh [moved from build-root/vagrant/clearinterfaces.sh with 100% similarity]
extras/vagrant/env.sh [moved from build-root/vagrant/env.sh with 100% similarity]
extras/vagrant/install.sh [moved from build-root/vagrant/install.sh with 100% similarity]
extras/vagrant/run.sh [moved from build-root/vagrant/run.sh with 100% similarity]
extras/vagrant/update.sh [moved from build-root/vagrant/update.sh with 100% similarity]

index b70103f..7f429d1 100644 (file)
--- a/README.md
+++ b/README.md
@@ -67,7 +67,7 @@ To install system dependencies, build VPP and then install it, simply run the
 build script. This should be performed a non-privileged user with `sudo`
 access from the project base directory:
 
-    ./build-root/vagrant/build.sh
+    ./extras/vagrant/build.sh
 
 If you want a more fine-grained approach because you intend to do some
 development work, the `Makefile` in the root directory of the source tree
@@ -79,7 +79,7 @@ interest. To see the available targets run:
 
 ### Quick-start: Vagrant
 
-The directory `build-root/vagrant` contains a `VagrantFile` and supporting
+The directory `extras/vagrant` contains a `VagrantFile` and supporting
 scripts to bootstrap a working VPP inside a Vagrant-managed Virtual Machine.
 This VM can then be used to test concepts with VPP or as a development
 platform to extend VPP. Some obvious caveats apply when using a VM for VPP
diff --git a/build-root/vagrant b/build-root/vagrant
new file mode 120000 (symlink)
index 0000000..ada25b8
--- /dev/null
@@ -0,0 +1 @@
+../extras/vagrant
\ No newline at end of file