initial commit

.gitignore

+*~
\ No newline at end of file

modules/joule/Gemfile

+source 'https://rubygems.org'
+
+puppetversion = ENV.key?('PUPPET_VERSION') ? "= #{ENV['PUPPET_VERSION']}" : ['>= 3.3']
+gem 'puppet', puppetversion
+gem 'puppetlabs_spec_helper', '>= 0.1.0'
+gem 'puppet-lint', '>= 0.3.2'
+gem 'facter', '>= 1.7.0'

modules/joule/README.md

+# joule
+
+#### Table of Contents
+
+1. [Overview](#overview)
+2. [Module Description - What the module does and why it is useful](#module-description)
+3. [Setup - The basics of getting started with joule](#setup)
+    * [What joule affects](#what-joule-affects)
+    * [Setup requirements](#setup-requirements)
+    * [Beginning with joule](#beginning-with-joule)
+4. [Usage - Configuration options and additional functionality](#usage)
+5. [Reference - An under-the-hood peek at what the module is doing and how](#reference)
+5. [Limitations - OS compatibility, etc.](#limitations)
+6. [Development - Guide for contributing to the module](#development)
+
+## Overview
+
+A one-maybe-two sentence summary of what the module does/what problem it solves.
+This is your 30 second elevator pitch for your module. Consider including
+OS/Puppet version it works with.
+
+## Module Description
+
+If applicable, this section should have a brief description of the technology
+the module integrates with and what that integration enables. This section
+should answer the questions: "What does this module *do*?" and "Why would I use
+it?"
+
+If your module has a range of functionality (installation, configuration,
+management, etc.) this is the time to mention it.
+
+## Setup
+
+### What joule affects
+
+* A list of files, packages, services, or operations that the module will alter,
+  impact, or execute on the system it's installed on.
+* This is a great place to stick any warnings.
+* Can be in list or paragraph form.
+
+### Setup Requirements **OPTIONAL**
+
+If your module requires anything extra before setting up (pluginsync enabled,
+etc.), mention it here.
+
+### Beginning with joule
+
+The very basic steps needed for a user to get the module up and running.
+
+If your most recent release breaks compatibility or requires particular steps
+for upgrading, you may wish to include an additional section here: Upgrading
+(For an example, see http://forge.puppetlabs.com/puppetlabs/firewall).
+
+## Usage
+
+Put the classes, types, and resources for customizing, configuring, and doing
+the fancy stuff with your module here.
+
+## Reference
+
+Here, list the classes, types, providers, facts, etc contained in your module.
+This section should include all of the under-the-hood workings of your module so
+people know what the module is touching on their system but don't need to mess
+with things. (We are working on automating this section!)
+
+## Limitations
+
+This is where you list OS compatibility, version compatibility, etc.
+
+## Development
+
+Since your module is awesome, other users will want to play with it. Let them
+know what the ground rules for contributing are.
+
+## Release Notes/Contributors/Etc **Optional**
+
+If you aren't using changelog, put your release notes here (though you should
+consider using changelog). You may also add any additional sections you feel are
+necessary or important to include here. Please use the `## ` header.

modules/joule/Rakefile

+require 'rubygems'
+require 'puppetlabs_spec_helper/rake_tasks'
+require 'puppet-lint/tasks/puppet-lint'
+PuppetLint.configuration.send('disable_80chars')
+PuppetLint.configuration.ignore_paths = ["spec/**/*.pp", "pkg/**/*.pp"]
+
+desc "Validate manifests, templates, and ruby files"
+task :validate do
+  Dir['manifests/**/*.pp'].each do |manifest|
+    sh "puppet parser validate --noop #{manifest}"
+  end
+  Dir['spec/**/*.rb','lib/**/*.rb'].each do |ruby_file|
+    sh "ruby -c #{ruby_file}" unless ruby_file =~ /spec\/fixtures/
+  end
+  Dir['templates/**/*.erb'].each do |template|
+    sh "erb -P -x -T '-' #{template} | ruby -c"
+  end
+end

modules/joule/manifests/init.pp

+# == Class: joule
+#
+# Full description of class joule here.
+#
+# === Parameters
+#
+# Document parameters here.
+#
+# [*sample_parameter*]
+#   Explanation of what this parameter affects and what it defaults to.
+#   e.g. "Specify one or more upstream ntp servers as an array."
+#
+# === Variables
+#
+# Here you should define a list of variables that this module would require.
+#
+# [*sample_variable*]
+#   Explanation of how this variable affects the funtion of this class and if
+#   it has a default. e.g. "The parameter enc_ntp_servers must be set by the
+#   External Node Classifier as a comma separated list of hostnames." (Note,
+#   global variables should be avoided in favor of class parameters as
+#   of Puppet 2.6.)
+#
+# === Examples
+#
+#  class { 'joule':
+#    servers => [ 'pool.ntp.org', 'ntp.local.company.com' ],
+#  }
+#
+# === Authors
+#
+# Author Name <author@domain.com>
+#
+# === Copyright
+#
+# Copyright 2017 Your name here, unless otherwise noted.
+#
+
+
+class joule {
+  $pip_url="http://nuc.office:8080/"
+  $pip_cmd="pip3 install --extra-index-url ${pip_url} --trusted-host nuc.office"
+
+
+  $deps = ['libblas-dev', 'liblapack-dev', 'gfortran']
+  package{ $deps:
+    ensure => present,
+    before => Exec['install_joule']
+  }
+  
+  exec{'install_joule':
+    command => "${pip_cmd} joule",
+    timeout => 0,
+    path => ["/usr/local/bin","/usr/bin"]
+  }
+  exec{'initialize_joule':
+    command => "joule initialize",
+    path => ["/usr/local/bin","/usr/sbin","/bin"],
+    creates => "/etc/joule/main.conf",
+    require => Exec['install_joule']
+  }
+    
+
+}

modules/joule/metadata.json

+{
+  "name": "jdonnal-joule",
+  "version": "0.1.0",
+  "author": "jdonnal",
+  "summary": "Install joule data processing framework",
+  "license": "Apache 2.0",
+  "source": "git.wattsworth.net",
+  "project_page": "git.wattsworth.net",
+  "issues_url": "git.wattsworth.net",
+  "dependencies": [
+    {"name":"puppetlabs-stdlib","version_requirement":">= 1.0.0"}
+  ]
+}
+

modules/joule/spec/classes/init_spec.rb

+require 'spec_helper'
+describe 'joule' do
+
+  context 'with defaults for all parameters' do
+    it { should contain_class('joule') }
+  end
+end

modules/joule/spec/spec_helper.rb

+require 'puppetlabs_spec_helper/module_spec_helper'

modules/joule/tests/init.pp

+# The baseline for module testing used by Puppet Labs is that each manifest
+# should have a corresponding test manifest that declares that class or defined
+# type.
+#
+# Tests are then run by using puppet apply --noop (to check for compilation
+# errors and view a log of events) or by fully applying the test in a virtual
+# environment (to compare the resulting system state to the desired state).
+#
+# Learn more about module testing here:
+# http://docs.puppetlabs.com/guides/tests_smoke.html
+#
+include joule

modules/nilmdb/Gemfile

+source 'https://rubygems.org'
+
+puppetversion = ENV.key?('PUPPET_VERSION') ? "= #{ENV['PUPPET_VERSION']}" : ['>= 3.3']
+gem 'puppet', puppetversion
+gem 'puppetlabs_spec_helper', '>= 0.1.0'
+gem 'puppet-lint', '>= 0.3.2'
+gem 'facter', '>= 1.7.0'

modules/nilmdb/README.md

+# nilmdb
+
+#### Table of Contents
+
+1. [Overview](#overview)
+2. [Module Description - What the module does and why it is useful](#module-description)
+3. [Setup - The basics of getting started with nilmdb](#setup)
+    * [What nilmdb affects](#what-nilmdb-affects)
+    * [Setup requirements](#setup-requirements)
+    * [Beginning with nilmdb](#beginning-with-nilmdb)
+4. [Usage - Configuration options and additional functionality](#usage)
+5. [Reference - An under-the-hood peek at what the module is doing and how](#reference)
+5. [Limitations - OS compatibility, etc.](#limitations)
+6. [Development - Guide for contributing to the module](#development)
+
+## Overview
+
+A one-maybe-two sentence summary of what the module does/what problem it solves.
+This is your 30 second elevator pitch for your module. Consider including
+OS/Puppet version it works with.
+
+## Module Description
+
+If applicable, this section should have a brief description of the technology
+the module integrates with and what that integration enables. This section
+should answer the questions: "What does this module *do*?" and "Why would I use
+it?"
+
+If your module has a range of functionality (installation, configuration,
+management, etc.) this is the time to mention it.
+
+## Setup
+
+### What nilmdb affects
+
+* A list of files, packages, services, or operations that the module will alter,
+  impact, or execute on the system it's installed on.
+* This is a great place to stick any warnings.
+* Can be in list or paragraph form.
+
+### Setup Requirements **OPTIONAL**
+
+If your module requires anything extra before setting up (pluginsync enabled,
+etc.), mention it here.
+
+### Beginning with nilmdb
+
+The very basic steps needed for a user to get the module up and running.
+
+If your most recent release breaks compatibility or requires particular steps
+for upgrading, you may wish to include an additional section here: Upgrading
+(For an example, see http://forge.puppetlabs.com/puppetlabs/firewall).
+
+## Usage
+
+Put the classes, types, and resources for customizing, configuring, and doing
+the fancy stuff with your module here.
+
+## Reference
+
+Here, list the classes, types, providers, facts, etc contained in your module.
+This section should include all of the under-the-hood workings of your module so
+people know what the module is touching on their system but don't need to mess
+with things. (We are working on automating this section!)
+
+## Limitations
+
+This is where you list OS compatibility, version compatibility, etc.
+
+## Development
+
+Since your module is awesome, other users will want to play with it. Let them
+know what the ground rules for contributing are.
+
+## Release Notes/Contributors/Etc **Optional**
+
+If you aren't using changelog, put your release notes here (though you should
+consider using changelog). You may also add any additional sections you feel are
+necessary or important to include here. Please use the `## ` header.

modules/nilmdb/Rakefile

+require 'rubygems'
+require 'puppetlabs_spec_helper/rake_tasks'
+require 'puppet-lint/tasks/puppet-lint'
+PuppetLint.configuration.send('disable_80chars')
+PuppetLint.configuration.ignore_paths = ["spec/**/*.pp", "pkg/**/*.pp"]
+
+desc "Validate manifests, templates, and ruby files"
+task :validate do
+  Dir['manifests/**/*.pp'].each do |manifest|
+    sh "puppet parser validate --noop #{manifest}"
+  end
+  Dir['spec/**/*.rb','lib/**/*.rb'].each do |ruby_file|
+    sh "ruby -c #{ruby_file}" unless ruby_file =~ /spec\/fixtures/
+  end
+  Dir['templates/**/*.erb'].each do |template|
+    sh "erb -P -x -T '-' #{template} | ruby -c"
+  end
+end

modules/nilmdb/manifests/init.pp

+# == Class: nilmdb
+#
+# Full description of class nilmdb here.
+#
+# === Parameters
+#
+# Document parameters here.
+#
+# [*sample_parameter*]
+#   Explanation of what this parameter affects and what it defaults to.
+#   e.g. "Specify one or more upstream ntp servers as an array."
+#
+# === Variables
+#
+# Here you should define a list of variables that this module would require.
+#
+# [*sample_variable*]
+#   Explanation of how this variable affects the funtion of this class and if
+#   it has a default. e.g. "The parameter enc_ntp_servers must be set by the
+#   External Node Classifier as a comma separated list of hostnames." (Note,
+#   global variables should be avoided in favor of class parameters as
+#   of Puppet 2.6.)
+#
+# === Examples
+#
+#  class { 'nilmdb':
+#    servers => [ 'pool.ntp.org', 'ntp.local.company.com' ],
+#  }
+#
+# === Authors
+#
+# Author Name <author@domain.com>
+#
+# === Copyright
+#
+# Copyright 2017 Your name here, unless otherwise noted.
+#
+class nilmdb {
+
+
+}

modules/nilmdb/metadata.json

+{
+  "name": "jdonnal-nilmdb",
+  "version": "0.1.0",
+  "author": "John Donnal",
+  "summary": "Install NilmDB and nilmtools",
+  "license": "Apache 2.0",
+  "source": "git.wattsworth.net",
+  "project_page": "git.wattsworth.net",
+  "issues_url": "git.wattsworth.net",
+  "dependencies": [
+    {"name":"puppetlabs-stdlib","version_requirement":">= 1.0.0"}
+  ]
+}
+

modules/nilmdb/spec/classes/init_spec.rb

+require 'spec_helper'
+describe 'nilmdb' do
+
+  context 'with defaults for all parameters' do
+    it { should contain_class('nilmdb') }
+  end
+end

modules/nilmdb/spec/spec_helper.rb

+require 'puppetlabs_spec_helper/module_spec_helper'

modules/nilmdb/tests/init.pp

+# The baseline for module testing used by Puppet Labs is that each manifest
+# should have a corresponding test manifest that declares that class or defined
+# type.
+#
+# Tests are then run by using puppet apply --noop (to check for compilation
+# errors and view a log of events) or by fully applying the test in a virtual
+# environment (to compare the resulting system state to the desired state).
+#
+# Learn more about module testing here:
+# http://docs.puppetlabs.com/guides/tests_smoke.html
+#
+include nilmdb

modules/python3/Gemfile

+source 'https://rubygems.org'
+
+puppetversion = ENV.key?('PUPPET_VERSION') ? "= #{ENV['PUPPET_VERSION']}" : ['>= 3.3']
+gem 'puppet', puppetversion
+gem 'puppetlabs_spec_helper', '>= 0.1.0'
+gem 'puppet-lint', '>= 0.3.2'
+gem 'facter', '>= 1.7.0'

modules/python3/README.md

+# python3
+
+#### Table of Contents
+
+1. [Overview](#overview)
+2. [Module Description - What the module does and why it is useful](#module-description)
+3. [Setup - The basics of getting started with python3](#setup)
+    * [What python3 affects](#what-python3-affects)
+    * [Setup requirements](#setup-requirements)
+    * [Beginning with python3](#beginning-with-python3)
+4. [Usage - Configuration options and additional functionality](#usage)
+5. [Reference - An under-the-hood peek at what the module is doing and how](#reference)
+5. [Limitations - OS compatibility, etc.](#limitations)
+6. [Development - Guide for contributing to the module](#development)
+
+## Overview
+
+A one-maybe-two sentence summary of what the module does/what problem it solves.
+This is your 30 second elevator pitch for your module. Consider including
+OS/Puppet version it works with.
+
+## Module Description
+
+If applicable, this section should have a brief description of the technology
+the module integrates with and what that integration enables. This section
+should answer the questions: "What does this module *do*?" and "Why would I use
+it?"
+
+If your module has a range of functionality (installation, configuration,
+management, etc.) this is the time to mention it.
+
+## Setup
+
+### What python3 affects
+
+* A list of files, packages, services, or operations that the module will alter,
+  impact, or execute on the system it's installed on.
+* This is a great place to stick any warnings.
+* Can be in list or paragraph form.
+
+### Setup Requirements **OPTIONAL**
+
+If your module requires anything extra before setting up (pluginsync enabled,
+etc.), mention it here.
+
+### Beginning with python3
+
+The very basic steps needed for a user to get the module up and running.
+
+If your most recent release breaks compatibility or requires particular steps
+for upgrading, you may wish to include an additional section here: Upgrading
+(For an example, see http://forge.puppetlabs.com/puppetlabs/firewall).
+
+## Usage
+
+Put the classes, types, and resources for customizing, configuring, and doing
+the fancy stuff with your module here.
+
+## Reference
+
+Here, list the classes, types, providers, facts, etc contained in your module.
+This section should include all of the under-the-hood workings of your module so
+people know what the module is touching on their system but don't need to mess
+with things. (We are working on automating this section!)
+
+## Limitations
+
+This is where you list OS compatibility, version compatibility, etc.
+
+## Development
+
+Since your module is awesome, other users will want to play with it. Let them
+know what the ground rules for contributing are.
+
+## Release Notes/Contributors/Etc **Optional**
+
+If you aren't using changelog, put your release notes here (though you should
+consider using changelog). You may also add any additional sections you feel are
+necessary or important to include here. Please use the `## ` header.

modules/python3/Rakefile

+require 'rubygems'
+require 'puppetlabs_spec_helper/rake_tasks'
+require 'puppet-lint/tasks/puppet-lint'
+PuppetLint.configuration.send('disable_80chars')
+PuppetLint.configuration.ignore_paths = ["spec/**/*.pp", "pkg/**/*.pp"]
+
+desc "Validate manifests, templates, and ruby files"
+task :validate do
+  Dir['manifests/**/*.pp'].each do |manifest|
+    sh "puppet parser validate --noop #{manifest}"
+  end
+  Dir['spec/**/*.rb','lib/**/*.rb'].each do |ruby_file|
+    sh "ruby -c #{ruby_file}" unless ruby_file =~ /spec\/fixtures/
+  end
+  Dir['templates/**/*.erb'].each do |template|
+    sh "erb -P -x -T '-' #{template} | ruby -c"
+  end
+end

modules/python3/lib/facter/pip_version.rb

+Facter.add('pip_version') do
+  setcode do
+    long_name = Facter::Core::Execution.exec('pip3 -V')
+    version = long_name.split(" ")[1] # eg: pip 9.0.1 from /usr/local/... (python 3.5)
+    major_number = version.split(".")[0].to_i
+    major_number
+  end
+end

modules/python3/lib/facter/python_version.rb

+Facter.add('python_version') do
+  setcode do
+    Facter::Core::Execution.exec('python3 -V')
+  end
+end

modules/python3/manifests/build.pp

+class python3::build {
+
+  notify { "python3 is at [${::python_version}], building 3.5.2 from source": }
+  
+  $build_deps = ["libssl-dev",
+                 "build-essential",
+                 "libncursesw5-dev",
+                 "libreadline-dev",
+                 "libgdbm-dev",
+                 "libc6-dev",
+                 "libsqlite3-dev",
+                 "tk-dev",
+                 "lzma-dev",
+                 "libbz2-dev"]
+  
+  package { $build_deps:
+    ensure => present
+  }
+  #get the source code
+  exec { 'wget_python':
+    command => "/usr/bin/wget https://www.python.org/ftp/python/3.5.2/Python-3.5.2.tgz",
+    cwd     => "/tmp",
+    creates => "/tmp/Python-3.5.2.tgz"
+  }
+  #extract the source code
+  exec { 'untar_python':
+    command => "/bin/tar -xvf Python-3.5.2.tgz",
+    cwd     => "/tmp",
+    creates => "/tmp/Python-3.5.2",
+    require => [Exec['wget_python']]
+  }
+  #compile the code
+  exec { 'compile_python':
+    command => "/bin/sh configure && /usr/bin/make && /usr/bin/make install",
+    cwd     => "/tmp/Python-3.5.2",
+    timeout => 0, #disable timeout
+    creates => "/usr/local/bin/python3",
+    require => [Exec['untar_python']]
+  }
+
+}

modules/python3/manifests/init.pp

+# == Class: python3
+#
+# Install Python >= 3.5 on RPi systems
+#
+# === Parameters
+# None
+# === Variables
+# None
+# === Examples
+#  include 'python3'
+# === Authors
+#
+# John Donnal <donnal@usna.edu>
+#
+# === Copyright
+#
+# Copyright 2017 John Donnal, unless otherwise noted.
+#
+class python3 {
+  if $::python_version != 'Python 3.5.2' {
+    include python3::build
+  }
+  if $::pip_version < 9 {
+    include python3::upgrade
+  }
+}

modules/python3/manifests/upgrade.pp

+
+class python3::upgrade {
+
+  exec{'upgrade_pip':
+    command => "pip3 install --upgrade pip"
+    path => ["/usr/local/bin","usr/bin"]
+  }
+}

modules/python3/metadata.json

+{
+  "name": "jdonnal-python3",
+  "version": "0.1.0",
+  "author": "John Donnal",
+  "summary": "Install Python >= 3.5 on RPi",
+  "license": "Apache 2.0",
+  "source": "git.wattsworth.net",
+  "project_page": "git.wattsworth.net",
+  "issues_url": "git.wattsworth.net",
+  "dependencies": [
+    {"name":"puppetlabs-stdlib","version_requirement":">= 1.0.0"}
+  ]
+}
+

modules/python3/spec/classes/init_spec.rb

+require 'spec_helper'
+describe 'python3' do
+
+  context 'with defaults for all parameters' do
+    it { should contain_class('python3') }
+  end
+end

modules/python3/spec/spec_helper.rb

+require 'puppetlabs_spec_helper/module_spec_helper'

modules/python3/tests/init.pp

+# The baseline for module testing used by Puppet Labs is that each manifest
+# should have a corresponding test manifest that declares that class or defined
+# type.
+#
+# Tests are then run by using puppet apply --noop (to check for compilation
+# errors and view a log of events) or by fully applying the test in a virtual
+# environment (to compare the resulting system state to the desired state).
+#
+# Learn more about module testing here:
+# http://docs.puppetlabs.com/guides/tests_smoke.html
+#
+include python3

modules/raspi/Gemfile

+source 'https://rubygems.org'
+
+puppetversion = ENV.key?('PUPPET_VERSION') ? "= #{ENV['PUPPET_VERSION']}" : ['>= 3.3']
+gem 'puppet', puppetversion
+gem 'puppetlabs_spec_helper', '>= 0.1.0'
+gem 'puppet-lint', '>= 0.3.2'
+gem 'facter', '>= 1.7.0'

modules/raspi/README.md

+# raspi
+
+#### Table of Contents
+
+1. [Overview](#overview)
+2. [Module Description - What the module does and why it is useful](#module-description)
+3. [Setup - The basics of getting started with raspi](#setup)
+    * [What raspi affects](#what-raspi-affects)
+    * [Setup requirements](#setup-requirements)
+    * [Beginning with raspi](#beginning-with-raspi)
+4. [Usage - Configuration options and additional functionality](#usage)
+5. [Reference - An under-the-hood peek at what the module is doing and how](#reference)
+5. [Limitations - OS compatibility, etc.](#limitations)
+6. [Development - Guide for contributing to the module](#development)
+
+## Overview
+
+A one-maybe-two sentence summary of what the module does/what problem it solves.
+This is your 30 second elevator pitch for your module. Consider including
+OS/Puppet version it works with.
+
+## Module Description
+
+If applicable, this section should have a brief description of the technology
+the module integrates with and what that integration enables. This section
+should answer the questions: "What does this module *do*?" and "Why would I use
+it?"
+
+If your module has a range of functionality (installation, configuration,
+management, etc.) this is the time to mention it.
+
+## Setup
+
+### What raspi affects
+
+* A list of files, packages, services, or operations that the module will alter,
+  impact, or execute on the system it's installed on.
+* This is a great place to stick any warnings.
+* Can be in list or paragraph form.
+
+### Setup Requirements **OPTIONAL**
+
+If your module requires anything extra before setting up (pluginsync enabled,
+etc.), mention it here.
+
+### Beginning with raspi
+
+The very basic steps needed for a user to get the module up and running.
+
+If your most recent release breaks compatibility or requires particular steps
+for upgrading, you may wish to include an additional section here: Upgrading
+(For an example, see http://forge.puppetlabs.com/puppetlabs/firewall).
+
+## Usage
+
+Put the classes, types, and resources for customizing, configuring, and doing
+the fancy stuff with your module here.
+
+## Reference
+
+Here, list the classes, types, providers, facts, etc contained in your module.
+This section should include all of the under-the-hood workings of your module so
+people know what the module is touching on their system but don't need to mess
+with things. (We are working on automating this section!)
+
+## Limitations
+
+This is where you list OS compatibility, version compatibility, etc.
+
+## Development
+
+Since your module is awesome, other users will want to play with it. Let them
+know what the ground rules for contributing are.
+
+## Release Notes/Contributors/Etc **Optional**
+
+If you aren't using changelog, put your release notes here (though you should
+consider using changelog). You may also add any additional sections you feel are
+necessary or important to include here. Please use the `## ` header.

modules/raspi/Rakefile

+require 'rubygems'
+require 'puppetlabs_spec_helper/rake_tasks'
+require 'puppet-lint/tasks/puppet-lint'
+PuppetLint.configuration.send('disable_80chars')
+PuppetLint.configuration.ignore_paths = ["spec/**/*.pp", "pkg/**/*.pp"]
+
+desc "Validate manifests, templates, and ruby files"
+task :validate do
+  Dir['manifests/**/*.pp'].each do |manifest|
+    sh "puppet parser validate --noop #{manifest}"
+  end
+  Dir['spec/**/*.rb','lib/**/*.rb'].each do |ruby_file|
+    sh "ruby -c #{ruby_file}" unless ruby_file =~ /spec\/fixtures/
+  end
+  Dir['templates/**/*.erb'].each do |template|
+    sh "erb -P -x -T '-' #{template} | ruby -c"
+  end
+end

modules/raspi/files/keyboard

+# Managed by puppet
+
+XKBMODEL="pc105"
+XKBLAYOUT="us"
+XKBVARIANT=""
+XKBOPTIONS=""
+
+BACKSPACE="guess"

modules/raspi/files/locale

+en_US.UTF-8 UTF-8

modules/raspi/files/timezone

+America/New_York

modules/raspi/manifests/init.pp

+# == Class: raspi
+#
+# Set locale to en-US UTF-8
+# Set timezone to America/New_York
+# Set keyboard to US pc-105
+#
+# === Parameters
+#
+# === Variables
+#
+# === Examples
+#
+# === Authors
+#
+# Author Name <author@domain.com>
+#
+# === Copyright
+#
+# Copyright 2017 Your name here, unless otherwise noted.
+#
+class raspi {
+
+  # set keyboard
+  file{ "/etc/default/keyboard":
+    source => "puppet:///modules/raspi/keyboard",
+    owner => root,
+    group => root
+  }
+  exec{ "/bin/setupcon":
+    refreshonly => true,
+    subscribe => File["/etc/default/keyboard"]
+  }
+  
+  # set locale
+  file{ "/etc/default/locale":
+    source => "puppet:///modules/raspi/locale",
+    owner => root,
+    group => root
+  }
+  exec{ "/usr/sbin/locale-gen":
+    refreshonly => true,
+    subscribe => File["/etc/default/locale"]
+  }
+
+  # set timezone
+  file{ "/etc/timezone":
+    source => "puppet:///modules/raspi/timezone",
+    owner => root,
+    group => root
+  }
+  exec{"/usr/sbin/dpkg-reconfigure -f noninteractive tzdata":
+    refreshonly => true,
+    subscribe => File['/etc/timezone']
+  }
+
+}

modules/raspi/metadata.json

+{
+  "name": "jdonnal-raspi",
+  "version": "0.1.0",
+  "author": "John Donnal",
+  "summary": "configure raspi to American defaults",
+  "license": "Apache 2.0",
+  "source": "git.wattsworth.net",
+  "project_page": "git.wattsworth.net",
+  "issues_url": "git.wattsworth.net",
+  "dependencies": [
+    {"name":"puppetlabs-stdlib","version_requirement":">= 1.0.0"}
+  ]
+}
+

modules/raspi/spec/classes/init_spec.rb

+require 'spec_helper'
+describe 'raspi' do
+
+  context 'with defaults for all parameters' do
+    it { should contain_class('raspi') }
+  end
+end

modules/raspi/spec/spec_helper.rb

+require 'puppetlabs_spec_helper/module_spec_helper'

modules/raspi/tests/init.pp

+# The baseline for module testing used by Puppet Labs is that each manifest
+# should have a corresponding test manifest that declares that class or defined
+# type.
+#
+# Tests are then run by using puppet apply --noop (to check for compilation
+# errors and view a log of events) or by fully applying the test in a virtual
+# environment (to compare the resulting system state to the desired state).
+#
+# Learn more about module testing here:
+# http://docs.puppetlabs.com/guides/tests_smoke.html
+#
+include raspi

site.pp

+node 'raspberrypi' {
+  include python3
+  include joule
+  include raspi
+}