Please help me to help testing the Salt provisioner

[Oliver Bestwalter]

Hello,

since I am using vagrant with the salt provisioner I noticed quite a few breakages that could have been caught quite easily had someone actually exercised the code with some standard settings on the mainstream distros. I understand that vagrant is a ruby project and that the ruby based provisioners get more love. It's o.k. I don't complain :)

As an example: Vagrant + Salt + Windows remains broken for over a year now (https://groups.google.com/forum/#!searchin/vagrant-up/bestwalter/vagrant-up/kY8IVXrKTBA/t5sHKuLSDAUJ)

I would really appreciate some information to help me get started with testing:

1. I am at home in Python and my complete knowledge of Ruby comes from writing Vagrantfiles, so my capabilites there are still quite limited, but I would really like to be able to run the development version of vagrant from my clone on the Linux host, to test fixes and reproduce bugs. I got the testing to run like described in the README, but I am at sea how to use the local vagrant clone to spin up boxes. Is there a Howto for people like me who are not conversant in the ruby ecosystem yet?

2. What kind of testing do you have in place to ensure the provisioners work correctly. Is there something automated in place already? I am pushing this topic in the salt community to integrate wndows vagrant boxes as part of testing Windows in Salt development. The other side of the equation would be to spin up windows vagrant boxes using the different provisioners with the development branch of Salt to ensure that no regressions creep in.

3. How is the release process for vagrant? Do you have roadmaps, release dates, release candidates?

thanks

Oliver

[Oliver Bestwalter]

P.S. I am doucumenting progress here: https://trello.com/b/vywwuncS/ci-for-salt-vagrant-windows

[Oliver Bestwalter]

Hi,

o.k. I found a github wiki entry (went completely under my radar) that explains how to get a vagrant install from dev: https://github.com/mitchellh/vagrant/wiki/Installing-Vagrant-from-source - problem is: it does not work out of the box, if you have a current version of bundle installed as the dev branch of vagrant relies on an old version of bundler. I managed to install the older version in parallel and explicitly call it with "bundle _1.5.2_ install", but "rake install" fails with the same problem and I wasn't able to figure out yet how to tell rake it should use the old version as well.

I updated the WIKI to the point where I got and would appreciate if somebody could help me with the last step.

cheers

Oliver

(went completely under my radar) entry that epxlin

[AD.]

Hi Oliver,

I'm in a similar boat :)

I'm just now picking up a partially completed project of mine that's been shelved since last year and have run into plenty of regressions and plain old changes as I bring the various components up to date. There's a lot of moving parts.

eg: Vagrant 1.6.x -> 1.7.x, Packer 0.6.x -> 0.8.x, Salt 2014.1 -> 2015.x, Ubuntu 12.04 -> 14.04, and Windows 2008R2 -> 2012R2. And moving the Windows communicators from cygwin SSH/Bash to WinRM/Powershell. Things would be much easier without Windows that's for sure.

Although I'm not a devloper, I'm ok with Python. My only tiny Ruby experience though is (ironically I suppose) submitting a minor vagrant salt provisioner (on Windows) fix last year. I suspect Packer will be sending me to the Go tutorial too.

I'll look through your Trello board to see if I can help out anywhere.

Cheers

Anton 

[Oliver Bestwalter]

Hi Anton,

I am still unable to install vagrant from source due to a bundler versioning issue. 

I opened an issue for that now: https://github.com/mitchellh/vagrant/issues/6183

The Ruby ecosystem is a bit of a mystery to me, so I hope somebody will chip in and update the docs.

cheers

Oliver

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/2vBhQMYsqn4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/405eb91d-006e-4539-ba51-5cc324db2d39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Oliver Bestwalter]

Hi,

Brain Suh posted a different way to install vagrant from master here: https://github.com/mitchellh/vagrant/issues/5973#issuecomment-137276605 (Bonus at end of the comment).

Could one of the @hashicorpers comment on the feasibility of that approach? If this is o.k. then we could update the Wiki with that.

Thanks

Oliver