Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support chef-server #2

Closed
adamhjk opened this issue Mar 9, 2010 · 3 comments
Closed

Support chef-server #2

adamhjk opened this issue Mar 9, 2010 · 3 comments

Comments

@adamhjk
Copy link

adamhjk commented Mar 9, 2010

In addition to the current chef-solo support, support building vagrant boxes from a chef-server.

@mitchellh
Copy link
Contributor

Adam,

I'll be actively learning about chef server and how best to integrate it into Vagrant ASAP. =]

@mitchellh
Copy link
Contributor

Adam,

An update on this. I've been working in the 'flexible-provisioning' branch to support this gracefully and I finished the chef server provisioner tonight. I tested it and it worked :) (provisioned a lamp server super quick!) I'm going to continue working in this branch to add a few more things to chef-solo and also to make the config easier to use (easier to add recipes and so on). But for now this is working like so...

In the Vagrantfile:

config.vm.provisioner = :chef_server
config.chef.chef_server_url = "http://myserver.com:4000"
config.chef.validation_key_path = "/path/to/my/validation.pem"

And that's it! vagrant up and away you go.

The base box currently has chef 0.7.x though so I'm going to have to fix that as well.

Mitchell

@mitchellh
Copy link
Contributor

Adam,

Chef server support is in:

http://github.com/mitchellh/vagrant/commit/9ba0647b6464c567eab93e6f7a9509f668422b69

Documentation will be forthcoming, but the above comment about the Vagrantfile is still accurate.

Mitchell

mitchellh pushed a commit that referenced this issue Jul 17, 2015
Changed minion config path for windows
chrisroberts pushed a commit that referenced this issue Nov 14, 2016
Move dynamic memory settings into conditional block
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants