vagrant is not stable

[mozilla]

vagrant is not stable

[tofumatt]

I'm working on this and mostly there... but I agree. Specifics aren't needed; I know there are issues and what most of 'em are.

This is mega-important.

[readevalprint]

Excellent, and feel free to go specific and educate us. Most of my Vagrant bigotry stems from ignorance.

[tofumatt]

So one of my biggest issues is that it's hard to create a working box from scratch because the whole VM setup isn't in puppet. This doesn't matter until you wanna change the VM a bit but don't want to use the previous box as a starting point.

Example: our current box has LDAP server and a bunch of other unneeded things on it. I'm trying to get it so that you can use the puppet scripts to setup the box, but then we can package it so it's fast to use/setup/reboot/etc. I'm struggling with elasticsearch's jdk stuff and getting oh-my-zsh to install specifically, but the point is that our vagrant VM is like a git repo with an up-to-date vendor but a (very) stale requirements.txt to use a weird analogy.

Unless you're having Virtualbox/vagrant version mismatch or Ruby issues, the issues aren't with vagrant/puppet/etc. per se, but more with us being relative vagrant novices and Mozillians having a hard-to-reproduce-easily VM setup. So that's what I'm trying to fix.

(Hopefully that helps at least shed some light on things?)

[readevalprint]

Interesting, I removed moved the pip requirements around a bit today. Also, not sure if it's best, but the instructions say to run ./manage.py sycndb/migrate so they shouldn't be needed in puppet.
https://github.com/readevalprint/mozillians/compare/requirements

[tofumatt]

I've fixed up the vagrant pretty well I think; if there are anymore issues with it please reopen this issue.