I think that has the potential to be a brilliant solution. Could you push a gerrit so its easy for folks to grab it to try and see how it goes?
Ed On Tue, Dec 20, 2016 at 11:15 AM, Kinsella, Ray <ray.kinse...@intel.com> wrote: > Hi Ed, > > For those of us that have to suffer a corporate firewall with a socks > proxy this is problematic. It stalls on the git clone as vagrant-proxy > doesn't take care of setting up the socks proxy. > > And to be honest, I wouldn't feel comfortable for vagrant-proxy to start > copying my ssh_config and keys to the vagrant box. In addition cloning vpp > a second time, inside the vagrant box feels alot like duplication of > network bits. > > Can I propose a simpler work-around, using rsync instead of nfs to copy > (instead of share) the vpp folder to the vagrant box. > > config.vm.synced_folder "../../", "/vpp", type: "rsync", > rsync__auto: false, > rsync__exclude: [ > "build-root/build*/", > "build-root/install*/", > "build-root/images*/", > "build-root/*.deb", > "build-root/*.rpm", > "build-root/*.changes", > "build-root/python", > "build-root/deb/debian/*.dkms", > "build-root/deb/debian/*.install", > "build-root/deb/debian/changes", > "build-root/tools"] > > Seems to work fine, and means we can remove the 'clone.sh' script. > What do you think? > > Regards, > > Ray K > > On 13/12/2016 18:20, Ed Warnicke wrote: > >> Ray, >> >> The reason is because vagrant produces a bunch of 'issues' when trying >> to build from a 'mounted' share. >> >> When running vagrant, /vpp gets mounted with where ever the source is >> *outside* the vagrant VM >> >> Once inside, if you try to build from /vpp, a variety of things can and >> do break sadly :( >> >> So we clone vpp again into the local-to-the-VM storage. >> >> Does that answer your question? >> >> Ed >> >> On Tue, Dec 13, 2016 at 10:47 AM, Kinsella, Ray <ray.kinse...@intel.com >> <mailto:ray.kinse...@intel.com>> wrote: >> >> Folks, >> >> Two QQ on clone.sh >> (https://git.fd.io/vpp/tree/build-root/vagrant/clone.sh >> <https://git.fd.io/vpp/tree/build-root/vagrant/clone.sh>) >> >> >> 1. Why are we re-cloning source already available in /vpp? >> 2. Why do we ssh to remote server on the third last line ? >> (this presumably hangs?). >> >> Ray K >> >> >> # Setup the vpp code >> cd ~vagrant/ >> sudo -u vagrant mkdir git >> cd git/ >> echo "SSH_AUTH_SOCK $SSH_AUTH_SOCK x" >> chmod 777 $SSH_AUTH_SOCK >> >> CLONE_URL=`cd /vpp;git remote -v | grep origin |grep fetch |awk >> '{print $2}'` >> echo "CLONE_URL $CLONE_URL" >> echo $CLONE_URL | grep -q "^ssh:" >> if [ $? == 0 ]; then >> SSH_HOST=`echo $CLONE_URL| awk -F/ '{print $3}'` >> SSH_PORT=`echo $SSH_HOST| awk -F: '{print $2}'` >> if [ -n $SSH_PORT ]; then >> SSH_PORT="-p $SSH_PORT" >> fi >> SSH_HOST=`echo $SSH_HOST| awk -F: '{print $1}'` >> echo "SSH_HOST $SSH_HOST" >> echo "SSH_PORT $SSH_PORT" >> sudo -HE -u vagrant ssh -oStrictHostKeyChecking=no -v $SSH_PORT >> $SSH_HOST >> fi >> sudo -HE -u vagrant git clone $CLONE_URL >> _______________________________________________ >> vpp-dev mailing list >> vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> >> https://lists.fd.io/mailman/listinfo/vpp-dev >> <https://lists.fd.io/mailman/listinfo/vpp-dev> >> >> >>
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
