poolparty 1.3.15 → 1.4.0

data/README.rdoc

@@ -19,12 +19,9 @@ For instance, to start a basic cloud, let's write one:
 
   pool "demo" do
     cloud "app" do
-      instances 2..10
-      keypair "cloud_demo"
-      
       using :ec2
-      
-      has_file "/etc/motd", :content => "Hello from your cloud"
+      instances 1
+      keypair "cloud_demo"
     end
   end
   
@@ -73,79 +70,6 @@ Clouds are distinguished by keypairs, so to create multiple clouds, create a new
     end
   end
   
-== Resources
-
-As you probably noticed from above, you provision your system with resources. There are native resources, plugins (which are basically resources) and you can write your own. The base resources included in PoolParty are as follows:
-
-* <tt>file</tt>
-* <tt>directory</tt>
-* <tt>exec</tt>
-* <tt>variable</tt>
-* <tt>service</tt>
-* <tt>package</tt>
-* <tt>user</tt>
-* <tt>group</tt>
-* <tt>link (symlink)</tt>
-* <tt>line (line in file)</tt>
-* <tt>gem_package</tt>
-* <tt>cron</tt>
-
-There are also dependency_resolver specific resources. For instance, **chef** specific resources are as follows:
-
-* <tt>chef_attribute</tt>
-* <tt>http_request</tt>
-* <tt>remote_directory</tt>
-* <tt>remote_file</tt>
-* <tt>route</tt>
-* <tt>script</tt>
-
-To use these resources in your config file (clouds.rb), simply "assert" (call) the method with has_ or does_not_have prepended. For instance:
-
-  pool "demo" do
-    cloud "app" do
-      has_file "/etc/motd", :requires => get_package("apache2")
-      has_package "apache2" do
-        action :install
-      end
-    end
-  end
-  
-As you can see, there are many different ways to call a resource. All the following resource calls are identical:
-
-  has_file "/etc/motd", :content => "Hello world", :owner => "ari"
-  has_file :name => "/etc/motd", :content => "Hello world", :owner => "ari"
-  has_file "/etc/motd" do
-    content "Hello world"
-    owner "ari"
-  end
-  has_file "/etc/motd", :content => "Hello world" do
-    owner "ari"
-  end
-  
-All resources can contain their own resources as well. This sets up a dependency on the parent dependency. For instance
-
-  has_directory "/etc/configs" do
-    has_file "/etc/configs/configger", :content => "Stuff"
-  end
-
-This says that the directory must exist before the file can be created.
-
-You can see the dependency graph setup by your clouds.rb by calling
-
-  cloud compile -g output
-  
-That will generate a output.dot and output.png in the current directory. For this to work, you must have dot installed. Try it!
-
-Resources can be built on top of other resources as well. This is the definition of a resource plugin. This is covered more in-depth on the homepage. For the curious, take a look at lib/poolparty/plugins/apache.rb for an example plugin. 
-
-There are currently several plugins that ship with PoolParty. Those include:
-
-* <tt>apache (this includes passenger, virtual_hosts, php5)</tt>
-* <tt>git</tt>
-* <tt>rails</tt>
-
-This is list likely to expand as plugins are simply resources built on top of other resources. There is an external project called poolparty-extensions (<a href="http://github.com/auser/poolparty-extensions/tree/master">http://github.com/auser/poolparty-extensions/tree/master</a>) that has quite a few external plugins, including hadoop, ganglia and more.
-
 == Extending
 
 To add a cloud_provider, there are four methods that need to be implemented. Simply sublcass the CloudProviders module and require it in your clouds.rb (or commit it back to PoolParty). Those four methods are:
@@ -159,18 +83,9 @@ That's it!
 
 Each resource is documented in the code and more documentation can be found at the site: <a href="http://poolpartyrb.com">http://poolpartyrb.com</a>.
 
-== FEATURES/PROBLEMS:
-
-* Written in Ruby and Erlang (Internal node communication handled by <a href="https://github.com/auser/hermes/tree/master">Hermes</a>)
-* Thrift interface (Connect to your cloud in ANY language supported by <a href="http://incubator.apache.org/thrift/">Thrift</a>)
-* Written from the ground up to be extensible with plugins
-* Easy git-style commands to communicate with your clouds
-* Much much more
-
 == REQUIREMENTS:
 
 * Ruby
-* Erlang
 
 == INSTALL:
 

data/Rakefile

@@ -1,46 +1,86 @@
-require 'config/requirements'
-
-begin
-  require 'hanna/rdoctask'
-rescue LoadError => e
-  require "rake/rdoctask"
-end
-
-require 'config/jeweler' # setup gem configuration
-
-Dir['tasks/**/*.rake'].each { |rake| load rake }
-
-desc "Clean tmp directory"
-task :clean_tmp do |t|
-  FileUtils.rm_rf("#{File.dirname(__FILE__)}/Manifest.txt") if ::File.exists?("#{File.dirname(__FILE__)}/Manifest.txt") 
-  FileUtils.touch("#{File.dirname(__FILE__)}/Manifest.txt")
-  %w(logs tmp).each do |dir|
-    FileUtils.rm_rf("#{File.dirname(__FILE__)}/#{dir}") if ::File.exists?("#{File.dirname(__FILE__)}/#{dir}")
-  end
-end
-
-desc "Remove the pkg directory"
-task :clean_pkg do |t|
-  %w(pkg).each do |dir|
-    FileUtils.rm_rf("#{File.dirname(__FILE__)}/#{dir}") if ::File.exists?("#{File.dirname(__FILE__)}/#{dir}")
-  end
-end
-
-
-namespace :gem do
-  task(:build).prerequisites.unshift :gemspec # Prepend the gemspec generation
-  
-  desc "Build the gem only if the tests pass"
-  task :test_then_build => [:test, :build]
-  
-  desc "Build and install the gem only if the tests pass"
-  task :test_then_install => [:test, :install]
-end
-
-# Generate documentation
-Rake::RDocTask.new do |rd|
-  rd.main = "README.rdoc"
-  rd.rdoc_files.include("README.rdoc", "lib/**/*.rb")
-  rd.rdoc_dir = "rdoc"
-  # rd.template = "hanaa"
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+
+require 'config/requirements'
+
+begin
+  require 'hanna/rdoctask'
+rescue LoadError => e
+  require "rake/rdoctask"
+end
+
+require 'config/jeweler' # setup gem configuration
+
+task :default  => [:test, :cleanup_test]
+desc "Update vendor directory and run tests"
+task :ci => ["poolparty:vendor:setup", "poolparty:vendor:update", :spec, :test]
+ 
+task :cleanup_test do
+  ::FileUtils.rm_rf "/tmp/poolparty"
+end
+ 
+# task :test do
+#   sh "ruby -Ilib:test #{Dir["#{File.dirname(__FILE__)}/../test/poolparty/*/*.rb"].join(" ")}"
+# end
+ 
+Rake::TestTask.new(:test) do |t|
+  t.test_files = FileList['test/lib/**/*_test.rb']
+  t.warning = false
+  t.verbose = false
+end
+ 
+begin
+  require 'rcov/rcovtask'
+ 
+  Rcov::RcovTask.new(:rcov) do |t|
+    t.libs << FileList['lib/**/*.rb']
+    t.rcov_opts = [
+      '-xRakefile', '-xrakefile',
+      '-xlib/erlang',
+      '--text-report',
+      '--sort coverage'
+    ] + FileList['tasks/*.rake'].pathmap("-x%p")
+    t.test_files = FileList['test/lib/**/*_test.rb']
+    t.output_dir = 'coverage'
+    t.verbose = true
+  end
+rescue LoadError
+  puts "RCov is not available"
+end
+
+
+desc "Clean tmp directory"
+task :clean_tmp do |t|
+  FileUtils.rm_rf("#{File.dirname(__FILE__)}/Manifest.txt") if ::File.exists?("#{File.dirname(__FILE__)}/Manifest.txt") 
+  FileUtils.touch("#{File.dirname(__FILE__)}/Manifest.txt")
+  %w(logs tmp).each do |dir|
+    FileUtils.rm_rf("#{File.dirname(__FILE__)}/#{dir}") if ::File.exists?("#{File.dirname(__FILE__)}/#{dir}")
+  end
+end
+
+desc "Remove the pkg directory"
+task :clean_pkg do |t|
+  %w(pkg).each do |dir|
+    FileUtils.rm_rf("#{File.dirname(__FILE__)}/#{dir}") if ::File.exists?("#{File.dirname(__FILE__)}/#{dir}")
+  end
+end
+
+
+namespace :gem do
+  task(:build).prerequisites.unshift :gemspec # Prepend the gemspec generation
+  
+  desc "Build the gem only if the tests pass"
+  task :test_then_build => [:test, :build]
+  
+  desc "Build and install the gem only if the tests pass"
+  task :test_then_install => [:test, :install]
+end
+
+# Generate documentation
+Rake::RDocTask.new do |rd|
+  rd.main = "README.rdoc"
+  rd.rdoc_files.include("README.rdoc", "lib/**/*.rb")
+  rd.rdoc_dir = "rdoc"
+  # rd.template = "hanaa"
 end

data/VERSION.yml

@@ -1,4 +1,4 @@
 --- 
-:minor: 3
-:patch: 15
 :major: 1
+:minor: 4
+:patch: 0

data/bin/cloud

@@ -1,12 +1,10 @@
 #!/usr/bin/env ruby
 $:.unshift(File.dirname(__FILE__) + "/../lib")
 require "poolparty"
-require "colors"
-require "mixins/printing"
 require 'git-style-binary/command'
 
 GitStyleBinary.primary do
-  self.class.send :include, Printing
+  # self.class.send :include, Printing
   
   @theme = :short
   
@@ -28,17 +26,15 @@ EOS
 
   before_run do |command|
     # Setup testing/debugging
-    $TESTING        = true if command[:verbose]
+    $PP_VERBOSE     = true if command[:verbose]
     $VERY_VERBOSE   = true if command[:very_verbose]
     $DEBUGGING      = true if command[:debug]
     $VERY_DEBUGGING = true if command[:very_debug]
     
-    @loaded_pool = PoolParty::Pool.find_and_load_default_clouds_dot_rb(command[:clouds_dot_rb])
-    @loaded_clouds = command[:name] ? [clouds[command[:name]]] : @loaded_pool.clouds.map {|name,cld|cld}
-    @loaded_clouds.map do |cld| 
-      cld.verbose = command[:verbose]
-      cld.debug = command[:debug]
-    end
+    require command[:clouds_dot_rb]
+    
+    @loaded_pool = pool
+    @loaded_clouds = command[:name] ? [pool.clouds[command[:name]]] : pool.clouds.map {|name,cld|cld}    
   end
   
   run do |command|

data/bin/cloud-bootstrap

@@ -20,10 +20,8 @@ EOS
     
     @loaded_clouds.each do |cld|
       
-      cld.nodes.each do |node|
-        node.cloud = cld # needed for bootstrap
-        node.bootstrap!(:force=>command[:force])
-      end
+      cld.compile!
+      cld.bootstrap!
       
     end
     

data/bin/cloud-compile

@@ -14,19 +14,13 @@ EOS
   short_desc "Configure a cloud instance"
   
   opt :inst_num, "The number of the instance to run bootstrap on", :type => :int
-  opt :generate_graph, "Generate the dependency tree graph", :type => :string, :default => nil
 
   run do |command|
     
     @loaded_clouds.each do |cld|
       ENV["POOLPARTY_NO_VALIDATION"] = "true"
       
-      cld.compile
-      
-      if command[:generate_graph]
-        vputs "Generating dependency graph at: #{command[:generate_graph]}"
-        cld.output_resources_graph('png', command[:generate_graph], {"fontsize" => 30})
-      end
+      cld.compile!
       
     end
     

data/bin/cloud-configure

@@ -20,15 +20,7 @@ EOS
     
     @loaded_clouds.each do |cld|
       
-      if command[:generate_graph]
-        vputs "Generating dependency graph at: #{command[:generate_graph]}"
-        cld.output_resources_graph('png', command[:generate_graph], {"fontsize" => 30})
-      end
-      
-      cld.nodes.each do |node|
-        node.cloud = cld # ?
-        node.configure!(:cloud => cld)
-      end
+      cld.configure!
       
     end
     

data/bin/cloud-console

@@ -1,7 +1,6 @@
 #!/usr/bin/env ruby
 $:.unshift(File.dirname(__FILE__) + "/../lib")
 require "poolparty"
-
 require 'git-style-binary/command'
 
 GitStyleBinary.command do
@@ -24,11 +23,9 @@ EOS
     # libs << " -r #{File.dirname(__FILE__) + '/../lib/console_lib/console_logger.rb'}"
     libs <<  " -r #{File.dirname(__FILE__) + '/../lib/poolparty.rb'}"
     f = command[:clouds_dot_rb]
-    libs <<  " -r " + if File.file?(f)
-      f
-    else
-      "#{PoolParty::Pool.find_default_clouds_dot_rb('clouds.rb')}"
-    end
+    File.open("/tmp/console.rb", "w") {|f| f << "require '#{command[:clouds_dot_rb]}'\npool.auto_execute = false" }
+    libs <<  " -r /tmp/console.rb"
+    
     puts "Loading PoolParty console..."
     exec "#{irb} #{libs} --simple-prompt"
     

data/bin/cloud-contract

@@ -17,22 +17,18 @@ EOS
     @loaded_clouds.each do |cld|
       
       node_to_terminate = cld.nodes.last
-      node_to_terminate.cloud = cld
+      # node_to_terminate.cloud = cld
       
       msg = [
         "Contracting cloud #{cld.name} (#{cld.keypair}) by 1",
         " node: #{node_to_terminate.public_ip}"
       ]
       
-      print_msg(msg)
+      puts msg.join("\n")
       
       node_to_terminate.terminate!
       
-      msg = [
-        "#{node_to_terminate.public_ip} has been terminated"
-      ]
-      
-      print_msg(msg)
+      puts "#{node_to_terminate.public_ip} has been terminated"
     end    
   end
 end

data/bin/cloud-list

@@ -26,7 +26,8 @@ EOS
         msg = ["Listing cloud #{cld.name}"]
 
         hsh = {}
-        cld.describe_instances(:keypair_name => cld.keypair.basename).each do |n| 
+        
+        cld.all_nodes.each do |n| 
           (hsh[n.status] ||= []) << n
         end
         
@@ -34,12 +35,12 @@ EOS
           msg << "#{k.capitalize} nodes"
           msg << line
           v.each do |a|
-            msg << "  #{a[:instance_id] || a[:id]}\t#{a[:ip] || a[:public_ip] || a[:name]}"
+            msg << "  #{a.instance_id}\t#{a.status}\t#{a.public_ip}\t#{a.dns_name}"
           end
           msg << ""
         end
         
-        print_msg(msg)
+        puts msg
       end
       
     end

data/bin/cloud-reboot

@@ -0,0 +1,25 @@
+#!/usr/bin/env ruby
+$:.unshift(File.dirname(__FILE__) + "/../lib")
+require "poolparty"
+
+require 'git-style-binary/command'
+
+GitStyleBinary.command do
+  banner <<-EOS
+Usage: #{$0} #{all_options_string}
+
+  Cycle through nodes in the cloud and wait for the autoscaler to reboot 
+EOS
+  
+  opt :configure, "Configure the cloud before rebooting", :type => :bool, :default => false
+  short_desc "Cycle the instances"
+
+  run do |command|
+    
+    @loaded_clouds.each do |cld|
+      cld.run if command[:configure]
+      cld.reboot!
+    end
+    
+  end
+end

data/bin/cloud-show

@@ -24,13 +24,21 @@ EOS
       msg = [
         "Cloud: #{cld.name}",
         "----------------------------",
-        "Instances: #{cld.nodes(:status => "running").size}",
-        "Minimum instances: #{cld.minimum_instances}",
-        "Maximum instances: #{cld.maximum_instances}",
-        "Running on: #{cld.cloud_provider_name}"
+        "Running Instances:   #{cld.nodes.size}",
+        "Minimum instances:   #{cld.minimum_instances}",
+        "Maximum instances:   #{cld.maximum_instances}",
+        "Running on:          #{cld.cloud_provider.name}",
+        "Keypair:             #{cld.keypair.basename}",
+        "Security group:      #{cld.cloud_provider.security_group_names}",
+        "Availability zones:  #{cld.cloud_provider.availability_zones}"
       ]
       
-      print_msg(msg)
+      if cld.load_balancers.size > 0
+        load_balancers = cld.cloud_provider.load_balancers.first.running_load_balancers.map {|a| a[:dns_name]}
+        msg << "Load balancers:      #{load_balancers.join("\n\t\t\t")}"
+      end
+            
+      puts msg.flatten
       
     end
     

data/bin/cloud-start

@@ -17,32 +17,7 @@ EOS
     
     @loaded_clouds.each do |cld|
 
-      if cld.nodes.size.zero?
-        puts "Starting cloud #{cld.name} (#{cld.keypair})"
-        puts "#{cld.nodes(:status => "running").size} running instances (#{cld.minimum_instances} - #{cld.maximum_instances})"
-        
-        cld.minimum_instances.times do |i|
-          cld.expand
-        end
-        # cld.nodes.each do |node|
-        #   vputs "Bootstrapping: #{node.instance_id}"
-        #   node.bootstrap!
-        #   node.configure!(:cloud => cld)
-        # end
-        
-        msg = [
-          "Your cloud has started with the following public_ips:"
-        ]
-        
-        cld.nodes.each {|node| msg << "#{node.public_ip}"}
-        
-        print_msg(msg)
-      else
-        puts <<-EOE
-          #{cld.nodes}
-          Your cloud is already running.
-        EOE
-      end
+      cld.run
       
     end
     

data/bin/cloud-terminate

@@ -22,10 +22,10 @@ EOS
       "Are you sure? (Y/N)"
       ]
       
-      o = command[:yes] || are_you_sure?(msg)
+      o = command[:yes] || true
       if o
-        vputs "Shutting down cloud"
-        cld.terminate!
+        puts "Shutting down cloud"
+        cld.teardown
       else
         
       end

data/examples/README.md

@@ -0,0 +1,57 @@
+
+simple.rb
+===
+The simple.rb configuration will create an ec2 auto scaling group that will launch the minimum_instances (1 in this case,) inside a security group. The default naming of most objects, such as security_groups, auto scaling groups, launch_configurations and load_balancers and keypairs follow the poolname-cloudname convention.  For example, the cloud below will create a security-group named 'pooolparty-simple'.  The names can be overridden, important if you want more than one.   If a keypair does not exist, it will be created.
+
+Since auto scaling is specified in this cloud, poolparty will not start the instance directly.  Instead, poolparty will create an ec2_launch_configuration and auto scaling group. 
+
+Some important notes:  Some of the methods used inside the cloud block are specific to the cloud provider being used, ec2 in this example.  The cloud_provider methods are added when the cloud_provider is specified, therefore you must be sure to specify the cloud_provider before any cloud_provider specific methods.
+
+User_data.  While not a specific feature of poolparty, we often use user_data scripts to configure instance in the cloud.  This allows for separation of concerns:
+  - PoolParty takes care of setting up an infrastructure of firewalled autoscaling, load balanced instances across multiple data centers.
+  - Userdata scripts configure the instances, optionally pulling in from a repository of additional tasks.    Userdata script can be used in conjunction with [runrul](http://alestic.com/2009/08/runurl) to run scripts form a shared repository, even installing and run chef if desired.
+  
+A benefit of userdata scripted instance configuration is that it does not require active management and monitoring. You just define your infrastructure with poolparty and let the autoscaling take care of the rest.
+
+chef_cloud.rb
+===
+The chef_cloud.rb does not define an autoscaling group.  Since there is no autoscaling group, poolparty will launch the instances (ec2_run_instance.) and wait for ssh to be available on all the launched hosts.
+Next, if a chef-repo was specified:
+  
+  1.  The repo will be uploaded the /etc/chef on the instances.
+  2.  Ssh to the instances and call chef -c /etc/chef/solo.rb -j /etc/chef/dna.json
+
+The dna.json can be populated either by simply editing the file dna.json in your chef-repo, or you can specify chef_attributes in your cloud block.  for example:
+
+    chef_attributes :apache2 => {:listen_ports => ["80", "8080"]} "8080"]}
+    
+If you specify chef_attributes they will be compiled into a a role namded for the cloud at /etc/chef/roles/cloudname.json, and a dna.json file that will execute the clouds role on the instance.
+
+Notes, Tips and Comments:
+===
+The goal of having an completely idempotent declarative configuration system is particularly valuable when you need to manage and update running servers. In the cloud we have found that often, it is easier to simply throw away the server and start a new one from a fresh state.
+
+  1. Update userdata scripts and launch configs
+  2. Terminate the instances (1 at a time for a rolling restart, or all at once)
+  3. Let the autoscaling (or client side poolparty) start new instances with the new userdata
+
+Since the instances are always starting from a known state (a base ami) the configuration scripts can be much simpler, simple shell scripts, possibly executed as runurls.
+
+If runurls are being called from the userdata script, another way to update the cloud instances configuration is to update the runurl (if you are hosting it, which is recommended) you can terminate instances and the newly launched instances will use the updated runurl/
+
+We try and keep private data out of the runurl scripts, opting to supply this data either as environment variables (possibly set by the userdata script,) as command line arguments to runrul (i.e. $1, $2 etc), or variables contained in a separate file our userdata script can download. 
+
+When the runurl cannot be public, and we do not want to embed all the runurl scripts in the userdata, we have used an authenticate only aws user.  That is create an aws user, but do not provide a credit card or sign up for any services. Even tho the user can not create any resources, it can authenticate.  We put the authenticate only user credentials in the userdata file, and  a small bit of code at the top of our userdata file to fetch and install an s3 utility, such as s3cmd. Then the s3cmd can download private readonly s3 urls.
+
+chef
+---
+If you want to use chef, one way to do so is to put code like the following in your userdata
+
+    # OPTIONAL: install chef-solo
+    export CLOUD=${1:-'poolparty'}
+    sudo gem install ohai chef --source http://gems.opscode.com --no-rdoc --no-ri
+    mkdir -p /etc/chef/cookpooks
+    s3sync -r https://mybucket.s3.amazonaws.com/chef-repo /etc/chef/chef
+    s3sync https://cloudteam.s3.amazonaws.com/chef-repo/$CLOUD.json /etc/chef/dna.json
+    chef-solo -c /etc/chef/chef/solo.rb -j /etc/chef/chef/dna.json
+

data/examples/chef_cloud/chef-repo/README

@@ -0,0 +1,3 @@
+Began as a clone of the Opscode base repo
+http://wiki.opscode.com/display/chef/Chef+Repository
+

data/examples/chef_cloud/chef-repo/Rakefile

@@ -0,0 +1,35 @@
+#
+# Rakefile for Chef Server Repository
+#
+# Author:: Adam Jacob (<adam@opscode.com>)
+# Copyright:: Copyright (c) 2008 Opscode, Inc.
+# License:: Apache License, Version 2.0
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+# 
+#     http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+require 'rubygems'
+require 'chef'
+require 'json'
+
+# Make sure you have loaded constants first
+require File.join(File.dirname(__FILE__), 'config', 'rake')
+
+# And choosen a VCS
+if File.directory?(File.join(TOPDIR, ".svn"))
+  $vcs = :svn
+elsif File.directory?(File.join(TOPDIR, ".git"))
+  $vcs = :git
+end
+
+load 'chef/tasks/chef_repo.rake'

data/examples/chef_cloud/chef-repo/certificates/README

@@ -0,0 +1 @@
+This directory contains certificates created by the Rakefile.

data/examples/chef_cloud/chef-repo/config/client.rb.example

@@ -0,0 +1,22 @@
+#
+# Example Chef Client Config File
+#
+# We recommend using Opscode's chef cookbook for managing chef itself,
+# instead of using this file. It is provided as an example.
+
+log_level          :info
+log_location       STDOUT
+ssl_verify_mode    :verify_none
+registration_url   "https://chef.localdomain"
+openid_url         "https://chef.localdomain"
+template_url       "https://chef.localdomain"
+remotefile_url     "https://chef.localdomain"
+search_url         "https://chef.localdomain"
+role_url           "https://chef.localdomain"
+
+file_store_path    "/srv/chef/file_store"
+file_cache_path    "/srv/chef/cache"
+
+pid_file           "/var/run/chef/chef-client.pid"
+
+Chef::Log::Formatter.show_time = true