Conversation
404a35e to
3073063
Compare
…chine Signed-off-by: Rafael Chacon <rafael@slack-corp.com>
Signed-off-by: Rafael Chacon <rafael@slack-corp.com>
Signed-off-by: Rafael Chacon <rafael@slack-corp.com>
Signed-off-by: Rafael Chacon <rafael@slack-corp.com>
| # If possible, use nfs, this gives a good boost to IO operations in the VM. | ||
| # if you run into with nfs, just remove this from the synced folder | ||
|
|
||
| config.vm.synced_folder ".", "/vagrant/src/vitess.io/vitess", type: "nfs" |
There was a problem hiding this comment.
this PR reminds me of something @rafael :)
FYI: the previous nfs bug in Vagrant/Virtualbox -> macOS that didn't allow us to use it it's now fixed in the latest High Sierra release.
There was a problem hiding this comment.
I'm still having issues with nfs, even on High Sierra. :-(
There was a problem hiding this comment.
Oh really :( - Which issues? I'm High Sierra, working for me.
There was a problem hiding this comment.
mount.nfs: Connection timed out
Is what I'm getting.
|
Why Vagrant instead of Docker? |
|
@tirsen - I'm not sure if this still holds because I haven't tried Docker + Vitess + Mac in more than a year, but I ran into many issues where it was really hard to get the tests passing with Docker. The main problem was that integration tests where too heavy in IO and many tests ended up timing out. So running them locally in docker was too flaky. |
Desc
Long overdue promise of having a Vagrantfile for Vitess project. The following allows people to quickly set up a Vitess development environment.
@sougou - If you think this is good to merge, I can follow up with other PR's to add this to the docs.
I tested this Vagrantfile in a ubuntu machine and in Mac OS. VirtualBox seems to work better in mac OS (the VM runs more smoothly there and tests/building run faster, but the setup works in both cases).
cc: @dweitzman
Usage
There are also scripts to start/stop a Vitess clusters that have port forwarding setup to the local machine.