flapjack 0.5.5 → 0.6.23

data/TODO.md

@@ -1,36 +0,0 @@
- * refactor couchdb backend to be less bongtastic
- * write "action" hooks API on notifications
-
- * write migration tool for sqlite3 => couchdb
-
- * write persistence backend setup tool (create couchdb/sqlite3 database)
-
- * add lintian-like checks for verifying packagability (see http://pkg-ruby-extras.alioth.debian.org/upstream-devs.html)
- * sandbox flapjack-worker
- * write beanstalkd.yreserve to simplify code
- * write beanstalkd.jput, beanstalkd.jreserve for native json api
-
- * build config file/cli options proxy
- * build easily runnable benchmarks for flapjack-{worker,notifier}
-
- * update installation guide
- * clean up persistence API to be more user friendly
-
- * write puppet manifests
- * provide common interface for loading checks into beanstalk (extract from populator)
- 
- * write zeroconf/avahi notifier
- * write growl notifier
- * write sms notifier
- * allow customisation of notifier messages (body, header)
-
- * http://www.kitchensoap.com/2009/10/05/meanwhile-more-meta-metrics/
-
- * add support to worker and notifier for multiple beanstalkds
- * patch beanstalk-client to recognise DRAINING status 
-
- * write check generator
-   * include a collection of common functions 
-     (logging to rrd, retreiving values, executing check)
-
-

data/VERSION

@@ -1 +0,0 @@
-0.5.5

data/bin/flapjack-benchmark

@@ -1,50 +0,0 @@
-#!/usr/bin/env ruby
-
-$: << File.dirname(__FILE__) + '/../lib' unless $:.include?(File.dirname(__FILE__) + '/../lib/')
-
-require 'flapjack/cli/notifier'
-require 'flapjack/applications/notifier'
-require 'daemons'
-require 'flapjack/patches'
-
-# setup 
-@options = Flapjack::Notifier::Options.parse(ARGV)
-
-log = Log4r::Logger.new("notifier")
-log.add(Log4r::SyslogOutputter.new("notifier"))
-
-app = Flapjack::Notifier::Application.run(:log => log, 
-                                          :notifiers => {},
-                                          :filters => [],
-                                          :queue_backend => {:type => :beanstalkd},
-                                          :persistence => {:type => :data_mapper,
-                                                           :uri => "sqlite3:///tmp/flapjack.db"})
-
-mockapp = Flapjack::Notifier::Application.run(:log => log,
-                                              :notifiers => {},
-                                              :queue_backend => {:type => :mockbackend,
-                                                                 :basedir => File.join(File.dirname(__FILE__), '..', 'spec', 'transports')},
-                                              :persistence => {:type => :mockbackend,
-                                                               :basedir => File.join(File.dirname(__FILE__), '..', 'spec', 'persistence')})
-
-# populate 
-require 'beanstalk-client'
-beanstalk = Beanstalk::Pool.new(["localhost:11300"], 'results')
-
-puts "Writing 1000 passing checks onto work queue."
-2000.times do 
-  result = {:output => "some output", :check_id => 1, :retval => 0}
-  beanstalk.yput(result)
-end
-
-# benchmark
-require 'benchmark' 
-
-Benchmark.bm(30) do |b|
-  b.report("beanstalkd + datamapper:") do
-    1000.times {app.process_result}
-  end
-  b.report("mock + mock:") do
-    1000.times {mockapp.process_result}
-  end
-end

data/bin/flapjack-notifier

@@ -1,21 +0,0 @@
-#!/usr/bin/env ruby
-
-$: << File.dirname(__FILE__) + '/../lib' unless $:.include?(File.dirname(__FILE__) + '/../lib/')
-
-require 'flapjack/cli/notifier'
-require 'flapjack/applications/notifier'
-require 'daemons'
-require 'flapjack/patches'
-
-@options = Flapjack::Notifier::Options.parse(ARGV)
-
-log = Log4r::Logger.new("notifier")
-log.add(Log4r::StdoutOutputter.new("notifier"))
-log.add(Log4r::SyslogOutputter.new("notifier"))
-
-app = Flapjack::Notifier::Application.run(:log => log, 
-                                          :notifiers => @options.notifiers,
-                                          :transport => @options.transport,
-                                          :persistence => @options.persistence)
-app.main()
-

data/bin/flapjack-notifier-manager

@@ -1,43 +0,0 @@
-#!/usr/bin/env ruby
-
-$: << File.dirname(__FILE__) + '/../lib' unless $:.include?(File.dirname(__FILE__) + '/../lib/')
-
-require 'rubygems'
-require 'daemons'
-require 'fileutils'
-require 'flapjack/cli/notifier_manager'
-require 'flapjack/patches' # for Daemons
-
-# reassign ARGV so we don't mess with it directly
-args = ARGV
-args << '--help' if args.size == 0
-options = Flapjack::NotifierManagerOptions.parse(args)
-
-worker_path = File.join(File.dirname(__FILE__), 'flapjack-notifier')
-
-# set up pid dir
-pid_dir = "/var/run/flapjack/"
-unless File.exists?(pid_dir)
-  puts "#{pid_dir} doesn't exist."
-  exit 2
-end
-
-unless File.writable?(pid_dir)
-  puts "Can't write to #{pid_dir} - check permissions?"
-  exit 2
-end
-
-# construct arguments
-daemon_args = args
-if args.first != "stop"
-  # if we're not stopping the daemon, pass options to it
-  daemon_args += ['--', '--recipients', options.recipients,
-                        '--config', File.expand_path(options.config_filename)]
-end
-
-# boot
-Daemons.run(worker_path, :ARGV => daemon_args,
-                         :multiple => false, 
-                         :dir_mode => :normal,
-                         :dir => pid_dir)
-

data/bin/flapjack-stats

@@ -1,27 +0,0 @@
-#!/usr/bin/env ruby
-
-require 'rubygems'
-require 'beanstalk-client'
-
-begin
-  beanstalk = Beanstalk::Pool.new(['localhost:11300'])
-  loop do
-    time = Time.now
-    beanstalk.list_tubes['localhost:11300'].each do |tube_name|
-      next if tube_name == 'default'
-      stats   = beanstalk.stats_tube(tube_name)
-      message = []
-      message << "#{time} [#{tube_name}]"
-      message << "total: #{stats['total-jobs']}"
-      message << "waiting: #{stats['current-waiting']}"
-      message << "ready: #{stats['current-jobs-ready']}"
-      puts message.join(', ')
-    end
-    sleep 1
-  end
-rescue Beanstalk::NotConnected
-  puts "beanstalk isn't up!"
-  exit 2
-end
-
-

data/bin/flapjack-worker

@@ -1,13 +0,0 @@
-#!/usr/bin/env ruby
-
-$: << File.expand_path(File.join(File.dirname(__FILE__), '..', 'lib'))
-
-require 'flapjack/cli/worker'
-require 'flapjack/applications/worker'
-
-@options = Flapjack::WorkerOptions.parse(ARGV)
-app = Flapjack::Worker::Application.run(:host => @options.host,
-                                        :port => @options.port,
-                                        :check_directory => @options.check_directory)
-app.main
-

data/bin/flapjack-worker-manager

@@ -1,35 +0,0 @@
-#!/usr/bin/env ruby
-
-$: << File.dirname(__FILE__) + '/../lib' unless $:.include?(File.dirname(__FILE__) + '/../lib/')
-
-require 'rubygems'
-require 'daemons'
-require 'fileutils'
-require 'flapjack/cli/worker_manager'
-require 'flapjack/patches' # for Daemons
-
-# reassign ARGV so we don't mess with it directly
-args = ARGV
-args << '--help' if args.size == 0
-options = WorkerManagerOptions.parse(args)
-
-worker_path = File.join(File.dirname(__FILE__), 'flapjack-worker')
-
-# set up pid dir
-pid_dir = "/var/run/flapjack"
-FileUtils.mkdir_p(pid_dir)
-
-# spin up a number of workers (5 is the default).
-options.workers.times do |n|
-  # we fork for each worker, as Daemons.run backgrounds this script.
-  fork do
-    Daemons.run(worker_path, 
-                :ARGV => (args + %w(-- -b localhost)), 
-                :multiple => true, 
-                :dir_mode => :normal,
-                :dir => pid_dir)
-  end
-  # so we don't try and stop the daemon multiple times
-  break if ARGV[0] == "stop"
-end
-

data/dist/etc/init.d/flapjack-notifier

@@ -1,47 +0,0 @@
-#!/bin/bash
-#
-# Copyright (c) 2009-2011 Lindsay Holmwood <lindsay@holmwood.id.au>
-#
-# flapjack-notifier
-# Boots flapjack-notifier, notifier for Flapjack.
-#
-
-PATH=$PATH:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local:/usr/local/sbin:/usr/local/bin:/usr/lib/flapjack/bin
-
-if [ -f /etc/default/flapjack-notifier ]; then
-  . /etc/default/flapjack-notifier
-fi
-
-# Default return value
-RETVAL=0
-
-if [ ! $(which flapjack-notifier-manager) ]; then
-  echo "Error: flapjack-notifier-manager isn't on your path."
-  echo "Refusing to start!"
-  exit 1
-fi
-
-# Evaluate command
-case "$1" in
-    start)
-      flapjack-notifier-manager start --recipients $RECIPIENTS \
-          --port $BEANSTALKD_PORT --beanstalk $BEANSTALKD_ADDR
-      RETVAL=$?
-  ;;
-    stop)
-      flapjack-notifier-manager stop --recipients $RECIPIENTS \
-         --port $BEANSTALKD_PORT --beanstalk $BEANSTALKD_ADDR
-      RETVAL=$?
-  ;;
-    restart)
-      flapjack-notifier-manager restart --recipients $RECIPIENTS \
-            --port $BEANSTALKD_PORT --beanstalk $BEANSTALKD_ADDR
-      RETVAL=$?
-  ;;
-    *)
-      echo "Usage: flapjack-notifier {start|stop|restart}"
-      RETVAL=1
-  ;;
-esac
-
-exit $RETVAL

data/dist/etc/init.d/flapjack-workers

@@ -1,44 +0,0 @@
-#!/bin/bash
-#
-# Copyright (c) 2009-2011 Lindsay Holmwood <lindsay@holmwood.id.au>
-#
-# flapjack-workers
-# Boots flapjack-workers, check executors for Flapjack.
-#
-
-PATH=$PATH:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local:/usr/local/sbin:/usr/local/bin:/usr/lib/flapjack/bin
-
-if [ -f /etc/default/flapjack-workers ]; then
-  . /etc/default/flapjack-workers
-fi
-
-# Default return value
-RETVAL=0
-
-if [ ! $(which flapjack-worker-manager) ]; then
-  echo "flapjack-worker-manager isn't on your path."
-  echo "Refusing to start."
-  exit 1
-fi
-
-# Evaluate command
-case "$1" in
-    start)
-      flapjack-worker-manager start --workers $WORKERS --checks-directory $CHECKS_DIRECTORY
-      RETVAL=$?
-  ;;
-    stop)
-      flapjack-worker-manager stop
-      RETVAL=$?
-  ;;
-    restart)
-      flapjack-worker-manager restart --workers $WORKERS
-      RETVAL=$?
-  ;;
-    *)
-      echo "Usage: flapjack-workers {start|stop|restart}"
-      RETVAL=1
-  ;;
-esac
-
-exit $RETVAL

data/features/flapjack-notifier-manager.feature

@@ -1,19 +0,0 @@
-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

@@ -1,27 +0,0 @@
-Feature: flapjack-worker-manager
-  To scale Flapjack easily and efficiently
-  A sysadmin
-  Must be able to manage clusters of workers
-  With ease
-  From the command line
-
-  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/flapjack-worker.feature

@@ -1,27 +0,0 @@
-Feature: flapjack-worker
-  To be alerted to problems
-  A user
-  Needs checks executed
-  On a regular schedule
-  And the results of those checks
-  Need to be reported
-
-  Scenario: Start a worker
-    Given beanstalkd is running
-    When I background run "flapjack-worker"
-    Then I should see "flapjack-worker" running
-    Then I should see "Waiting for check" in the "flapjack-worker" output
-
-  Scenario: Start a worker without beanstalk running
-    Given beanstalkd is not running
-    When I background run "flapjack-worker"
-    Then I should see "flapjack-worker" running
-    Then I should not see "Shutting down" in the "flapjack-worker" output
-
-  Scenario: Beanstalk disappears while worker running
-    Given beanstalkd is running
-    When I background run "flapjack-worker"
-    And beanstalkd is killed
-    Then I should see "flapjack-worker" running
-    Then I should not see "Shutting down" in the "flapjack-worker" output
-    Then I should see "went away" in the "flapjack-worker" output

data/features/netsaint-config-converter.feature

@@ -1,126 +0,0 @@
-Feature: Netsaint -> Flapjack configuration converter
-  To assist the migration to Flapjack
-  An operator needs to migrate
-  A functioning netsaint or nagios configuration
-  Into Flapjack's native configuration system
-
-  @parse
-  Scenario: Parse + print netsaint services
-    Given NetSaint configuration is at "features/support/data/etc/netsaint"
-    When I run "flapjack-netsaint-parser" with the following arguments:
-      | argument                                    |
-      | print                                       |
-      | services                                    |
-      | --source=features/support/data/etc/netsaint |
-    Then I should see a valid JSON output
-    And I should see a list of services
-    And I should see the following attributes for every service:
-      | attribute     |
-      | check_command |
-      | description   |
-
-  @parse
-  Scenario: Parse + print netsaint timeperiods
-    Given NetSaint configuration is at "features/support/data/etc/netsaint"
-    When I run "flapjack-netsaint-parser" with the following arguments:
-      | argument                                    |
-      | print                                       |
-      | timeperiods                                 |
-      | --source=features/support/data/etc/netsaint |
-    Then I should see a valid JSON output
-    And I should see a list of timeperiods
-    And I should see the following attributes for every timeperiod:
-      | attribute        | nillable? |
-      | timeperiod_alias | true      |
-
-  @parse
-  Scenario: Parse + print netsaint contacts
-    Given NetSaint configuration is at "features/support/data/etc/netsaint"
-    When I run "flapjack-netsaint-parser" with the following arguments:
-      | argument                                    |
-      | print                                       |
-      | contacts                                    |
-      | --source=features/support/data/etc/netsaint |
-    Then I should see a valid JSON output
-    And I should see a list of contacts
-    And I should see the following attributes for every contact:
-      | attribute                |
-      | contact_alias            |
-      | email_address            |
-      | host_notification_period |
-      | host_notify_commands     |
-      | notify_host_down         |
-      | notify_host_unreachable  |
-      | notify_service_warning   |
-      | notify_service_recovery  |
-      | notify_service_critical  |
-      | notify_host_recovery     |
-      | service_notify_commands  |
-      | svc_notification_period  |
-    And I should see the following attributes for every contact:
-      | attribute                | nillable? |
-      | pager                    | true      |
-
-  @parse
-  Scenario: Parse + print netsaint contactgroups
-    Given NetSaint configuration is at "features/support/data/etc/netsaint"
-    When I run "flapjack-netsaint-parser" with the following arguments:
-      | argument                                    |
-      | print                                       |
-      | contactgroups                               |
-      | --source=features/support/data/etc/netsaint |
-    Then I should see a valid JSON output
-    And I should see a list of contactgroups
-    And I should see the following attributes for every contactgroup:
-      | attribute   |
-      | contacts    |
-      | group_alias |
-
-  @parse
-  Scenario: Parse + print netsaint hosts
-    Given NetSaint configuration is at "features/support/data/etc/netsaint"
-    When I run "flapjack-netsaint-parser" with the following arguments:
-      | argument                                    |
-      | print                                       |
-      | hosts                                       |
-      | --source=features/support/data/etc/netsaint |
-    Then I should see a valid JSON output
-    And I should see a list of hosts
-    And I should see the following attributes for every host:
-      | attribute             |
-      | host_alias            |
-      | address               |
-      | parent_hosts          |
-      | host_check_command    |
-      | max_attempts          |
-      | notification_interval |
-      | notification_period   |
-      | notify_recovery       |
-      | notify_down           |
-      | notify_unreachable    |
-    And I should see the following attributes for every host:
-      | attribute                | nillable? |
-      | event_handler            | true      |
-
-  @import
-  Scenario: Import Netsaint config
-    Given NetSaint configuration is at "features/support/data/etc/netsaint"
-    And no file exists at "features/support/tmp/dump.json"
-    And beanstalkd is running
-    And there are no jobs on the "checks" beanstalkd queue
-    When I run "flapjack-netsaint-parser" with the following arguments:
-      | argument                                      |
-      | dump                                          |
-      | --source=features/support/data/etc/netsaint   |
-      | --format=json                                 |
-      | --to=features/support/tmp/dump.json           |
-    Then I should see "features/support/tmp/dump.json" in the output
-    Then I should see valid JSON in "features/support/tmp/dump.json"
-    Then I should see a valid JSON batch in "features/support/tmp/dump.json"
-    When I run "flapjack-populator" with the following arguments:
-      | argument                                      |
-      | deploy                                        |
-      | --from=features/support/tmp/dump.json         |
-    Then I should see "Deployed batch \d+" in the output
-    Then there should be several jobs on the "checks" beanstalkd queue
-