Thomas F Herbert 7b75d211ae Fix for broken vagrant installs when using Vagrant 1.8.5.
I upgraded Fedora23 which installed kernel 4.6.4 which in turn required
VirtualBox 5.1.2 which in turn required Vagrant 1.8.5.

Workaround for a change in Vagrant 1.8.5 that breaks Centos. The
newer version of Vagrant doesn't chmod the ssh directory before trying to copy
new public key during installs. This will be fixed upstream in Vagrant 1.8.6.
Bug doesn't affect Ubuntu because it uses a different umask whereas Centos uses
0002.

Change-Id: I8108d4cc208fc47fa69f8a5cf27b2bba7e34293e
Signed-off-by: Thomas F Herbert <therbert@redhat.com>
2016-08-02 14:20:21 +00:00
..
2016-06-25 03:50:28 -07:00

INTRO:

This is a vagrant environment for VPP.

VPP currently works under Linux and has support for:

- Ubuntu 14.04, 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 use, edit env.sh then
  source ./env.sh
  vagrant up

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

PROVIDERS:

Supported vagrant providers are:

- Virtualbox, VMware Fusion/Workstation, Libvirt