<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Puppet on Jason Hancock</title>
    <link>https://geek.jasonhancock.com/tags/puppet/</link>
    <description>Recent content in Puppet on Jason Hancock</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2017 Jason Hancock. All Rights Reserved</copyright>
    <lastBuildDate>Sat, 06 Oct 2012 04:38:47 +0000</lastBuildDate>
    
	<atom:link href="https://geek.jasonhancock.com/tags/puppet/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>puppet certified professional</title>
      <link>https://geek.jasonhancock.com/2012/10/05/puppet-certified-professional/</link>
      <pubDate>Sat, 06 Oct 2012 04:38:47 +0000</pubDate>
      
      <guid>https://geek.jasonhancock.com/2012/10/05/puppet-certified-professional/</guid>
      <description>It&amp;rsquo;s official. I&amp;rsquo;m a Puppet Certified Professional. I took the exam the day before PuppetConf.</description>
    </item>
    
    <item>
      <title>puppetconf 2012</title>
      <link>https://geek.jasonhancock.com/2012/09/28/puppetconf-2012/</link>
      <pubDate>Sat, 29 Sep 2012 01:05:26 +0000</pubDate>
      
      <guid>https://geek.jasonhancock.com/2012/09/28/puppetconf-2012/</guid>
      <description>I&amp;rsquo;ve been at PuppetConf for the last couple of days. As usual, it has been an amazing experience and worth the price of admission.
After seeing the presentations, I have a few things I&amp;rsquo;d like to explore when I get back to the office next week:
 Puppet 3.0 has been released (to the dev repos- hits prod repos on Monday apparently). Logstash rspec-puppet I want to get reinvigorated about the cloud Random tools  Puppet3.</description>
    </item>
    
    <item>
      <title>the puppet inventory service from php</title>
      <link>https://geek.jasonhancock.com/2012/09/12/the-puppet-inventory-service-from-php/</link>
      <pubDate>Wed, 12 Sep 2012 18:14:43 +0000</pubDate>
      
      <guid>https://geek.jasonhancock.com/2012/09/12/the-puppet-inventory-service-from-php/</guid>
      <description>Let&amp;rsquo;s say you wanted to tie into Puppet&amp;rsquo;s inventory service from a PHP app.
I wanted to do just that, so I started googling around to see if someone already done it. I found an Ubersmith plugin that had some code and a great writeup on generating the certificate, which I&amp;rsquo;ll paraphrase here.
To generate a certificate called somecert on your puppetmaster, run this:
puppet cert generate somecert cat /var/lib/puppet/ssl/private_keys/somecert.pem /var/lib/puppet/ssl/certs/somecert.</description>
    </item>
    
    <item>
      <title>puppet apache log analysis</title>
      <link>https://geek.jasonhancock.com/2012/08/23/puppet-apache-log-analysis/</link>
      <pubDate>Thu, 23 Aug 2012 18:18:54 +0000</pubDate>
      
      <guid>https://geek.jasonhancock.com/2012/08/23/puppet-apache-log-analysis/</guid>
      <description>Inspired by this post from Oliver Hookins, I modified my puppetmaster&amp;rsquo;s apache configuration as described in the post (added the %D). Once I had some logs, I needed to parse them, but the script that Oliver wrote hasn&amp;rsquo;t been released. It isn&amp;rsquo;t pretty, but I threw together a quick perl script to get the job done. You can find it here.</description>
    </item>
    
    <item>
      <title>Deploying Tasseo not to Heroku</title>
      <link>https://geek.jasonhancock.com/2012/08/02/deploying-tasseo-not-to-heroku/</link>
      <pubDate>Thu, 02 Aug 2012 22:56:38 +0000</pubDate>
      
      <guid>https://geek.jasonhancock.com/2012/08/02/deploying-tasseo-not-to-heroku/</guid>
      <description>I&amp;rsquo;m new to Graphite. From all the buzz on twitter and what I&amp;rsquo;ve gotten my hands on so far, it&amp;rsquo;s pretty cool. One of the problems (or features) is that Graphite has a great api, so quite a few third-party dashboards have popped up. Tasseo is one such dashboard. I like it for it&amp;rsquo;s minimalistic appearance that packs in just enough data to give you everything you need to know in a quick glance.</description>
    </item>
    
    <item>
      <title>puppetdb</title>
      <link>https://geek.jasonhancock.com/2012/05/23/puppetdb/</link>
      <pubDate>Wed, 23 May 2012 16:44:04 +0000</pubDate>
      
      <guid>https://geek.jasonhancock.com/2012/05/23/puppetdb/</guid>
      <description>Puppetlabs released PuppetDB last Friday. It&amp;rsquo;s a drop-in replacement for the existing stored configurations backends and the inventory service. Stored configurations have always been a performance bottleneck in my puppet installations, so I was eager to try it out.
I had it up and running, completely puppetized within a couple of hours. This was mainly due to my unfamiliarity with Postgres and having to repurpose some of the existing postgres modules on the forge to suit my needs.</description>
    </item>
    
    <item>
      <title>puppet camp los angeles 2012</title>
      <link>https://geek.jasonhancock.com/2012/05/03/puppet-camp-los-angeles-2012/</link>
      <pubDate>Thu, 03 May 2012 15:26:40 +0000</pubDate>
      
      <guid>https://geek.jasonhancock.com/2012/05/03/puppet-camp-los-angeles-2012/</guid>
      <description>Puppet Camp LA 2012 is being held on May 19th and hosted by Media Temple in Culver City. I&amp;rsquo;m excited to be a speaker this year. I&amp;rsquo;ll be talking about running Puppet on CloudStack instances and automating other parts of your infrastructure. Although the details will be focused on what it takes to run Puppet specifically on CloudStack instances, the methodology I will be presenting translates to other clouds and bare-metal infrastructure.</description>
    </item>
    
    <item>
      <title>puppet svn pre-commit hook</title>
      <link>https://geek.jasonhancock.com/2012/04/18/puppet-svn-pre-commit-hook/</link>
      <pubDate>Thu, 19 Apr 2012 05:13:57 +0000</pubDate>
      
      <guid>https://geek.jasonhancock.com/2012/04/18/puppet-svn-pre-commit-hook/</guid>
      <description>I wanted a subversion pre-commit hook script that did the following:
 Ensures all *.pp files in the transaction can be validated by the parser Ensures all *.pp files pass a puppet-lint check Ensures all *.erb files pass a syntax check  I poked around a bit, but it looks like most of the existing pre-commit hook scripts were a bit out of date (wouldn&amp;rsquo;t work on puppet &amp;gt;= 2.7). Also, I didn&amp;rsquo;t see a script that also ran puppet-lint.</description>
    </item>
    
    <item>
      <title>Running Puppet on CloudStack Instances</title>
      <link>https://geek.jasonhancock.com/2012/02/08/running-puppet-on-cloudstack-instances/</link>
      <pubDate>Thu, 09 Feb 2012 04:36:41 +0000</pubDate>
      
      <guid>https://geek.jasonhancock.com/2012/02/08/running-puppet-on-cloudstack-instances/</guid>
      <description>When we were building our CloudStack environment we wanted newly created instances to check into the puppetmaster and receive their configurations automatically. The goals for accomplishing this were:
 No human intervention Do not have to update a separate asset database/spreadsheet/text file/etc. Do NOT use Puppet&amp;rsquo;s auto-signing feature Instances receive all config via Puppet, thus minimizing the number of CloudStack templates we have to maintain by only having to keep base/minimal images for each OS that we are supporting (One el5 image, one el6 image, etc.</description>
    </item>
    
    <item>
      <title>Removing Destroyed CloudStack Instances From Puppet Stored Configurations DB</title>
      <link>https://geek.jasonhancock.com/2012/02/06/removing-destroyed-cloudstack-instances-from-puppet-stored-configurations-db/</link>
      <pubDate>Mon, 06 Feb 2012 19:09:52 +0000</pubDate>
      
      <guid>https://geek.jasonhancock.com/2012/02/06/removing-destroyed-cloudstack-instances-from-puppet-stored-configurations-db/</guid>
      <description>If you&amp;rsquo;re using Puppet, and using Puppet to automatically generate configurations for other parts of your infrastructure by using stored configurations, then one thing you have to do is clean up the stored configurations database once you have destroyed a node, otherwise whatever stored config you created will continue to persist despite you removing that node.
Luckily for us, the folks at PuppetLabs ship a script that we can use to clean up after a node.</description>
    </item>
    
  </channel>
</rss>