flapjack 0.4.12 → 0.5.1

data/bin/flapjack-notifier-manager

@@ -31,9 +31,7 @@ end
 daemon_args = args
 if args.first != "stop"
   # if we're not stopping the daemon, pass options to it
-  daemon_args += ['--', '--beanstalk', options.host, 
-                        '--port', options.port.to_s,
-                        '--recipients', options.recipients,
+  daemon_args += ['--', '--recipients', options.recipients,
                         '--config', File.expand_path(options.config_filename)]
 end
 

data/bin/flapjack-worker

@@ -2,10 +2,8 @@
 
 $: << File.dirname(__FILE__) + '/../lib' unless $:.include?(File.dirname(__FILE__) + '/../lib/')
 
-require 'rubygems'
-require 'log4r'
-require 'log4r/outputter/syslogoutputter'
 require 'flapjack/cli/worker'
+require 'flapjack/applications/worker'
 
 at_exit do 
   puts "Shutting down"
@@ -17,20 +15,8 @@ trap("INT") do
 end
 
 @options = Flapjack::WorkerOptions.parse(ARGV)
-@worker = Flapjack::Worker.new(:host => @options.host, 
-                               :port => @options.port,
-                               :checks_directory => @options.check_directory)
-
-begin
-  @worker.process_loop
-rescue Beanstalk::NotConnected
-  puts "Couldn't connect to the beanstalk!"
- 
-  timeout = 5
-  puts "Retrying in #{timeout} seconds"
-  sleep timeout 
-
-  puts "Retrying..."
-  retry
-end
+app = Flapjack::Worker::Application.run(:host => @options.host,
+                                        :port => @options.port,
+                                        :check_directory => @options.check_directory)
+app.main
 

data/doc/PACKAGING.md

@@ -0,0 +1,25 @@
+Debian / Ubuntu
+===============
+
+Packaged dependencies: 
+
+ * libdaemons-ruby 
+ * liblog4r-ruby
+ * libxmpp4r-ruby
+ * libtmail-ruby 
+
+Unpackaged dependencies: 
+
+ * beanstalkd-client (libbeanstalkd-ruby)
+ * dm-core 
+ * dm-timestamps
+ * dm-types
+ * dm-validations
+ * data_objects
+ * do_sqlite3
+ * do_mysql
+
+The unpackaged dependencies need to be packaged to make Flapjack packagable. 
+
+Current development efforts are working towards abstracting the 
+DataMapper/DataObjects dependency so packaging isn't a complete travesty.

data/etc/flapjack/flapjack-notifier.conf.example

@@ -0,0 +1,34 @@
+# top level
+[notifier]
+  notifier-directories = /usr/lib/flapjack/notifiers/ /path/to/my/notifiers
+  notifiers = mailer, xmpp
+
+# persistence layers
+[persistence]
+  backend = data_mapper
+  uri = sqlite3:///tmp/flapjack.db
+
+# couchdb backend
+#[persistence]
+#  backend = couchdb
+#  version = 0.8
+#  host = localhost
+#  port = 5984 
+#  database = flapjack_production
+  
+# message transports
+[transport]
+  backend = beanstalkd
+  host = localhost
+  port = 11300
+
+# notifiers
+[mailer-notifier]
+  from_address = foo@bar.com
+
+[xmpp-notifier]
+  jid = foo@bar.com
+  password = barfoo
+  
+
+

data/etc/flapjack/recipients.conf.example

@@ -0,0 +1,14 @@
+# example recipients.conf
+
+[John Doe]
+  email = johndoe@example.org
+  jid = john@example.org
+  phone = +61 400 111 222
+  pager = 61400111222
+
+[Jane Doe]
+  email = janedoe@example.org
+  jid = jane@example.org
+  phone = +61 222 333 111
+  pager = 61222333111
+

data/features/flapjack-notifier-manager.feature

@@ -0,0 +1,19 @@
+Feature: flapjack-notifier-manager
+  So people can be notified when things break
+  A notifier must be started
+  Through an easy to use command line tool
+
+  Scenario: Starting the notifier
+    Given the flapjack-notifier-manager is on my path
+    And the "/var/run/flapjack" directory exists and is writable
+    And beanstalkd is running on localhost
+    And there are no instances of flapjack-notifier running
+    When I run "flapjack-notifier-manager start --recipients spec/configs/recipients.ini --config spec/configs/flapjack-notifier.ini" 
+    Then 1 instances of "flapjack-notifier" should be running
+
+  Scenario: Stopping the notifier
+    Given there is an instance of the flapjack-notifier running
+    And beanstalkd is running on localhost
+    When I run "flapjack-notifier-manager stop" 
+    Then 0 instances of "flapjack-notifier" should be running
+

data/features/flapjack-worker-manager.feature

@@ -0,0 +1,25 @@
+Feature: flapjack-notifier-manager
+  To scale Flapjack easily and efficiently
+  A sysadmin
+  Must be able to manage clusters of workers
+
+  Scenario: Running multiple workers
+    Given the flapjack-worker-manager is on my path
+    And beanstalkd is running on localhost
+    And there are no instances of flapjack-worker running
+    When I run "flapjack-worker-manager start" 
+    Then 5 instances of "flapjack-worker" should be running
+
+  Scenario: Running a specified number of workers
+    Given the flapjack-worker-manager is on my path
+    And beanstalkd is running on localhost
+    And there are no instances of flapjack-worker running
+    When I run "flapjack-worker-manager start --workers=10" 
+    Then 10 instances of "flapjack-worker" should be running
+
+  Scenario: Stopping all workers
+    Given there are 5 instances of the flapjack-worker running
+    And beanstalkd is running on localhost
+    When I run "flapjack-worker-manager stop" 
+    Then 0 instances of "flapjack-worker" should be running
+

data/features/packaging-lintian.feature

@@ -0,0 +1,15 @@
+Feature: Packagability 
+  To make Flapjack usable to the masses
+  It must be easily packagable
+
+  Scenario: No rubygems references
+    Given I am at the project root
+    When I run "grep require lib/* bin/* -R |grep rubygems"
+    Then I should see 0 lines of output
+
+  Scenario: A shebang that works everywhere
+    Given I am at the project root
+    When I run "find lib/ -type 'f' -name '*.rb'"
+    Then every file in the output should start with "#!/usr/bin/env ruby"
+
+

data/features/persistence/couch.feature

@@ -0,0 +1,105 @@
+Feature: CouchDB persistence backend
+  To use a CouchDB backend with Flapjack
+  The backend must conform 
+  To the persistence API
+
+  Background:
+    Given I set up the Couch backend with the following options:
+      | host      | port | database      |
+      | localhost | 5984 | flapjack_test | 
+
+  Scenario: Create a check
+    When I create the following checks:
+      | name     | id | command | status | enabled |
+      | passing  | 1  | exit 0  | 0      | true    |
+      | warning  | 2  | exit 1  | 1      | true    |
+      | critical | 3  | exit 2  | 2      | true    |
+    Then looking up the following checks should return documents:
+      | id | 
+      | 1  |
+      | 2  |
+      | 3  |
+
+  Scenario: Update a check
+    Given the following checks exist:
+      | name     | id | command | status | enabled |
+      | passing  | 4  | exit 0  | 0      | true    |
+    When I update the following checks:
+      | name     | id | command | status | enabled |
+      | passing  | 4  | exit 2  | 2      | true    |
+    Then the updates should succeed
+
+  Scenario: Delete a check
+    Given the following checks exist:
+      | name     | id | command | status | enabled |
+      | passing  | 5  | exit 0  | 0      | true    |
+    When I delete the check with id "4"
+    Then the check with id "4" should not exist
+
+  Scenario: List all checks
+    Given the following checks exist:
+      | name     | id | command | status | enabled |
+      | passing  | 6  | exit 0  | 0      | true    |
+      | warning  | 7  | exit 1  | 1      | true    |
+      | critical | 8  | exit 2  | 2      | true    |
+    When I get all checks
+    Then I should have at least 3 checks
+
+  Scenario: Query for failing parents
+    Given the following checks exist:
+      | name           | id | command | status | enabled |
+      | failing parent | 1  | exit 2  | 2      | true    |
+      | passing child  | 2  | exit 0  | 0      | true    |
+    And the following related checks exist: 
+      | id | parent_id | child_id |
+      | 1  | 1         | 2        |
+    Then the following result should not have a failing parent:
+      | check_id | 
+      | 1        |
+    Then the following result should have a failing parent:
+      | check_id |
+      | 2        |
+
+  Scenario: Saving events
+    Given the following checks exist: 
+      | name           | id | command | status | enabled |
+      | failing parent | 4  | exit 2  | 4      | true    |
+    Then the following event should save:
+      | check_id | status |
+      | 4        | 2      |
+    And the check with id "4" on the Sqlite3 backend should have an event created
+
+  Scenario: List events for a check
+    Given the following checks exist: 
+      | name           | id | command | status | enabled |
+      | passing child  | 12 | exit 2  | 3      | true    |
+    Given the following events exist: 
+      | check_id |
+      | 12       |
+      | 12       |
+      | 12       |
+    When I get all events for check "12"
+    Then I should have at least 3 events
+
+  Scenario: List all events
+    Given the following events exist: 
+      | check_id |
+      | 9        |
+      | 10       |
+      | 11       |
+    When I get all events
+    Then I should have at least 3 events
+
+  Scenario: List all check relationships
+    Given the following checks exist: 
+      | name     | id | command | status | enabled |
+      | passing  | 9  | exit 0  | 0      | true    |
+      | warning  | 10 | exit 1  | 1      | true    |
+      | critical | 11 | exit 2  | 2      | true    |
+    And the following related checks exist: 
+      | parent_id | child_id |
+      | 9         | 10       |
+      | 10        | 11       |
+      | 11        | 9        |
+    When I get all check relationships
+    Then I should have at least 3 check relationships

data/features/persistence/sqlite3.feature

@@ -0,0 +1,105 @@
+Feature: SQLite3 persistence backend
+  To use a SQLite3 backend with Flapjack
+  The backend must conform 
+  To the persistence API
+
+  Background:
+    Given I set up the Sqlite3 backend with the following options:
+      | database  | auto_migrate | 
+      | :memory:  | true         |
+
+  Scenario: Create a check
+    When I create the following checks:
+      | name     | id | command | status | enabled |
+      | passing  | 1  | exit 0  | 0      | true    |
+      | warning  | 2  | exit 1  | 1      | true    |
+      | critical | 3  | exit 2  | 2      | true    |
+    Then looking up the following checks should return documents:
+      | id | 
+      | 1  |
+      | 2  |
+      | 3  |
+
+  Scenario: Update a check
+    Given the following checks exist:
+      | name     | id | command | status | enabled |
+      | passing  | 4  | exit 0  | 0      | true    |
+    When I update the following checks:
+      | name     | id | command | status | enabled |
+      | passing  | 4  | exit 2  | 2      | true    |
+    Then the updates should succeed
+
+  Scenario: Delete a check
+    Given the following checks exist:
+      | name     | id | command | status | enabled |
+      | passing  | 5  | exit 0  | 0      | true    |
+    When I delete the check with id "4"
+    Then the check with id "4" should not exist
+
+  Scenario: List all checks
+    Given the following checks exist:
+      | name     | id | command | status | enabled |
+      | passing  | 6  | exit 0  | 0      | true    |
+      | warning  | 7  | exit 1  | 1      | true    |
+      | critical | 8  | exit 2  | 2      | true    |
+    When I get all checks
+    Then I should have at least 3 checks
+
+  Scenario: Query for failing parents
+    Given the following checks exist:
+      | name           | id | command | status | enabled |
+      | failing parent | 1  | exit 2  | 2      | true    |
+      | passing child  | 2  | exit 0  | 0      | true    |
+    And the following related checks exist: 
+      | id | parent_id | child_id |
+      | 1  | 1         | 2        |
+    Then the following result should not have a failing parent:
+      | check_id | 
+      | 1        |
+    Then the following result should have a failing parent:
+      | check_id |
+      | 2        |
+
+  Scenario: Saving events
+    Given the following checks exist: 
+      | name           | id | command | status | enabled |
+      | failing parent | 4  | exit 2  | 4      | true    |
+    Then the following event should save:
+      | check_id | status |
+      | 4        | 2      |
+    And the check with id "4" on the Sqlite3 backend should have an event created
+
+  Scenario: List events for a check
+    Given the following checks exist: 
+      | name           | id | command | status | enabled |
+      | passing child  | 12 | exit 2  | 3      | true    |
+    Given the following events exist: 
+      | check_id |
+      | 12       |
+      | 12       |
+      | 12       |
+    When I get all events for check "12"
+    Then I should have at least 3 events
+
+  Scenario: List all events
+    Given the following events exist: 
+      | check_id |
+      | 9        |
+      | 10       |
+      | 11       |
+    When I get all events
+    Then I should have at least 3 events
+
+  Scenario: List all check relationships
+    Given the following checks exist: 
+      | name     | id | command | status | enabled |
+      | passing  | 9  | exit 0  | 0      | true    |
+      | warning  | 10 | exit 1  | 1      | true    |
+      | critical | 11 | exit 2  | 2      | true    |
+    And the following related checks exist: 
+      | parent_id | child_id |
+      | 9         | 10       |
+      | 10        | 11       |
+      | 11        | 9        |
+    When I get all check relationships
+    Then I should have at least 3 check relationships

data/features/persistence/steps/couch_steps.rb

@@ -0,0 +1,25 @@
+Given /^I set up the Couch backend with the following options:$/ do |table|
+  @backend_options = table.hashes.first.symbolize_keys
+  uri = "/#{@backend_options[:database]}/"
+  request  = ::Net::HTTP::Put.new(uri)
+  response = ::Net::HTTP.start(@backend_options[:host], @backend_options[:port]) {|http| http.request(request)}
+  
+  @backend = Flapjack::Persistence::Couch.new(@backend_options)
+
+  uri = "/#{@backend_options[:database]}/_all_docs"
+  request = ::Net::HTTP::Get.new(uri)
+  response = ::Net::HTTP.start(@backend_options[:host], @backend_options[:port]) {|http| http.request(request)}
+  
+  parser = Yajl::Parser.new
+  doc = parser.parse(response.body)
+  doc["rows"].each do |row|
+    uri = "/#{@backend_options[:database]}/#{row["id"]}?rev=#{row["value"]["rev"]}"
+    request = ::Net::HTTP::Delete.new(uri)
+    response = ::Net::HTTP.start(@backend_options[:host], @backend_options[:port]) {|http| http.request(request)}
+  end
+end
+
+Then /^the check with id "([^\"]*)" on the Couch backend should have a status of "([^\"]*)"$/ do |arg1, arg2|
+  pending # express the regexp above with the code you wish you had
+end
+

data/features/persistence/steps/generic_steps.rb

@@ -0,0 +1,102 @@
+When /^I create the following checks:$/ do |table|
+  table.hashes.each do |attrs|
+    @backend.save_check(attrs.symbolize_keys).should be_true
+  end
+end
+
+Then /^looking up the following checks should return documents:$/ do |table|
+  table.hashes.each do |attrs|
+    @backend.get_check(attrs['id']).should_not be_nil
+  end
+end
+
+When /^I update the following checks:$/ do |table|
+  table.hashes.each do |attrs|
+    @backend.save_check(attrs.symbolize_keys).should be_true
+  end
+end
+
+Then /^the updates should succeed$/ do
+  # matches on "should be_true" above
+end
+
+When /^I delete the check with id "([^\"]*)"$/ do |id|
+  @backend.delete_check(id).should be_true
+end
+
+Then /^the check with id "([^\"]*)" should not exist$/ do |id|
+  @backend.get_check(id).should be_nil
+end
+
+When /^I get all checks$/ do
+  @checks = @backend.all_checks
+end
+
+Then /^I should have at least (\d+) checks$/ do |n|
+  @checks.size.should >= n.to_i
+end
+
+Given /^the following checks exist:$/ do |table|
+  table.hashes.each do |attrs|
+    @backend.save_check(attrs.symbolize_keys)
+  end
+end
+
+Then /^the following results should save:$/ do |table|
+  table.hashes.each do |attrs|
+    @backend.save_check(attrs.symbolize_keys).should be_true
+  end
+end
+
+Given /^the following related checks exist:$/ do |table|
+  table.hashes.each do |attrs|
+    @backend.save_check_relationship(attrs).should be_true
+  end
+end
+
+Then /^the following result should not have a failing parent:$/ do |table|
+  table.hashes.each do |attrs|
+    @backend.any_parents_failed?(attrs['check_id']).should be_false
+  end
+end
+
+Then /^the following result should have a failing parent:$/ do |table|
+  table.hashes.each do |attrs|
+    @backend.any_parents_failed?(attrs['check_id']).should be_true
+  end
+end
+
+Then /^the following event should save:$/ do |table|
+  table.hashes.each do |attrs|
+    result = Flapjack::Transport::Result.new(:result => attrs.symbolize_keys)
+    @backend.create_event(result).should be_true
+  end
+end
+
+
+When /^I get all check relationships$/ do
+  @relationships = @backend.all_check_relationships
+end
+
+Then /^I should have at least (\d+) check relationships$/ do |n|
+  @relationships.size.should >= n.to_i
+end
+
+Given /^the following events exist:$/ do |table|
+  table.hashes.each do |attrs|
+    result = Flapjack::Transport::Result.new(:result => attrs.symbolize_keys)
+    @backend.create_event(result).should be_true
+  end
+end
+
+When /^I get all events$/ do
+  @events = @backend.all_events
+end
+
+Then /^I should have at least (\d+) events$/ do |n|
+  @events.size.should >= n.to_i
+end
+
+When /^I get all events for check "([^\"]*)"$/ do |id|
+  @events = @backend.all_events_for(id) 
+end