syncwrap 1.0.0

data/History.rdoc

@@ -0,0 +1,2 @@
+=== 1.0.0 (2012-7-15)
+* Initial release.

data/Manifest.txt

@@ -0,0 +1,28 @@
+History.rdoc
+Manifest.txt
+README.rdoc
+Rakefile
+etc/init.d/iyyov
+etc/postgresql/9.1/main/environment
+etc/postgresql/9.1/main/pg_ctl.conf
+etc/postgresql/9.1/main/pg_hba.conf
+etc/postgresql/9.1/main/pg_ident.conf
+etc/postgresql/9.1/main/postgresql.conf
+etc/postgresql/9.1/main/start.conf
+etc/sysctl.d/61-postgresql-shm.conf
+lib/syncwrap/base.rb
+lib/syncwrap.rb
+lib/syncwrap/common.rb
+lib/syncwrap/distro.rb
+lib/syncwrap/ec2.rb
+lib/syncwrap/hashdot.rb
+lib/syncwrap/iyyov.rb
+lib/syncwrap/java.rb
+lib/syncwrap/jruby.rb
+lib/syncwrap/postgresql.rb
+lib/syncwrap/remote_task.rb
+lib/syncwrap/rhel.rb
+lib/syncwrap/ubuntu.rb
+lib/syncwrap/user_run.rb
+test/test_syncwrap.rb
+usr/local/bin/jgem

data/README.rdoc

@@ -0,0 +1,92 @@
+= SyncWrap
+
+* http://github.com/dekellum/syncwrap
+
+== Description
+
+A generalized and modular set of provisioning and deployment routines.
+The Rake-centric Vlad and not-actually-Rake Capistrano both suffer
+from lack of objects, e.g. the ability to customize and mix-in
+behavior. SyncWrap offers an Object/Module system that can be used
+with either.  Known to work with Vlad/rake-remote_task but could also
+be integrated with Capistrano, or others.
+
+== Features
+
+* Multi-line shell support in SyncWrap::Common#run,
+  SyncWrap::Common#sudo for more natural script embedding
+
+* SyncWrap::Common::rput offers some useful rsync magic, like setting
+  the owner of placed remote files
+
+* Platform differences are factored out into platform-specific modules
+
+* SyncWrap::RemoteTask rake-remote_task adapter (see synopsis below)
+
+* Gem install utilities. e.g. SyncWrap::JRuby#jruby_check_gem,
+  SyncWrap::JRuby#jruby_install_gem
+
+== Provisions
+
+Currently the following provisions are provided:
+
+* Complete SyncWrap::Java, SyncWrap::Hashdot, SyncWrap::JRuby stack
+
+* SyncWrap::PostgreSQL
+
+* SyncWrap::Iyyov job scheduler and process monitor
+
+* SyncWrap::UserRun for setup of a run user for deployed daemons, jobs
+  and var directories.
+
+== Synopsis
+
+For example, in your Rakefile with the SyncWrap::RemoteTask adapter:
+
+  class SyncWrapper
+
+    # Include these support modules for the tasks below, or include
+    # your own.
+
+    include SyncWrap::Java
+    include SyncWrap::Hashdot
+    include SyncWrap::JRuby
+    include SyncWrap::Ubuntu
+
+    include SyncWrap::RemoteTask
+
+    def initialize
+      super
+      self.common_prefix = '/usr/local'
+    end
+
+    def define_tasks
+      desc "Combined Java, Hashdot, JRuby Deployment"
+      remote_task :jruby_deploy do
+        java_install
+        hashdot_install
+        jruby_install
+      end
+    end
+
+    # Override any of the support methods as needed.
+
+  end
+
+  SyncWrapper.new.define_tasks
+
+== License
+
+Copyright (c) 2011-2012 David Kellum
+
+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.

data/Rakefile

@@ -0,0 +1,64 @@
+# -*- ruby -*-
+
+require 'rubygems'
+require 'bundler/setup'
+
+require 'rjack-tarpit'
+
+RJack::TarPit.new( 'syncwrap' ).define_tasks
+
+require 'syncwrap/java'
+require 'syncwrap/hashdot'
+require 'syncwrap/jruby'
+require 'syncwrap/iyyov'
+require 'syncwrap/ubuntu'
+require 'syncwrap/postgresql'
+require 'syncwrap/remote_task'
+
+class SyncWrapper
+  include SyncWrap::Java
+  include SyncWrap::Hashdot
+  include SyncWrap::JRuby
+  include SyncWrap::Iyyov
+  include SyncWrap::Ubuntu
+  include SyncWrap::PostgreSQL::Ubuntu
+
+  include SyncWrap::RemoteTask
+
+  def initialize
+    super
+
+    # SETUP: Install user@server instance goes here
+    set :domain, "localhost"
+
+  end
+
+  def define_tasks
+
+    desc "Combined Java, Hashdot, JRuby Deployment"
+    remote_task :jruby_deploy do
+      java_install
+      hashdot_install
+      jruby_install
+    end
+
+    desc "Deploy Iyyov Deamon"
+    remote_task :iyyov_deploy do
+      user_run_dir_setup
+      iyyov_install
+    end
+
+    desc "Deploy PostgreSQL"
+    remote_task :pg_deploy do
+      pg_install
+      pg_stop
+      pg_adjust_sysctl
+      pg_configure
+      pg_start
+    end
+
+  end
+
+end
+
+SyncWrapper.new.define_tasks

data/etc/init.d/iyyov

@@ -0,0 +1,98 @@
+#!/bin/sh
+
+### BEGIN INIT INFO
+# Provides:          iyyov
+# Required-Start:    $remote_fs $syslog
+# Required-Stop:     $remote_fs $syslog
+# Should-Start:      $named
+# Default-Start:     2 3 4 5
+# Default-Stop:
+# Short-Description: Iyyov jruby monitor
+# Description:       Iyyov jruby monitoring and job control daemon
+### END INIT INFO
+
+set -e
+
+. /lib/lsb/init-functions
+
+# Gem home directory
+# Set to match system "jgem environment path"
+gem_home="/usr/local/lib/jruby/gems"
+
+# (Exact) Gem version of iyyov to run
+version="1.1.3"
+
+# User to run the daemon as (should own rundir)
+user="runr"
+
+# Running directory (for jobs.rb config, log, and pid file)
+rundir="/var/local/runr/iyyov"
+
+prog="iyyov"
+daemon="${gem_home}/gems/iyyov-${version}-java/init/${prog}"
+config="${rundir}/jobs.rb"
+pidfile="${rundir}/${prog}.pid"
+
+RETVAL=0
+
+start() {
+    [ -x "$daemon" ] || exit 5
+    [ -f "$config" ] || exit 6
+    [ -d "$rundir" ] || exit 7
+
+    log_daemon_msg "Starting Iyyov Daemon" "iyyov"
+    start-stop-daemon --start -d $rundir -c $user --exec $daemon -- $config
+    RETVAL=$?
+    log_end_msg $RETVAL
+}
+
+status() {
+    if [ -f "$pidfile" ]; then
+        pid=`cat $pidfile`
+        echo "Status $prog: running pid $pid"
+    else
+        echo "Status $prog: not running"
+    fi
+}
+
+reload() {
+    if [ -e "$pidfile" ]; then
+        touch $config
+    fi
+}
+
+stop() {
+    log_daemon_msg "Stopping iyyov daemon" "iyyov"
+    start-stop-daemon --stop --quiet --oknodo --pidfile $pidfile
+    RETVAL=$?
+    log_end_msg $RETVAL
+}
+
+case "$1" in
+    start)
+        start
+        ;;
+    stop)
+        stop
+        ;;
+    status)
+        status
+        ;;
+    reload)
+        reload
+        ;;
+    restart)
+        stop
+        start
+        RETVAL=$?
+        ;;
+    condrestart)
+        [ -e $pidfile ] && restart
+        RETVAL=$?
+        ;;
+    *)
+        echo $"Usage: $0 {start|stop|status|reload|restart|condrestart}"
+        RETVAL=1
+esac
+
+exit $RETVAL

data/etc/postgresql/9.1/main/environment

@@ -0,0 +1,7 @@
+# environment variables for postmaster process
+# This file has the same syntax as postgresql.conf:
+#  VARIABLE = simple_value
+#  VARIABLE2 = 'any value!'
+# I. e. you need to enclose any value which does not only consist of letters,
+# numbers, and '-', '_', '.' in single quotes. Shell commands are not
+# evaluated.

data/etc/postgresql/9.1/main/pg_ctl.conf

@@ -0,0 +1,5 @@
+# Automatic pg_ctl configuration
+# This configuration file contains cluster specific options to be passed to
+# pg_ctl(1).
+
+pg_ctl_options = ''

data/etc/postgresql/9.1/main/pg_hba.conf

@@ -0,0 +1,96 @@
+# PostgreSQL Client Authentication Configuration File
+# ===================================================
+#
+# Refer to the "Client Authentication" section in the PostgreSQL
+# documentation for a complete description of this file.  A short
+# synopsis follows.
+#
+# This file controls: which hosts are allowed to connect, how clients
+# are authenticated, which PostgreSQL user names they can use, which
+# databases they can access.  Records take one of these forms:
+#
+# local      DATABASE  USER  METHOD  [OPTIONS]
+# host       DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+# hostssl    DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+# hostnossl  DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
+#
+# (The uppercase items must be replaced by actual values.)
+#
+# The first field is the connection type: "local" is a Unix-domain
+# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
+# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
+# plain TCP/IP socket.
+#
+# DATABASE can be "all", "sameuser", "samerole", "replication", a
+# database name, or a comma-separated list thereof. The "all"
+# keyword does not match "replication". Access to replication
+# must be enabled in a separate record (see example below).
+#
+# USER can be "all", a user name, a group name prefixed with "+", or a
+# comma-separated list thereof.  In both the DATABASE and USER fields
+# you can also write a file name prefixed with "@" to include names
+# from a separate file.
+#
+# ADDRESS specifies the set of hosts the record matches.  It can be a
+# host name, or it is made up of an IP address and a CIDR mask that is
+# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
+# specifies the number of significant bits in the mask.  A host name
+# that starts with a dot (.) matches a suffix of the actual host name.
+# Alternatively, you can write an IP address and netmask in separate
+# columns to specify the set of hosts.  Instead of a CIDR-address, you
+# can write "samehost" to match any of the server's own IP addresses,
+# or "samenet" to match any address in any subnet that the server is
+# directly connected to.
+#
+# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
+# "krb5", "ident", "peer", "pam", "ldap", "radius" or "cert".  Note that
+# "password" sends passwords in clear text; "md5" is preferred since
+# it sends encrypted passwords.
+#
+# OPTIONS are a set of options for the authentication in the format
+# NAME=VALUE.  The available options depend on the different
+# authentication methods -- refer to the "Client Authentication"
+# section in the documentation for a list of which options are
+# available for which authentication methods.
+#
+# Database and user names containing spaces, commas, quotes and other
+# special characters must be quoted.  Quoting one of the keywords
+# "all", "sameuser", "samerole" or "replication" makes the name lose
+# its special character, and just match a database or username with
+# that name.
+#
+# This file is read on server startup and when the postmaster receives
+# a SIGHUP signal.  If you edit the file on a running system, you have
+# to SIGHUP the postmaster for the changes to take effect.  You can
+# use "pg_ctl reload" to do that.
+
+# Put your actual configuration here
+# ----------------------------------
+#
+# If you want to allow non-local connections, you need to add more
+# "host" records.  In that case you will also need to make PostgreSQL
+# listen on a non-local interface via the listen_addresses
+# configuration parameter, or via the -i or -h command line switches.
+
+# DO NOT DISABLE!
+# If you change this first entry you will need to make sure that the
+# database superuser can access the database using some other method.
+# Noninteractive access to all databases is required during automatic
+# maintenance (custom daily cronjobs, replication, and similar tasks).
+#
+# Database administrative login by Unix domain socket
+local   all             postgres                                peer
+
+# TYPE  DATABASE        USER            ADDRESS                 METHOD
+
+# "local" is for Unix domain socket connections only
+local   all             all                                     peer
+# IPv4 local connections:
+host    all             all             127.0.0.1/32            trust
+# IPv6 local connections:
+host    all             all             ::1/128                 trust
+# Allow replication connections from localhost, by a user with the
+# replication privilege.
+#local   replication     postgres                                peer
+#host    replication     postgres        127.0.0.1/32            md5
+#host    replication     postgres        ::1/128                 md5

data/etc/postgresql/9.1/main/pg_ident.conf

@@ -0,0 +1,42 @@
+# PostgreSQL User Name Maps
+# =========================
+#
+# Refer to the PostgreSQL documentation, chapter "Client
+# Authentication" for a complete description.  A short synopsis
+# follows.
+#
+# This file controls PostgreSQL user name mapping.  It maps external
+# user names to their corresponding PostgreSQL user names.  Records
+# are of the form:
+#
+# MAPNAME  SYSTEM-USERNAME  PG-USERNAME
+#
+# (The uppercase quantities must be replaced by actual values.)
+#
+# MAPNAME is the (otherwise freely chosen) map name that was used in
+# pg_hba.conf.  SYSTEM-USERNAME is the detected user name of the
+# client.  PG-USERNAME is the requested PostgreSQL user name.  The
+# existence of a record specifies that SYSTEM-USERNAME may connect as
+# PG-USERNAME.
+#
+# If SYSTEM-USERNAME starts with a slash (/), it will be treated as a
+# regular expression.  Optionally this can contain a capture (a
+# parenthesized subexpression).  The substring matching the capture
+# will be substituted for \1 (backslash-one) if present in
+# PG-USERNAME.
+#
+# Multiple maps may be specified in this file and used by pg_hba.conf.
+#
+# No map names are defined in the default configuration.  If all
+# system user names and PostgreSQL user names are the same, you don't
+# need anything in this file.
+#
+# This file is read on server startup and when the postmaster receives
+# a SIGHUP signal.  If you edit the file on a running system, you have
+# to SIGHUP the postmaster for the changes to take effect.  You can
+# use "pg_ctl reload" to do that.
+
+# Put your actual configuration here
+# ----------------------------------
+
+# MAPNAME       SYSTEM-USERNAME         PG-USERNAME