Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
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>
|
|
Many thanks to Keith Burns for the suggestion.
Change-Id: Iae52c8afd43357e955825fbafbad057c0e6a97c7
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|
|
Change-Id: Ib246f1fbfce93274020ee93ce461e3d8bd8b9f17
Signed-off-by: Ed Warnicke <eaw@cisco.com>
|