purpleidea/oh-my-vagrant

New maintainers and contributors welcome, but I'm not driving the
development at the moment. I'll try to review patches as they come.

We've moved into #vagrant, since activity was pretty quiet. Feel free to
"hilight"[sic] purpleidea if you have an Oh-My-Vagrant specific question.

Hopefully this won't cause any issues with code removal in the root dir.
This should probably only be used in special cases (like for a build ci
using vtest+) and probably shouldn't be mixed with other "system" types.
You should definitely not pick a project name that matches a built-in
system name, in particular if you want to use the two together!

This was a real mind bender, and finally I found the solution:
http://mywiki.wooledge.org/BashFAQ/089

This is a weird nested shell issue... If you can help figure out why it
passes normally, but fails on the centos-ci when single quotes are used,
I'd appreciate the patch!

These aliases and functions are defined in /etc/profile.d/* so without
-i, bash won't run as a login shell and won't receive these values. The
usual result is error code 127, or "command not found".

This adds a proper vssh implementation that supports the cd parameter,
-c for executing commands, and proper exit codes!

This is based on the article:

https://www.berrange.com/posts/2015/12/21/ceph-single-node-deployment-on-fedora-23/

It seems to work, except I don't know what to do next!

Happy hacking :)

This helps you kick off jenkins builds if you need to login before
kicking the special magic url. In my Jenkins instance this is called:
"Build Triggers" -> "Trigger builds remotely (e.g., from scripts)"
I had to set the "Authentication Token" to something manually. I used
`pwgen` to pick one!

It includes the mechanism to add a git post-push hook, because the git
developers refuse to add it which is sad.

Jenkins seems to run the script in some way requiring we force the
pseudo t. I'm now ready to just patch it like this and not care too much
about the details. If you're a Jenkins pro, and there's a better way,
please LMK.

This is mostly thanks to Vasyl Kaigorodov for kicking this off and actually adding the image building capabilities to vagrant-builder.

Thanks to Vasyl Kaigorodov for the original patch this is based on which
was the big motivator!

`--stdin` is not supported on Debian derivatives of `passwd` utility, use
another method to set root password.
Also if VM update requested - take this into account and call `apt-get` instead of
`yum`.