chef

I've been trying to customise a tomcat chef recipe but nothing I'm doing seems to change the tomcat installation. I'm using vagrant ie. vagrant destroy && vagrant up In Vagrantfile config.vm.provision :chef_solo do |chef| chef.add_recipe "apt" chef.add_recipe "nginx-app" chef.add_recipe "tomcat-app" end cookbooks/tomcat-app/recipes/default.rb # # Cookbook Name:: tomcat-app # Recipe:: default package "tomcat7" do action :install end cookbooks/tomcat-app/attributes.rb node.default["tomcat"]["port"] = 8083 <-- can't seem to make this apply Thanks, I suspect you're writing your own tomcat cookbook

I am trying to install chef and knife ec2 plugin on my laptop to set up the workstation. Initially I use chef omnibus to install chef-client but after installing I encountered some problems, so a quick googling landed me to stackoverflow and couple of threads suggested me to install chef using gem. I am running on ruby 2.0.0-p0 and insalled chef and knife ec2 but I am getting a different issue now. I have posted the issue bleow, kindly have a look. Please help me out to fix me this issue /home/jeevan/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/dependency.rb:247:in `to_specs':

I'm using the opscode nginx cookbook for configuring the nginx server on my nodes. The nginx cookbook has some default attributes I'd like to override in my role ("web_server"). These are the attributes I'd like to override: default['nginx']['version'] = "1.2.2" # in cookbooks/nginx/attributes/default.rb default['nginx']['source']['prefix'] = "/opt/nginx-#{node['nginx']['version']}" # in cookbooks/nginx/attributes/source.rb In my roles/web_server.rb file I have something like this: name "web_server" description "Setup a web server" run_list "role[base]", "recipe[nginx]" override_attributes

I'm new to Chef and the documentation (even the home page of their website) makes my head spin. I'm not even sure if I'm using it for the correct purpose. My intent is to setup a Vagrantfile that tells Chef Solo to install some software automatically when I spin up a new box. That is one of Chef Solo's intended uses, am I correct? I'm not really sure if that qualifies as one of "the hardest infrastructure challenges on the planet" , but whatever. My first goal is to get Chef Solo to install nginx for me. In my project, I've cloned the cookbook for nginx : $ git clone https://github.com/opscode

I'd like to put the output of a shell command into a variable for later use in a Chef recipe. In bash I could do something like output=`tail -1 file.txt` and then I could echo $output Can an 'execute resource' do this so that I can use the result later in the recipe? Francois while Graham's solution seemed to work at first, I found out about Chef::Mixin:ShellOut ruby_block "check_curl_command_output" do block do #tricky way to load this Chef::Mixin::ShellOut utilities Chef::Resource::RubyBlock.send(:include, Chef::Mixin::ShellOut) curl_command = 'curl --write-out %{http_code} --silent --output

What is the basic difference between convergence and idempotence in Chef? Convergence and idempotence are not Chef-specific. They're generally attributed to configuration management theory, though have use in other fields, notably mathematics. Let's start with the more basic, idempotent. We're going to ignore the mathematic use of idempotent, and focus instead on what configuration management people mean when they talk about it. That is: "multiple applications of the same action do not have side effects on the system state." A simple example of an idempotent operation is mkdir -p : mkdir -p