When using hosted chef with multiple organizations (where organization is the right way to differentiate projects as opposed to setting environments) what is the best approach for managing the client configuration files?

I have separate organizations, each with their own validation key, and generated knife.rb configuration. On my workstations I have separate chef repos and chef client configuration directories for each organization.

But, how do I best manage /etc/chef/*?

I was thinking that I could create separate /etc/chef_ORGANIZATION directories to hold the appropriate configuration and validations, then just symlink /etc/chef to the org I’m working with.

Anyone have other suggestions on how to work with multiple orgs?

I was running chef-client cookbook 1.1.2 on all of our instances (Ubuntu 10, 12). Just downloaded the latest chef-client 1.2 cookbook, modified appropriate attributes, then ran chef-client to upgrade to the new cookbook. Now I have problems with “Error Syncing Cookbooks” and “DEBUG: Re-raising exception: Net::HTTPServerException – 404 "Not Found”"

Any reason why the new cookbook would fail? This is very reproducible – happened on 30 instances already, so I had to revert to the old chef-client cookbook.

Hi,

I have some troubles importing attributes at first run with chef-clietn 11 for windows. I have a json file “c:/chef/first-boot.json” with similar content

{“company”:{“company_name”:“My Company”},“run_list”:[“role[server_role]”]}

I start the client with this line

chef-client -c c:/chef/client.rb -j c:/chef/first-boot.json

I have a role, which is applied correctly and all recipes for that role are started to compile and run. However, if I want to use the “company” attribute at the first run, the attribute is missing (for example node[:company][:company_name] gives me “NoMethodError”, because node[:company] do not exist). If I do not use this attribute (i.e. all recipes pass trough the first run), the attribute node[:company] appears in the chef server and I can use it on the next run.

This method for first run attributes works well on linux chef-client. There I’m able to use the node[:company] attribute on the first run without any problems.

Am I doing something wrong or there is some limitation for chef-client for windows?

Here is my log from the console

chef-client -c c:/chef/client.rb -j c:/chef/first-boot.json -E dev INFO: Chef 11.4.0 INFO: Client key c:/chef/client.pem is not present – registering INFO: Setting the run_list to [“role[server_role]”] from JSON INFO: Run List is [role[server_role]] INFO: Run List expands to [testbook::compnay_set] INFO: Starting Chef Run for node01 INFO: Running start handlers INFO: Start handlers complete. INFO: Loading cookbooks [testbook] Synchronizing Cookbooks: – sag_base – testbook Compiling Cookbooks… ================================================================================ Recipe Compile Error in c:/chef/cache/cookbooks/testbook/recipes/compnay_set.rb ================================================================================ NoMethodError

undefined method `[]‘ for nil:NilClass

Cookbook Trace:

c:/chef/cache/cookbooks/testbook/recipes/install_dbc.rb:8:in `from_file'

Relevant File Content:

c:/chef/cache/cookbooks/testbook/recipes/install_dbc.rb: … 7: 8>> name = node[:company][:company_name] 9: …

ERROR: Running exception handlers FATAL: Saving node information to c:/chef/cache/failed-run-data.json ERROR: Exception handlers complete Chef Client failed. 0 resources updated FATAL: Stacktrace dumped to c:/chef/cache/chef-stacktrace.out FATAL: NoMethodError: undefined method `[]‘ for nil:NilClass

I am receiving an error with my ‘knife bootstrap windows winrm FQDN’ command. It keeps timing out, and I’m not sure what I can do.

 C:\Users\USER>knife bootstrap windows winrm myserver.net
Bootstrapping Chef on myserver.net
Enter your password:
ERROR: Network Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. - connect(2) (http://myserver.net:5985)
Check your knife configuration and network settings