vpp/extras/vagrant/README
Dave Wallace d4c623eea4 Vagrant fails if Vagrantfile is a symlink on Windows 10.
- Revert Vagrantfile symlink to the default
- Update README and env.sh

Change-Id: Ib1a557b897e0217b162c31118a4c265769dd1760
Signed-off-by: Dave Wallace <dwallacelf@gmail.com>
2017-09-25 22:09:19 +00:00

44 lines
1.1 KiB
Plaintext

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