In addition to the core Chef tools (chef, knife), there are quite a few third party tools that assist with managing Chef configurations.
Summary:
I'm running into a problem with "knife data bag from file", where knife doesn't recognize the .json data bag file pulled down from a remote git repo.
Background:
I'm currently trying to transition from chef-solo use to chef server while using the cookbooks, data bags and other chef info from our remote git repo.
I've currently pulled down a copy of our git repo and set the cookbook pa
Be gentle, I'm new to chef, trying to get my environment set up and have some new recipes to upload to my new chef server. I'm able to do some commands, and I was able to knife bootstrap the new node, so I'm pretty sure my configuration is correct.
It appears that it's trying to upload to localhost when I turn on verbose logging.
We're using Vagrant & Chef to provision the staging VM for our app.
Once I have a working cookbook, I upload it to chef-server and Jenkins hook ensures the staging env gets updated.
However, it's not clear to me how to try out the cookbook before I upload it.
I am wondering how projects that have multiple component teams manage their sets of cookbooks?
We are trying to figure out how we can have an ops team provide a set of "common component" cookbooks that can be re-used by other teams that will also write their own cookbooks.
This might be a simple question - I am trying to install a cookbook (gitlab)
I cloned the cookbook into a folder on my local drive and ran
knife cookbook upload gitlab.
Immediately it threw an error:
Cookbook gitlab depends on cookbook postgresql version >= 0.0.0
So I ran
knife cookbook site download postgresql
It had some dependencies, which had further dependencies, and now I'm at t
For example, after I run a knife command of 'knife cookbook upload cookbook_name' from a chef workstation or somewhere, where can I find the history or log about who sent the knife command and when, and what the command is? I need to monitor all the knife behaviors on the chef server side centrally.. How to do that?
Thanks!
I'm using Vagrant + Chef (chef_client provisioner) to create & provision a staging environment for my server.
I'm using a bridged network on a vagrant VM with chef-client. knife node show test1-vagrant shows an ip address of 10.0.2.15, which is eth0. eth1 is 192.168.1.5, which is what DHCP gave it. How can i get chef thinking the ip address is 192.168.1.5 instead, so that I can knife ssh -a ipaddress?
Email this page
