-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Chef-Provisioning support #31
Comments
This is my conjecture. We already have node objects into nodes/ after the chef-provisioning first run. e.g.
Maybe, we can use knife-zero to them without |
There is one issue: knife-zero bootstraps chef_server_url "chefzero://localhost:8889" while chef-provisioning bootstraps ´client.rb`to chef_server_url "http://localhost:8901" To match the port, I've added the following to my .chef/knife.rb: knife[:remote_chef_zero_port] = 8889 Which made it work. Awesome :-) knife zero chef_client 'name:testnode01' -a cloud_v2.public_ipv4 --sudo -i .chef/keys/google_default -x rmoriz
xxxxxx.82 Starting Chef Client, version 12.3.0
...
xxxxxx.82 Running handlers:
xxxxxx.82 Running handlers complete
xxxxxx.82 Chef Client finished, 0/11 resources updated in 3.149465662 seconds |
Thank you for good report 👍 , I'll try it too. BTW, can I close this issue? |
yes. thanks (maybe put a link into the readme for others?) |
Yes, I'll update README after I confirmed all steps. |
Hi, I tried chef-provisioning with ec2. My recipe is below.
And Chef-Client created client.rb after new machine provisioned.
Then, I added just one line to my
And then, I run (recipe sleep::default is created after provisioning. It means that cookbook was not transferred when machiens were provisioned.)
I wonder what |
interesting. I was using the google provisioning plugin. |
Hi,
I think knife-zero and chef-provisioning could be a great combination:
Chef-Provisioning is cookbook-as-a-gem that provides various resources to spin up nodes in the cloud and converge them using Chef's native cookbook DSL. https://github.com/chef/chef-provisioning
It also can spin up a local chef-zero instance and forward the port to the nodes, which run chef-client -z.
Ideally, one would use chef-provisioning to create a fleet of nodes and use knife-zero to manage them individually in the future.
Afaik, the only issue that prevents this currently, is the different port that knife-zero and chef-provisioning use to forward the local chef-zero service to the nodes (configured in /etc/chef/client.rb while bootstrapping).
Here is a chef-provisioning example (needs chef-provisioning and chef-provisioning-google):
https://gist.github.com/rmoriz/f293ca1402591c5469ae
The downsite of chef-provisioning is, that you can only run the complete recipe, e.g. converge all nodes. This is where knife-zero would be awesome.
The text was updated successfully, but these errors were encountered: