diff options
| author |   Damjan Marion <damarion@cisco.com> | 2017-04-20 11:43:56 +0200 |
|---|---|---|
| committer |   Neale Ranns <nranns@cisco.com> | 2017-04-20 12:57:33 +0000 |
| commit | 48009e4c5732180ecc951ac6359b9b96d38b8dc2 (patch) | |
| tree | d370b842a5be1eb47c4aed5fcae76a659eaa9224 /README.md | |
| parent | 686c1c8454803e48d45428a720f129f24dc981f7 (diff) | |
Move vagrant stuff to extras/
Change-Id: I7e3d6ecc3f23d862004c273e23e36e234ceb6015
Signed-off-by: Damjan Marion <damarion@cisco.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md index b70103fb1fc..7f429d12b31 100644 --- 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 |