jrmoserbaltimore

/usr/lib/ruby/1.9.1/psych.rb:203:in `parse': (/etc/puppet/hiera.yaml): found character that cannot start any token while scanning for the next token at line 3 column 5 (Psych::SyntaxError)
        from /usr/lib/ruby/1.9.1/psych.rb:203:in `parse_stream'
        from /usr/lib/ruby/1.9.1/psych.rb:151:in `parse'
        from /usr/lib/ruby/1.9.1/psych.rb:127:in `load'
        from /usr/lib/ruby/1.9.1/psych.rb:297:in `block in load_file'
        from /usr/lib/ruby/1.9.1/psych.rb:297:in `open'
        from /usr/lib/ruby/1.9.1/psych.rb:297:in `load_file'
        from /usr/lib/ruby/vendor_ruby/hiera/config.rb:54:in `yaml_load_file'
        from /usr/lib/ruby/vendor_ruby/hiera/config.rb:19:in `load'
        from /usr/lib/ruby/vendor_ruby/hiera.rb:47:in `initialize'

jrmoserbaltimore

node 'panera.example.com' {
  $sudogroup = 'wheel'

  user { 'baked':
    name    => 'Baked Pumpernickel',
    uid    => '1000',
    gid    => 'users',
    groups    => [ $sudogroup, 'puppet' ],
    shell    => '/bin/bash',
    password  => '$6$dJGfA238999hashthisstuff33deafcows7',

jrmoserbaltimore

---
classes:
  - puppet
puppet::servername:    'hq-ext-puppet.sbgnet.com'
puppet::repository:    'puppetlabs'
puppet::environment:   'dmz'
puppet::environments:
    - 'dmz'

jrmoserbaltimore

class pacemaker::config::crm {
  $crm_config          = $pacemaker::crm_config
  $crm_hash            = $pacemaker::crm_hash

  exec { 'dump crm config':
    command     => 'crm configure save /etc/corosync/config.crm',
    onlyif      => 'rm -f /etc/corosync/config.crm',
    path        => '/bin:/sbin:/usr/bin:/usr/sbin',
    tag         => 'pre-crm',
  }

jrmoserbaltimore

Getting Started

This chapter will be about getting started with Puppet 3.1. We will begin at the beginning by explaining some background on software configuration management tools, then move on to how to get Puppet running on your system and finally how to get it setup to start working with. At the end of this chapter you should understand why Puppet is around, why you should use it and you should be all setup to do so.

About Software Configuration Management

What is software configuration management, and why should you care? Software configuration management (SCM) refers to any strategy for tracking and controlling changes to the configuration of a software system. This includes the most basic style of simply keeping backups of configuration files at every change all the way up to centralized, role-based systems combined with version control systems (VCS) like Git; parallel job execution systems like Mcollective; and in some cases full lifecycle configuration management (CM) systems like The

jrmoserbaltimore

class wowza::config::license {
  $licensekey          = $::wowza::licensekey
  $licensesource       = $::wowza::licensesource

  file { '/usr/local/WowzaMediaServer':
    ensure   => link,
    target   => "/usr/local/WowzaMediaServer-$wowza_version",
    owner    => 'root',
    group    => 'root',
    mode     => '0777'

jrmoserbaltimore

---
gluster:
  peers:
    - peer-1.example.com:
  volumes:
    web:
      replicate: 2
      distribute: 2
      bricks:
        - peer-1.example.com:/mnt/silo0

jrmoserbaltimore

# type gluster::peer
# Verifies a peer in the Gluster cluster
#
define gluster::peer(
  $hostname,
) {
  $peergrep     = regsubst($hostname, '(\.)', '\\.', 'G')

  # Do unless current system is peer
  if ( $hostname != $::fqdn ) {

jrmoserbaltimore

  package { [
    'mod_passenger',
    'rubygem-minitest',
    'rubygem-bundler',
    'mysql-devel',
    'postgresql-devel',
    'sqlite-devel',
    'ruby-devel',
    'gcc',
    'make',

jrmoserbaltimore

<xml>
  <station>
    <call>ktit</call>
    <tz>America/New_York</tz>
    <daypart>
      <name>earlymorning</name>
      <schedule>
        <days>1,2,3,4,5</days>
        <starttime>0500</starttime>
        <endtime>0700</endtime>