Skip to content

Instantly share code, notes, and snippets.

View ryanycoleman's full-sized avatar

Ryan Coleman ryanycoleman

  • Stackery
  • Portland, OR
View GitHub Profile
# puppet module install domcleal-augeasproviders
# puppet resource sshd_config
# cp /etc/ssh/sshd_config /etc/ssh/sshd_config.good
# puppet apply sshd_config.pp
resources { 'sshd_config':
purge => true,
}

The pe-easy-agent.sh script mentioned in the instance_defaults hash is available at pe-easy-agent.sh

Monitor association changes string to array on one side, but other side is still a string. Causes a constantly change attempt:
-----
monitor_association changed '{"type"=>"MONITOR_RULE_TYPE_SINGLE", "quorum"=>"0", "monitor_templates"=>"/Common/MyMonitor"}' to '{"type"=>"MONITOR_RULE_TYPE_SINGLE", "monitor_templates"=>["/Common/MyMonitor"], "quorum"=>"0"}'
@ryanycoleman
ryanycoleman / tuesday.txt
Created September 19, 2014 18:51
Ryan's PuppetConf Picks
puppetconf { '2014':
ensure => busy,
website => 'puppetconf.com',
venue => 'sfo',
live_streaming => 'available',
}
11:10am - 11:50am
Getting Started with Puppet - Michael Stahnke, Puppet Labs - http://sched.co/1kR7leZ
Writing and Publishing Puppet Modules - Colleen Murphy, Puppet Labs - http://sched.co/1kR50kp
@ryanycoleman
ryanycoleman / a_puppet.sh
Last active August 29, 2015 14:07
POODLE remediation for Puppet Enterprise 3.3.x based on instructions found on the Puppet Labs blog: http://puppetlabs.com/blog/impact-assessment-sslv3-vulnerability-poodle-attack
/opt/puppet/bin/puppet module install herculesteam-augeasproviders_apache
/opt/puppet/bin/puppet apply puppetmaster.pp
/opt/puppet/bin/puppet apply puppetdashboard.pp
/opt/puppet/bin/puppet apply jetty.pp
@ryanycoleman
ryanycoleman / transfer_to_community.md
Created February 4, 2015 14:33
transfer_to_community.md

Advice for migrating existing [Forge] modules to Puppet-Community

Basics

Transferring a module to another owner is pretty simple when you break it down. See puppetlabs-nginx for an example.

Basically, you want to avoid surprising existing users of your module by raising a number of signals that will get their notice. It's as easy as 1-2-3!

  1. Transfer the GitHub repository to the puppet-community organization
  2. Prepare and release the "warning" Forge release to the existing namespace
@ryanycoleman
ryanycoleman / gist:1634941
Created January 18, 2012 19:03
mco puppetral
peadmin@training:~$ mco rpc puppetral create type=user title=elmo ensure=present
Determining the amount of hosts matching filter for 2 seconds .... 1
* [ ============================================================> ] 1 / 1
training.puppetlabs.lan
Status: Resource was created
Resource: {"exported"=>false,
"title"=>"elmo",
@ryanycoleman
ryanycoleman / gist:1648544
Created January 20, 2012 17:24
functions move
- Classes
- - parameterised
- - abbreviated_relationships
- - exercise_hidd
- Defined Resource Types
- - overview
- usage
- example
- module_structure
- exercise
# modulepath is /etc/puppetlabs/puppet/modules
# helloworld/manifests/init.pp
class helloworld {
file { '/tmp/hello':
ensure => file,
source => "puppet:///modules/helloworld/hello",
}
[root@centos6 lib]# puppet master --configprint libdir
/var/lib/puppet/lib
[root@centos6 lib]# tree .
.
├── hiera
│   ├── backend
│   │   └── puppet_backend.rb
│   └── scope.rb
└── puppet
└── parser