Improvements to vagrant/chef to make more customizable #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is related to issue #9 and composed of:
About proxy bug
On old Vagrantfile, the proxy session doesn't work because Vagrant don't support two calls on provision block. More info here: http://stackoverflow.com/questions/13065576/override-vagrant-configuration-settings-locally-per-dev
About solo.local.json
Now it's possible to overwrite solo.json with solo.local.json. Basically, we use this solo.local to change openruko's home and to reject some chef recipes we don't need using
reject_run
field.About vagrant_common.rb
It's the way we found to share common helpers on both cluster and standalone Vagrantfiles.
Note
Guys, i found this that can help us, https://github.com/puppetlabs/puppetlabs-openstack_dev_env. This is Openstack's builder, using puppet. We can extract some ideas from their Vagrantfile to help us improve local customizations.