chef-repo | My personal chef-repo | Infrastructure Automation library

The error is reported here:

ec2_server_create.rb:1185:in `create_key_pair':

you are also supposed to specify a keypair to ssh into EC2, like that:

The error:

i have a feeling that you are confusing something, since the title of your question mentions chef-solo when you are really using chef-zero (--local-mode).

you should definitely favor chef-zero over chef-solo (but i won't get into the reasons why).

in both cases (using chef-zero or chef-solo), you will have to download all the cookbooks and make verify chef-client knows where are the cookbooks located.

if you ase using chef-zero, here are some references:

Local mode does not require a configuration file, instead it will look for a directory named /cookbooks and will set chef_repo_path to be just above that. (Local mode will honor the settings in a configuration file, if desired.) If the client.rb file is not found and no configuration file is specified, local mode will search for a config.rb file.

client.rb settings:

chef_repo_path: The path to the chef-repo containing cookbooks and other files, such as environments or data bags, when running Chef Infra Client in local mode.

cookbook_path: The sub-directory for Chef Infra Client cookbooks. This value can be a string or an array of file system locations, processed in the specified order. The last cookbook is considered to override local modifications.

since i see that you are using berkshelf, you can use vendor sub-command to download all the cookbooks dependencies and place them in the same directory. then, have a custom configuration for chef-client, that sets the value of cookbook_path to the same directory which you used in conjunction with berks vendor, and finally execute chef-client.

That should be expect(chef_run).to touch_file('C:\inetpub\wwwroot\iisstart.htm'). You only use expect { ... } with raise_error and things like it, most matches use expect(...) as a normal call. Also you had an extra space after touch_file. method (args) is not allowed in Ruby (or at least it is allowed and doesn't do what you think it does).

After realising the the chef-provisoning-vagrant was a ruby gem I was able to check if it was installed. I checked my gem library and it was not present, only aws and fog variants were there.

I ran the command chef gem install chef-provisioning-vagrant which then installed the provisioner and it worked better after that. I guess this provisioner has been removed from the ChefDK since the book I was looking at was written.

On CentOS / RHEL etc (and on Fedora) the package name for Apache is "httpd".

Alternatively, there is a standard cookbook for installing and configuring Apache2:

• https://supermarket.chef.io/cookbooks/apache2

It is fairly sophisticated, and includes recipes for configuring a number of common Apache modules.

The error is not related to cookbook versions, as you can see from the message: NoMethodError: undefined method 'desciption'. You misspelled description.

This is a bug in ChefDK 3.0 when using policy tarball exports. It will be fixed in ChefDK 3.1 next week. In the mean time, add this to your knife.rb config file:

You should not use Chef to host any 'big' files. Setup additional HTTP server or use off site storage like S3.