c2e63feb62
The top-level Makefile in VPP already uses the file /etc/os-release to recognize which OS the build is being performed on. The scripts for vagrant images instead were still using different files for different distros and adding a new distro to be supported causes issues with the extra-logic to deal with it. This patch aligns the vagrant scripts to use the same approach followed by the top-level Makefile and simplifies the steps to identify / update the OS and build / run VPP. Change-Id: I539f4a7c27b3fef70ed1c12b0276049bc47dc289 Signed-off-by: Marco Varlese <marco.varlese@suse.com>
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