Tom Jones c3b416c492 build: Explicitly use bash for shell scripts
VPP requires bash for all shell scripts. Align shebang lines in build
and test scripts to look up the location of bash rather than hard coding
'/bin/bash'.

Look up the location of bash for makefiles.

Type: improvement
Change-Id: I23b705d81d60389fa8af61c680cf0abd74f0ea24
Signed-off-by: Tom Jones <thj@freebsd.org>
2024-01-19 12:30:01 +00:00
..
2017-04-20 12:57:33 +00:00
2018-08-14 20:16:51 +00:00
2020-09-21 06:59:48 +00:00
2017-04-20 12:57:33 +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