salted-rails 0.0.2

data/salt/munin/files/server/munin.conf

@@ -0,0 +1,107 @@
+# Example configuration file for Munin, generated by 'make build'
+
+# The next three variables specifies where the location of the RRD
+# databases, the HTML output, logs and the lock/pid files.  They all
+# must be writable by the user running munin-cron.  They are all
+# defaulted to the values you see here.
+#
+dbdir	/var/lib/munin
+htmldir /var/cache/munin/www
+logdir /var/log/munin
+rundir  /var/run/munin
+#
+# Where to look for the HTML templates
+tmpldir	/etc/munin/templates
+
+graph_width 500
+#graph_height 600
+
+# (Exactly one) directory to include all files from.
+#
+includedir /etc/munin/munin-conf.d
+
+
+# Make graphs show values per minute instead of per second
+#graph_period minute
+
+# Graphics files are normaly generated by munin-graph, no matter if
+# the graphs are used or not.  You can change this to
+# on-demand-graphing by following the instructions in
+# http://munin.projects.linpro.no/wiki/CgiHowto
+#
+#graph_strategy cgi
+
+# munin-cgi-graph is invoked by the web server up to very many times at the
+# same time.  This is not optimal since it results in high CPU and memory
+# consumption to the degree that the system can thrash.  Again the default is
+# 6.  Most likely the optimal number for max_cgi_graph_jobs is the same as
+# max_graph_jobs.
+#
+#munin_cgi_graph_jobs 6
+
+# If the automatic CGI url is wrong for your system override it here:
+#
+#cgiurl_graph /cgi-bin/munin-cgi-graph
+
+# munin-graph runs in parallel, the number of concurrent processes is
+# 6.  If you want munin-graph to not be parallel set to 0.  If set too
+# high it will slow down munin-graph.  Some experiments are needed to
+# determine how many are optimal on your system.  On a multi-core
+# system with good SCSI disks the number can probably be quite high.
+# 
+#max_graph_jobs 6
+
+# Drop somejuser@fnord.comm and anotheruser@blibb.comm an email everytime 
+# something changes (OK -> WARNING, CRITICAL -> OK, etc)
+#contact.someuser.command mail -s "Munin notification" somejuser@fnord.comm
+#contact.anotheruser.command mail -s "Munin notification" anotheruser@blibb.comm
+#
+# For those with Nagios, the following might come in handy. In addition,
+# the services must be defined in the Nagios server as well.
+#contact.nagios.command /usr/bin/send_nsca nagios.host.comm -c /etc/nsca.conf
+
+# a simple host tree
+[localhost]
+    address 127.0.0.1
+    use_node_name yes
+
+# 
+# A more complex example of a host tree
+#
+## First our "normal" host.
+# [fii.foo.com]
+#       address foo
+#
+## Then our other host...
+# [fay.foo.com]
+#       address fay
+#
+## Then we want totals...
+# [foo.com;Totals] #Force it into the "foo.com"-domain...
+#       update no   # Turn off data-fetching for this "host".
+#
+#   # The graph "load1". We want to see the loads of both machines... 
+#   # "fii=fii.foo.com:load.load" means "label=machine:graph.field"
+#       load1.graph_title Loads side by side
+#       load1.graph_order fii=fii.foo.com:load.load fay=fay.foo.com:load.load
+#
+#   # The graph "load2". Now we want them stacked on top of each other.
+#       load2.graph_title Loads on top of each other
+#       load2.dummy_field.stack fii=fii.foo.com:load.load fay=fay.foo.com:load.load
+#       load2.dummy_field.draw AREA # We want area instead the default LINE2.
+#       load2.dummy_field.label dummy # This is needed. Silly, really.
+#
+#   # The graph "load3". Now we want them summarised into one field
+#       load3.graph_title Loads summarised
+#       load3.combined_loads.sum fii.foo.com:load.load fay.foo.com:load.load
+#       load3.combined_loads.label Combined loads # Must be set, as this is
+#                                                 # not a dummy field!
+#
+## ...and on a side note, I want them listen in another order (default is
+## alphabetically)
+#
+# # Since [foo.com] would be interpreted as a host in the domain "com", we
+# # specify that this is a domain by adding a semicolon.
+# [foo.com;]
+#       node_order Totals fii.foo.com fay.foo.com
+#

data/salt/munin/nginx.sls

@@ -0,0 +1,13 @@
+munin-nginx-plugins:
+    file:
+        - recurse
+        - source: salt://munin/files/nginx/plugins
+        - name: /etc/munin/plugins
+        - mode: 755
+
+munin-nginx-plugin-conf:
+    file:
+        - recurse
+        - source: salt://munin/files/nginx/plugin-conf.d
+        - name: /etc/munin/plugin-conf.d
+        - mode: 755

data/salt/munin/node.sls

@@ -0,0 +1,34 @@
+# Example Configurations for Munin Node
+# Originally for Ubuntu 10.04, package
+# name may be different for your dist
+
+munin-node:
+    pkg:
+        - installed
+    service:
+        - running
+        - watch:
+            - file: core-munin-conf
+            - pkg: munin-node-dependancies
+
+# Dependancies for Several Custom Munin Plugins
+munin-node-dependancies:
+    pkg:
+        - installed
+        - names:
+            - libwww-perl
+
+# Configuration Files & Scripts
+munin-node-conf:
+    file:
+        - recurse
+        - source: salt://munin/files/node
+        - name: /etc/munin
+
+# Check Permissions of Plugins to Ensure They Are Executible
+chmod -R 755 /etc/munin/plugins/:
+    cmd:
+        - run
+        - unless: bash /etc/munin/checkPermissions.sh
+        - require:
+            - file: core-munin-conf

data/salt/munin/php5-fpm.sls

@@ -0,0 +1,13 @@
+munin-php5-fpm-plugins:
+    file:
+        - recurse
+        - source: salt://munin/files/php5-fpm/plugins
+        - name: /etc/munin/plugins
+        - mode: 755
+
+munin-php5-fpm-plugin-conf:
+    file:
+        - recurse
+        - source: salt://munin/files/php5-fpm/plugin-conf.d
+        - name: /etc/munin/plugin-conf.d
+        - mode: 755

data/salt/munin/server.sls

@@ -0,0 +1,7 @@
+# Example Configurations for Munin Server
+# Originally for Ubuntu 10.04, package
+# name may be different for your dist
+
+munin:
+	pkg:
+		- installed

data/salt/railsapp/database.sls

@@ -0,0 +1,25 @@
+include:
+  - databases.mysql.server
+
+database:
+  mysql_database.present:
+    - names:
+      - {{ pillar['database']['development']['database'] }}
+      - {{ pillar['database']['test']['database'] }}
+    - require:
+      - service.running: mysql-server
+      - pkg: mysql-server
+  mysql_user:
+    - present
+    - name: {{ pillar['database']['development']['username'] }}
+    - password: {{ pillar['database']['development']['password'] }}
+    - require:
+      - mysql_database.present: database
+  mysql_grants.present:
+    - database: {{ pillar['database']['development']['username'] }}_%.*
+    - grant: ALL PRIVILEGES
+    - user: {{ pillar['database']['development']['username'] }}
+    - host: localhost
+    - require:
+      - mysql_user.present: database
+

data/salt/railsapp/files/Gemfile

@@ -0,0 +1,57 @@
+# Either run vagrant or manually link Gemfile* to salt/salt/railsapps/files/ when Gemfile is changed
+
+source 'https://rubygems.org'
+
+gem 'rails', '1.2.6'
+
+gem 'image_science', '1.2.4'
+# drags in RubyInLIne which drags in ZenTest, which has a gemsepc in 4.3.4 that breaks in all but the most current rubygems (author refuses to fix)
+gem 'ZenTest', '4.3.3'  # '~> 4.3'
+
+# also in environment.rb because of passenger preloading
+gem 'mysql', '2.8.1'
+
+gem 'json', '~> 1.5.5'
+
+gem 'rake', '~> 0.9'
+
+gem 'rdoc'
+
+gem 'rdoc-data'
+# then  rdoc-data --install
+
+group :development do
+  gem 'bullet', '1.7.6'
+  gem 'capistrano', '2.11.2'
+  gem 'cgi_multipart_eof_fix', '2.5.0'
+  gem 'daemon_controller', '1.0.0'
+  gem 'diff-lcs', '1.1.3'
+  gem 'fastthread', '1.0.7'
+  gem 'gem_plugin', '0.2.3'
+  gem 'highline', '1.6.11'
+  gem 'hoe', '2.14.0'
+  gem 'linecache', '0.46'
+  gem 'mongrel', '1.1.5'
+  gem 'needle', '1.3.0'
+  gem 'net-scp', '1.0.4'
+  gem 'net-sftp', '2.0.5'
+  gem 'net-ssh', '2.3.0'
+  gem 'net-ssh-gateway', '1.1.0'
+  gem 'passenger', '3.0.11'
+  gem 'production_log_analyzer', '1.5.1'
+  gem 'rack', '1.2.4'
+  gem 'rails_analyzer_tools', '1.4.0'
+  gem 'rbx-require-relative', '0.0.9'
+  gem 'ruby-debug-base', '0.10.4'
+  gem 'ruby-debug-ide', '0.4.9'
+  gem 'rubyforge', '0.4.5'
+  gem 'SyslogLogger', '1.4.0'
+end
+
+group :test do
+  gem 'rcov', '0.9.11'
+  gem 'rspec', '1.1.12'
+  gem 'syntax' 			# syntax highlighting on rspec output
+  gem 'launchy', '>= 2.0.0'     # opsys independent launch browser
+  gem 'rspec-rails', '1.1.12'
+end

data/salt/railsapp/files/Gemfile.lock

@@ -0,0 +1,133 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    RubyInline (3.12.1)
+      ZenTest (~> 4.3)
+    SyslogLogger (1.4.0)
+      hoe (>= 1.2.0)
+    ZenTest (4.3.3)
+    actionmailer (1.3.6)
+      actionpack (= 1.13.6)
+    actionpack (1.13.6)
+      activesupport (= 1.4.4)
+    actionwebservice (1.2.6)
+      actionpack (= 1.13.6)
+      activerecord (= 1.15.6)
+    activerecord (1.15.6)
+      activesupport (= 1.4.4)
+    activesupport (1.4.4)
+    addressable (2.3.3)
+    bullet (1.7.6)
+    capistrano (2.11.2)
+      highline
+      net-scp (>= 1.0.0)
+      net-sftp (>= 2.0.0)
+      net-ssh (>= 2.0.14)
+      net-ssh-gateway (>= 1.1.0)
+    cgi_multipart_eof_fix (2.5.0)
+    daemon_controller (1.0.0)
+    daemons (1.1.9)
+    diff-lcs (1.1.3)
+    fastthread (1.0.7)
+    gem_plugin (0.2.3)
+    highline (1.6.11)
+    hoe (2.14.0)
+      rake (~> 0.8)
+    image_science (1.2.4)
+      RubyInline (~> 3.9)
+    json (1.5.5)
+    launchy (2.2.0)
+      addressable (~> 2.3)
+    linecache (0.46)
+      rbx-require-relative (> 0.0.4)
+    mongrel (1.1.5)
+      cgi_multipart_eof_fix (>= 2.4)
+      daemons (>= 1.0.3)
+      fastthread (>= 1.0.1)
+      gem_plugin (>= 0.2.3)
+    mysql (2.8.1)
+    needle (1.3.0)
+    net-scp (1.0.4)
+      net-ssh (>= 1.99.1)
+    net-sftp (2.0.5)
+      net-ssh (>= 2.0.9)
+    net-ssh (2.3.0)
+    net-ssh-gateway (1.1.0)
+      net-ssh (>= 1.99.1)
+    passenger (3.0.11)
+      daemon_controller (>= 0.2.5)
+      fastthread (>= 1.0.1)
+      rack
+      rake (>= 0.8.1)
+    production_log_analyzer (1.5.1)
+      rails_analyzer_tools (>= 1.4.0)
+    rack (1.2.4)
+    rails (1.2.6)
+      actionmailer (= 1.3.6)
+      actionpack (= 1.13.6)
+      actionwebservice (= 1.2.6)
+      activerecord (= 1.15.6)
+      activesupport (= 1.4.4)
+      rake (>= 0.7.2)
+    rails_analyzer_tools (1.4.0)
+      SyslogLogger (>= 1.4.0)
+      hoe (>= 1.2.0)
+    rake (0.9.6)
+    rbx-require-relative (0.0.9)
+    rcov (0.9.11)
+    rdoc (3.12.2)
+      json (~> 1.4)
+    rdoc-data (3.12)
+      rdoc (> 2.5, < 4.0)
+    rspec (1.1.12)
+    rspec-rails (1.1.12)
+      rspec (= 1.1.12)
+    ruby-debug-base (0.10.4)
+      linecache (>= 0.3)
+    ruby-debug-ide (0.4.9)
+      rake (>= 0.8.1)
+    rubyforge (0.4.5)
+    syntax (1.0.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  SyslogLogger (= 1.4.0)
+  ZenTest (= 4.3.3)
+  bullet (= 1.7.6)
+  capistrano (= 2.11.2)
+  cgi_multipart_eof_fix (= 2.5.0)
+  daemon_controller (= 1.0.0)
+  diff-lcs (= 1.1.3)
+  fastthread (= 1.0.7)
+  gem_plugin (= 0.2.3)
+  highline (= 1.6.11)
+  hoe (= 2.14.0)
+  image_science (= 1.2.4)
+  json (~> 1.5.5)
+  launchy (>= 2.0.0)
+  linecache (= 0.46)
+  mongrel (= 1.1.5)
+  mysql (= 2.8.1)
+  needle (= 1.3.0)
+  net-scp (= 1.0.4)
+  net-sftp (= 2.0.5)
+  net-ssh (= 2.3.0)
+  net-ssh-gateway (= 1.1.0)
+  passenger (= 3.0.11)
+  production_log_analyzer (= 1.5.1)
+  rack (= 1.2.4)
+  rails (= 1.2.6)
+  rails_analyzer_tools (= 1.4.0)
+  rake (~> 0.9)
+  rbx-require-relative (= 0.0.9)
+  rcov (= 0.9.11)
+  rdoc
+  rdoc-data
+  rspec (= 1.1.12)
+  rspec-rails (= 1.1.12)
+  ruby-debug-base (= 0.10.4)
+  ruby-debug-ide (= 0.4.9)
+  rubyforge (= 0.4.5)
+  syntax

data/salt/railsapp/gems.sls

@@ -0,0 +1,18 @@
+include:
+  - lang.ruby
+
+railsapp_gems:
+  file.recurse:
+    - source: salt://railsapp/files
+    - name: /tmp
+    - file_mode: 644
+    - user: {{ pillar['username'] }}
+  cmd.run:
+    # Run twice if first fails (weirdness with installing ruby-debug)
+    - name: {{ pillar['homedir'] }}/.rbenv/shims/bundle install || {{ pillar['homedir'] }}/.rbenv/shims/bundle install
+    - cwd: /tmp
+    - user: {{ pillar['username'] }}
+    - require:
+      - file: railsapp_gems
+      - gem.installed: base_gems
+

data/salt/railsapp/init.sls

@@ -0,0 +1,3 @@
+include:
+  - railsapp.gems
+  - railsapp.database

data/salt/run-standalone

@@ -0,0 +1,3 @@
+#!/bin/bash
+
+sudo salt-call state.highstate --local 

data/salt/salt/minion/config.template

@@ -0,0 +1,259 @@
+##### Primary configuration settings #####
+##########################################
+# Set the location of the salt master server, if the master server cannot be
+# resolved, then the minion will fail to start.
+#master: salt
+{% if master is defined -%} master: {{ master }}{% endif %}
+
+# Set the port used by the master reply and authentication server
+#master_port: 4506
+{% if master_port is defined -%} master_port: {{ master_port }}{% endif %}
+
+# The user to run salt
+#user: root
+{% if salt_user is defined -%} user: {{ salt_user }}{% endif %}
+
+# The root directory prepended to these options: pki_dir, cachedir, log_file.
+#root_dir: /
+{% if root_dir is defined -%} root_dir: {{ root_dir }}{% endif %}
+
+# The directory to store the pki information in
+#pki_dir: /etc/salt/pki
+{% if pki_dir is defined -%} pki_dir: {{ pki_dir }}{% endif %}
+
+# Explicitly declare the id for this minion to use, if left commented the id
+# will be the hostname as returned by the python call: socket.getfqdn()
+# Since salt uses detached ids it is possible to run multiple minions on the
+# same machine but with different ids, this can be useful for salt compute
+# clusters.
+#id:
+{% if id is defined -%} id: {{ id }}{% endif %}
+
+# Append a domain to a hostname in the event that it does not exist.  This is
+# useful for systems where socket.getfqdn() does not actually result in a
+# FQDN (for instance, Solaris).
+#append_domain:
+{% if append_domain is defined -%} append_domain: {{ append_domain }}{% endif %}
+
+# If the connection to the server is interrupted, the minion will
+# attempt to reconnect. sub_timeout allows you to control the rate
+# of reconnection attempts (in seconds). To disable reconnects, set
+# this value to 0.
+#sub_timeout: 60
+{% if sub_timeout is defined -%} sub_timeout: {{ sub_timeout }}{% endif %}
+
+# Where cache data goes
+#cachedir: /var/cache/salt
+{% if cachedir is defined -%} cachedir: {{ cachedir }}{% endif %}
+
+# The minion can locally cache the return data from jobs sent to it, this
+# can be a good way to keep track of jobs the minion has executed
+# (on the minion side). By default this feature is disabled, to enable
+# set cache_jobs to True
+#cache_jobs: False
+{% if cache_jobs is defined -%} cache_jobs: {{ cache_jobs }}{% endif %}
+
+# When waiting for a master to accept the minion's public key, salt will
+# continuously attempt to reconnect until successful. This is the time, in
+# seconds, between those reconnection attempts.
+#acceptance_wait_time = 10
+{% if acceptance_wait_time is defined -%} acceptance_wait_time: {{ acceptance_wait_time }}{% endif %}
+
+# When healing a dns_check is run, this is to make sure that the originally
+# resolved dns has not changed, if this is something that does not happen in
+# your environment then set this value to False.
+#dns_check: True
+{% if dns_check is defined -%} dns_check: {{ dns_check }}{% endif %}
+
+
+#####   Minion module management     #####
+##########################################
+# Disable specific modules. This allows the admin to limit the level of
+# access the master has to the minion
+#disable_modules: [cmd,test]
+{% if disable_modules is defined -%} disable_modules: {{ disable_modules }}{% endif %}
+#disable_returners: []
+{% if disable_returners is defined -%} disable_returners: {{ disable_returners }}{% endif %}
+#
+# Modules can be loaded from arbitrary paths. This enables the easy deployment
+# of third party modules. Modules for returners and minions can be loaded.
+# Specify a list of extra directories to search for minion modules and
+# returners. These paths must be fully qualified!
+#module_dirs: []
+{% if module_dirs is defined -%} module_dirs: {{ module_dirs }}{% endif %}
+#returner_dirs: []
+{% if returner_dirs is defined -%} returner_dirs: {{ returner_dirs }}{% endif %}
+#states_dirs: []
+{% if states_dirs is defined -%} states_dirs: {{ states_dirs }}{% endif %}
+#render_dirs: []
+{% if render_dirs is defined -%} render_dirs: {{ render_dirs }}{% endif %}
+#
+# A module provider can be statically overwritten or extended for the minion
+# via the providers option, in this case the default module will be
+# overwritten by the specified module. In this example the pkg module will
+# be provided by the yumpkg5 module instead of the system default.
+#
+# providers:
+#   pkg: yumpkg5
+#
+{% if providers is defined -%} providers: {{ providers }}{% endif %}
+# Enable Cython modules searching and loading. (Default: False)
+#cython_enable: False
+{% if cython_enable is defined -%} cython_enable: {{ cython_enable }}{% endif %}
+
+#####    State Management Settings    #####
+###########################################
+# The state management system executes all of the state templates on the minion
+# to enable more granular control of system state management. The type of
+# template and serialization used for state management needs to be configured
+# on the minion, the default renderer is yaml_jinja. This is a yaml file
+# rendered from a jinja template, the available options are:
+# yaml_jinja
+# yaml_mako
+# json_jinja
+# json_mako
+#
+#renderer: yaml_jinja
+{% if renderer is defined -%} renderer: {{ renderer }}{% endif %}
+#
+# autoload_dynamic_modules Turns on automatic loading of modules found in the
+# environments on the master. This is turned on by default, to turn of
+# autoloading modules when states run set this value to False
+#autoload_dynamic_modules: True
+{% if autoload_dynamic_modules is defined -%} autoload_dynamic_modules: {{ autoload_dynamic_modules }}{% endif %}
+#
+# clean_dynamic_modules keeps the dynamic modules on the minion in sync with
+# the dynamic modules on the master, this means that if a dynamic module is
+# not on the master it will be deleted from the minion. By default this is
+# enabled and can be disabled by changing this value to False
+#clean_dynamic_modules: True
+{% if clean_dynamic_modules is defined -%} clean_dynamic_modules: {{ clean_dynamic_modules }}{% endif %}
+#
+# Normally the minion is not isolated to any single environment on the master
+# when running states, but the environment can be isolated on the minion side
+# by statically setting it. Remember that the recommended way to manage
+# environments is to isolate via the top file.
+#environment: None
+{% if environment is defined -%} environment: {{ environment }}{% endif %}
+#
+# If using the local file directory, then the state top file name needs to be
+# defined, by default this is top.sls.
+#state_top: top.sls
+{% if state_top is defined -%} state_top: {{ state_top }}{% endif %}
+
+#####     File Directory Settings    #####
+##########################################
+# The Salt Minion can redirect all file server operations to a local directory,
+# this allows for the same state tree that is on the master to be used if
+# copied completely onto the minion. This is a literal copy of the settings on
+# the master but used to reference a local directory on the minion.
+
+# Set the file client, the client defaults to looking on the master server for
+# files, but can be directed to look at the local file directory setting 
+# defined below by setting it to local.
+#file_client: remote
+{% if file_client is defined -%} file_client: {{ file_client }}{% endif %}
+
+# The file directory works on environments passed to the minion, each environment
+# can have multiple root directories, the subdirectories in the multiple file
+# roots cannot match, otherwise the downloaded files will not be able to be
+# reliably ensured. A base environment is required to house the top file.
+# Example:
+# file_roots:
+#   base:
+#     - /srv/salt/
+#   dev:
+#     - /srv/salt/dev/services
+#     - /srv/salt/dev/states
+#   prod:
+#     - /srv/salt/prod/services
+#     - /srv/salt/prod/states
+#
+# Default:
+#file_roots:
+#  base:
+#    - /srv/salt
+{% if file_roots is defined -%} file_roots: {{ file_roots }}{% endif %}
+
+# The hash_type is the hash to use when discovering the hash of a file in
+# the minion directory, the default is md5, but sha1, sha224, sha256, sha384
+# and sha512 are also supported.
+#hash_type: md5
+{% if hash_type is defined -%} hash_type: {{ hash_type }}{% endif %}
+
+# The Salt pillar is searched for locally if file_client is set to local. If
+# this is the case, and pillar data is defined, then the pillar_roots need to
+# also be configured on the minion:
+#pillar_roots:
+#  base:
+#    - /srv/pillar
+{% if pillar_roots is defined -%} pillar_roots: {{ pillar_roots }}{% endif %}
+
+######        Security settings       #####
+###########################################
+# Enable "open mode", this mode still maintains encryption, but turns off
+# authentication, this is only intended for highly secure environments or for
+# the situation where your keys end up in a bad state. If you run in open mode
+# you do so at your own risk!
+#open_mode: False
+{% if open_mode is defined -%} open_mode: {{ open_mode }}{% endif %}
+
+
+######         Thread settings        #####
+###########################################
+# Disable multiprocessing support, by default when a minion receives a
+# publication a new process is spawned and the command is executed therein.
+#multiprocessing: True
+{% if multiprocessing is defined -%} multiprocessing: {{ multiprocessing }}{% endif %}
+
+######         Logging settings       #####
+###########################################
+# The location of the minion log file
+#log_file: /var/log/salt/minion
+#
+# The level of messages to send to the log file.
+# One of 'info', 'quiet', 'critical', 'error', 'debug', 'warning'.
+# Default: 'warning'
+#log_level: warning
+{% if log_level is defined -%} log_level: {{ log_level }}{% endif %}
+#
+# Logger levels can be used to tweak specific loggers logging levels.
+# For example, if you want to have the salt library at the 'warning' level,
+# but you still wish to have 'salt.modules' at the 'debug' level:
+#   log_granular_levels: {
+#     'salt': 'warning',
+#     'salt.modules': 'debug'
+#   }
+#
+#log_granular_levels: {}
+{% if log_granular_levels is defined -%} log_granular_levels: {{ log_granular_levels }}{% endif %}
+
+######      Module configuration      #####
+###########################################
+# Salt allows for modules to be passed arbitrary configuration data, any data
+# passed here in valid yaml format will be passed on to the salt minion modules
+# for use. It is STRONGLY recommended that a naming convention be used in which
+# the module name is followed by a . and then the value. Also, all top level
+# data must be applied via the yaml dict construct, some examples:
+#
+# A simple value for the test module:
+#test.foo: foo
+#
+# A list for the test module:
+#test.bar: [baz,quo]
+#
+# A dict for the test module:
+#test.baz: {spam: sausage, cheese: bread}
+
+{%- if module_settings is defined %}
+  {%- for modules in module_settings %}
+    {%- for module, options in modules.items() %}
+      {%- for option in options %}
+        {%- for key in option %}
+{{ module }}.{{ key }}: {{ option[key] }}
+
+        {%- endfor %}
+      {%- endfor %}
+    {%- endfor %}
+  {%- endfor %}
+{%- endif %}