aboutsummaryrefslogtreecommitdiffstats
path: root/build-root/vagrant/Vagrantfile
AgeCommit message (Collapse)AuthorFilesLines
2016-05-07Small improvement to vagrant fileEd Warnicke1-5/+5
Change-Id: Ia85ed0ef55cb5da118289667d7b217d8890d487e Signed-off-by: Ed Warnicke <eaw@cisco.com>
2016-05-02Break out install.sh from build.shEd Warnicke1-0/+1
This is necessary because we are now using build.sh for CI... and we shouldn't install packages on CI boxes. Change-Id: I68f7880dfc75bbc4aa278ab0765a43e3fb899f3d Signed-off-by: Ed Warnicke <eaw@cisco.com>
2016-05-02VPP-32 Increase # cpus to 2, leave RAM at 4G for virtualbox vagrant usersKeith Burns (alagalah)1-1/+3
Change-Id: Ifb40316db96e019d6c14ff6a6e9653579009d4c3 Signed-off-by: Keith Burns (alagalah) <alagalah@gmail.com>
2016-04-25Break boostrap.sh into piecesEd Warnicke1-3/+6
In order to make it easier for folks who have existing Centos or Ubuntu boxes to utilize the same 'Getting started' scripting that is used in Vagrant, as well as enable us to use that scripting in CI, broke up bootstrap.sh into update.sh - Things like apt-get update build.sh - Install any dependencies and build vpp clearinterfaces.sh - Clean off any non-default gateway interfaces. Used by vagrant. run.sh - Start vpp as a service on the box. A user (or CI) just wanting to get going and build on an existing Ubuntu or Centos image (ie, not via vagrant) can simply run build.sh Change-Id: I8f19342f163cad07c6c05def943a5fb8e394b879 Signed-off-by: Ed Warnicke <eaw@cisco.com>
2016-04-11vagrant: libvirt configuration.Jeff Shaw1-2/+6
Configure the proxy, vcpu, and memory parameters for the libvirt provider. Change-Id: Id662e60f76b4b424d3a5d98929a44ef2587ef258 Signed-off-by: Jeff Shaw <jeffrey.b.shaw@intel.com>
2016-03-25Fix vagrant centos flavor to work with top level make fileEd Warnicke1-1/+1
Change-Id: I89044ed27130a036536ed33aba847034ed15ad7d Signed-off-by: Ed Warnicke <eaw@cisco.com>
2016-02-03Switched vagrant for ~/git/vpp to /vppEd Warnicke1-0/+16
build-root/vagrant/Vagrantfile was always mounting the vpp into /vpp Now rather than cloning it and building, we just use it as mounted. In order to let folks know what happened, a README.moved is copied into the ~/git/vpp so folks know what happened. In addition to make it easier for folks to do commits from withing the vagrant, we install git-review, and copy in the users .gitconfig and .gnupg directory. A couple of notes about this. VMWare goes much much faster in all cases. Virtualbox is a bit slower in the very first run (without ccache). One of the benefits of using the mounted /vpp though is that after your first vagrant up, you always have access to the .ccache, as it lives outside the vagrant, and so in steady state everything is faster. Change-Id: I2cd2c28181b3d7e664240dfe2249b5be3f1b9241 Signed-off-by: Ed Warnicke <eaw@cisco.com>
2016-01-18build - Vagrant template to get more emulated PCI NICsVincent JARDIN1-0/+9
For some testing, it an be usefull to have more physical NICS that DPDK's PMDs can bind to. Example to run vpp within a VM with 3 emulated NICs: export VPP_VAGRANT_NICS=3 vagrant up Change-Id: I82d70f21c0a9ceba126ab6620c3b869d590d8de1 Signed-off-by: Vincent JARDIN <vincent.jardin@6wind.com>
2015-12-14Fix to make it easy to use http proxy with VagrantEd Warnicke1-0/+7
Many thanks to Keith Burns for the suggestion. Change-Id: Iae52c8afd43357e955825fbafbad057c0e6a97c7 Signed-off-by: Ed Warnicke <eaw@cisco.com>
2015-12-08Initial commit of vpp code.v1.0.0Ed Warnicke1-0/+36
Change-Id: Ib246f1fbfce93274020ee93ce461e3d8bd8b9f17 Signed-off-by: Ed Warnicke <eaw@cisco.com>