Damjan Marion 4a6cb83d33 rename vpp-dpdk-dev to vpp-ext-deps
We need to have new tenants in the development package.
This is first of series of patches which will allow us to have multiple
external libs and tools packaged for developer's convenience.

Change-Id: I884bd75fba96005bbf8cea92774682b2228e0e22
Signed-off-by: Damjan Marion <damarion@cisco.com>
2018-09-20 14:30:54 +02:00
..
2018-08-14 20:16:51 +00:00
2018-08-14 20:16:51 +00:00
2018-08-14 20:16:51 +00:00
2018-08-14 20:16:51 +00:00
2018-08-14 20:16:51 +00:00

INTRO:

This is a vagrant environment for VPP.

VPP currently works under Linux and has support for:

- Ubuntu 16.04 and Centos7.2

The VM builds VPP from source which can be located at /vpp

VM PARTICULARS:
This vagrant environment creates a VM based on environment variables found in ./env.sh
To customize the vm for your use case, edit env.sh then
  source ./env.sh
  vagrant up

By default, the VM created is/has:
- Ubuntu 16.04
- 2 vCPUs
- 4G of RAM
- 3 NICs (1 x NAT - host access, 2 x VPP DPDK enabled)

PROVIDERS:

Supported vagrant providers are:

- Virtualbox, VMware Fusion/Workstation, Libvirt

ALTERNATE CONFIGURATIONS

The following Vagrantfiles provide alternate configurations for specific testing purposes.  To use them,

1. Copy the desired configuration to Vagrantfile
2. Run "vagrant up"
3. vagrant ssh <vm name>

When testing is complete
4. Run "vagrant destroy" to stop the VM's and delete files.
5. Run "git checkout -- Vagrantfile" to restore the default configuration

Available Vagrantfiles:

Vagrantfile.vcl_test  - Create two vm's for multi-host VppCommLib testing