Vagrant on Linux + Windows Guest (VirtualBox) + Salt Provider: any luck?

[Oliver Bestwalter]

Hi,

I am trying to get this combination to work and basically inherited it from a co worker who also did not get it to work over the course of the last year. So my hunch is that this combination is completely broken for at least a year.

Can anyone proof me wrong (and tell me, how it's done)?

If somebody is interested in the details: I am collecting the show stopper bugs in both projects here:

https://trello.com/c/z8BKiSos/5-salt-bugs

https://trello.com/c/iO1En6lR/2-vagrant-bugs

Cheers

Oliver

P.S. I am also asking on the salt users list (https://groups.google.com/forum/#!topic/salt-users/H8pc6-Yue4Q).

[Oliver Bestwalter]

Anyone?

[Shawn Neal]

This doesn't sound like a combination that many people use, myself included. I remember helping you with one of the Vagrant/Salt issues. If there are more Vagrant issues please file GitHub issues, I'd love to get them fixed.

[Oliver Bestwalter]

Hi Shawn,

thanks you for your reply. No new bugs need to be filed. The bugs involved from the Vagrant and Salt projects are all known already (hopefully) and I collected them in a Trello Board (vagrant bugs are here: https://trello.com/c/iO1En6lR/2-vagrant-bugs). A few are already resolved in develop or are in the process of being resolved. I am slowly getting involved on the Salt side of things, but in Vagrant I am pretty much just a user still.

I have a few more questions, maybe you can answer them for me or point me to the right place?

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. Is there a way to tell the provisioner in the Vagrantfile that it should use a different version of Salt on windows? 

Last but not least: when will the next release of Vagrant be is there a roadmap or timeline somewhere?

Cheers

Oliver

--
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/kY8IVXrKTBA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.