This class covers advanced skills for professionals who want to extend the capabilities of the Puppet IT automation solution using Ruby development. (Replaces the former Puppet Developer course.)

Prerequisites:

To complete the course successfully, attendees need to have at least the equivalent Puppet knowledge of the Puppet 100 – Puppet Fundamentals course (completion of Puppet Fundamentals before attending this course is highly recommended).

Topics covered include:

• Understanding Fundamental Aspects of Extending the Puppet Framework
• Custom Resource Type and Provider development
• Advanced Custom Facts, Functions, Reports
• Unit Spec Tests for Ruby & Puppet
• Principles and best practices of extending Puppet
• Students who wish to extend their Puppet solution, but are not yet familiar with the Ruby programming language, can register to attend a free 1-day primer (first day of class) covering the elements of Ruby for Puppet: Introduction & Advanced Programming Topics.

The topics are covered over 3 days + day 1 optional for Ruby primer. Sessions will mix theory and practice, balancing 30% lecture with 70% hands-on exercises. (In order to perform the hands-on exercises, each student needs to bring a WiFi enabled laptop with VMware installed to participate in the labs.)

Pricing

• $2,995 USD by Aug 25, 2012; $3,195.00 USD on or after Aug 26, 2012.

Following on from Adrien’s wonderful post on syntax checking and writing tests, you have a way of checking the syntax and style guide from the command line. Using this approach, even on a mature (like a fine wine) Puppet code base, you can move towards having beautiful, aligned, ordered manifests—the type of manifests you’d be happy taking home to meet the family.

Puppet-lint takes the Puppet Labs Style Guide and places it nicely in a command line tool. Think of it as a programmatic PEP-8 for those from a Pythonic world. Now, where this comes in handy is when you’re using revision control (which is all the time, obviously!), because you can tie the two together. Yes, every time you try and commit your code to your RCS, it checks the files you’re committing, and makes sure you haven’t used a tab where there should be a space.

In Puppet Labs’ kickass Operations department, we’re ever so slightly keen on Git, not least due to the wonderful GitHub. RCSHub just doesn’t cut it for us these days.

With Git, as with many an RCS, you’re free to define hooks to do weird and wondrous things upon certain actions. This chapter on git hooks from Customizing Git explains them in detail. If you’re using Subversion, then this pre-commit documentation suggests what you can do on the server side to accomplish the same thing.

For this, the pre-commit hook is the one we want to utilise. I first make a bash script to get a list of the files that change in the commit. Then, the hook script goes through them one at a time, seeing if they’re Puppet manifests by name, and running puppet-lint on them as it goes. If any of the manifests fail linting, it exits there and then I may go fix them at my leisure!

#!/bin/bash
# Requires bash, as it uses the [[ ]] syntax.
#
# If it's puppet code, lint it up.
 
# I we don't have puppet-lint, so just exit and leave them be.
which puppet-lint >/dev/null 2>&1 || exit
 
# Variables goes hither
declare -a FILES
IFS="
"
FILES=$(git diff --cached --name-only --diff-filter=ACM )
 
for file in ${FILES[@]}
do
  if [[ $file =~ \.*.pp\$ ]]
  then
    puppet-lint --with-filename "$file"
    RC=$?
    if [ $RC -ne 0 ]
    then
      exit $RC
    fi
  fi
done
 
exit 0

I save that file to .git/hooks/pre-commit in my repository, give it a light sprinkling of ‘chmod +x’, a dash of ‘gem install puppet-lint’ and I am ready to roll.

Exhibit A, the Larch

So let’s see this bad-boy in use, I hear you cry! Let’s take a manifest that breaks all of the rules, and see what happens…

node 'hubert.humphrey.edu' {
 
	user{ "mhunter":
	   managehome => true,
	   home => "/home/mhunter",
	   comment => 'Mark Hunter',
	   ensure => 'present'
   }
 
}

[enlil:puppetlabs-modules]% git commit hubert.pp
hubert.pp - WARNING: double quoted string containing no variables on line 3
hubert.pp - WARNING: double quoted string containing no variables on line 5
hubert.pp - WARNING: => on line isn't properly aligned for resource on line 5
hubert.pp - WARNING: => on line isn't properly aligned for resource on line 6
hubert.pp - WARNING: => on line isn't properly aligned for resource on line 7
hubert.pp - ERROR: two-space soft tabs not used on line 4
hubert.pp - ERROR: two-space soft tabs not used on line 5
hubert.pp - ERROR: two-space soft tabs not used on line 6
hubert.pp - ERROR: two-space soft tabs not used on line 7
hubert.pp - ERROR: two-space soft tabs not used on line 8
hubert.pp - ERROR: trailing whitespace found on line 2
hubert.pp - WARNING: ensure found on line but it's not the first attribute on line 7

Woah, that’s a lot of errors. By default, puppet-lint will let warnings through, but stop dead on errors, and we got them all! I’ll tidy this manifest up…

node 'hubert.humphrey.edu' {
 
  user{ 'mhunter':
    ensure     => present,
    managehome => true,
    home       => '/home/mhunter',
    comment    => 'Mark Hunter',
  }
 
}

Much more readable, and now when I try and commit it, I get:

[enlil:puppetlabs-modules]% git commit hubert.pp
[master 6020331] Add in a new pupil to the school!
 1 file changed, 10 insertions(+)
 create mode 100644 hubert.pp

Clean, and the best part is I don’t have to alter my workflow, I can just carry on editing with Vim, commit my work as normal, and just be kindly reminded when a manifest has things that need tidying up.

Learn More

• Puppet Labs style guide
• puppet-lint
• Verifying Puppet: Checking Syntax and Writing Automated Tests
• Puppet-lint SubVersion commit hook by Jason Hancock

This training course teaches students a best practice approach to managing their infrastructure using Puppet IT automation software. (Replaces the former Puppet Master course.)

Prerequisites:

This course has no prerequisites, but to complete the course successfully attendees need to have at least the equivalent experience of a junior Unix/Linux administrator.

Topics covered include:

• Developing modules/classes on a system that represent target systems
• Using Puppet Apply to test and iterate modules
• Placing modules on the Puppet Master
• Declaring appropriate classes in node definitions
• Triggering a Puppet run using the Live Management GUI
• Collecting and analyzing results in the Enterprise Console
• Puppet Language Patterns and Best Practices

The topics are covered over 3 days. Sessions will mix theory and practice, balancing 50% lecture with 50% hands-on exercises. (In order to perform the hands-on exercises, each student needs to bring a WiFi enabled laptop with VMware installed to participate in the labs.)

Pricing

• $2,395 USD by Sept 3, 2012; $2,595 USD on or after Sept 4, 2012.

To use the module you need to download it from the Puppet Forge onto your Puppet master using the module tools:

# puppet module install puppetlabs-boundary

You can then use the module to install and manage the Boundary meters that monitor your network traffic and send the results to Boundary.  To create a new meter you will need your Boundary ID and API key and create a `boundary_meter` resource like so:

boundary_meter { "db.example.com":
  ensure => present,
  id => "abcde12345",
  apikey => "abcde12345",
  tags => [ "production", "newyork", "mysql", "appcluster1" ],
}

This resource will create a meter called “db.example.com” and add the tags production, newyork, mysql and appcluster1 (or the tags of your choice).  After you run Puppet you will be able to see your meter in the Boundary console.  We can also easily delete the meter by ensuring it is `absent`.

You can find the source code on GitHub and we welcome bug reports, ideas and features from the Puppet community. Thanks to Joe Williams, Jeff Hulten, W. Andrew Loe III, Alessandro Franceschi and Scott Smith for their contributions to the current module.

This training course teaches students a best practice approach to managing their infrastructure using Puppet IT automation software. (Replaces the former Puppet Master course.)

Prerequisites:

This course has no prerequisites, but to complete the course successfully attendees need to have at least the equivalent experience of a junior Unix/Linux administrator

Topics covered include:

• Developing modules/classes on a system that represent target systems
• Using Puppet Apply to test and iterate modules
• Placing modules on the Puppet Master
• Declaring appropriate classes in node definitions
• Triggering a Puppet run using the Live Management GUI
• Collecting and analyzing results in the Enterprise Console
• Puppet Language Patterns and Best Practices

The topics are covered over 3 days. Sessions will mix theory and practice, balancing lectures with hands-on exercises. (In order to perform the hands-on exercises, each student needs to bring a WiFi enabled laptop with VMware installed to participate in the labs.)

Pricing

• $2,195 by Aug 6, 2012; $2,395 on or after Aug 7, 2012.

This training course teaches students a best practice approach to managing their infrastructure using Puppet IT automation software. (Replaces the former Puppet Master course.)

Prerequisites:

This course has no prerequisites, but to complete the course successfully attendees need to have at least the equivalent experience of a junior Unix/Linux administrator.

Topics covered include:

• Developing modules/classes on a system that represent target systems
• Using Puppet Apply to test and iterate modules
• Placing modules on the Puppet Master
• Declaring appropriate classes in node definitions
• Triggering a Puppet run using the Live Management GUI
• Collecting and analyzing results in the Enterprise Console
• Puppet Language Patterns and Best Practices

The topics are covered over 3 days. Sessions will mix theory and practice, balancing lectures with hands-on exercises. (In order to perform the hands-on exercises, each student needs to bring a WiFi enabled laptop with VMware installed to participate in the labs.)

Pricing

• $2,195 by July 23, 2012; $2,395 on or after July 24, 2012.

This training course teaches students a best practice approach to managing their infrastructure using Puppet IT automation software. (Replaces the former Puppet Master course.)

Prerequisites:

This course has no prerequisites, but to complete the course successfully attendees need to have at least the equivalent experience of a junior Unix/Linux administrator.

Topics covered include:

• Developing modules/classes on a system that represent target systems
• Using Puppet Apply to test and iterate modules
• Placing modules on the Puppet Master
• Declaring appropriate classes in node definitions
• Triggering a Puppet run using the Live Management GUI
• Collecting and analyzing results in the Enterprise Console
• Puppet Language Patterns and Best Practices

The topics are covered over 3 days. Sessions will mix theory and practice, balancing lectures with hands-on exercises. (In order to perform the hands-on exercises, each student needs to bring a WiFi enabled laptop with VMware installed to participate in the labs.)

Pricing

• $2,195 by July 16, 2012; $2,395 on or after July 17, 2012.

The major areas of advance are below:

• Complete messaging protocol rewrite to enable direct style connectivity that would allow programs to bypass normal discovery instead using their own data sources
• An additional more robust messaging paradigm supporting a more assured addressing and delivery scheme
• Batched mode allowing users to address machines in small groups thus avoiding thundering herd and enabling more granular changes
• A more complete language for expressing discovery that includes and/or/not style queries across the infrastructure
• Improved Stomp connection security using normal industry standard Certificate Authority validated TLS
• New connector that uses ActiveMQ-specific features for better performance and scalability
• Security of the SSL and AES security plugins have been improved for tamper protection by middle men
• A message validity period has been introduced to lower the window of message replay attacks
• Better error handling and better logging for Stomp connections
• JSON output from the ‘rpc’ application
• Ability to pipe RPC requests into each other creating a chain of related RPC calls
• Better validations, better error handling and better documentation creation from the DDL
• Performance improvements in the CLI, more consistently formatted output of received data
• A Ruby GEM of the client is now made available on rubygems.org
• The rc script for Debian based systems have been improved to prevent duplicate daemons from running
• Built in packager for plugins into native OS packages—RedHat and Debian supported
• MS Windows Support

The full release notes for this release expands on key areas of the above list and you can download this release from our download area, Yum repository or our Apt repository.

This training is ideal for those who want a Puppet jumpstart. Newer members at an organization already using Puppet, or experienced sysadmins wanting to bring Puppet into their team will get everything they need to deploy solutions.

Prerequisites:

Attendees should have at least the equivalent experience of a junior Unix/Linux administrator.

Topics covered include:

• Architecture & Installation
• Configuring Puppet and Puppetmaster
• Resource Types and the Resource Abstration Layer
• Virtual Resources, Exported Resources and Stored Configs
• Meta-parameters, Dependencies and Events
• Classes, Modules and Definitions
• Tags and Environments
• Puppet Language Patterns and Best Practices

The topics are covered over 3 days. Sessions will mix theory and practice, balancing lectures with hands-on exercises. (In order to perform the hands-on exercises, each student needs to bring a WiFi enabled laptop with VMware installed to participate in the labs.)

Pricing

• EUR 1980 (+VAT).
• Lodging assistance is available – http://www.heinlein-support.de/schulung/puppet?ref=ebtn.

May 19 – Puppet Camp Los Angeles: Senior Developer Deepak Giridharagopal will introduce PuppetDB, and the Puppet projects team lead Daniel Pittman will share the Puppet roadmap for 2012.

May 21 – Find us at EMC world, we’ll be around and looking to find you. Follow us @puppetlabs to find out where we are.

We’ve announced new Puppet Camps for June and July:

• Southeast Asia in Kuala Lumpur on June 5th
• Sydney on June 8th (tickets are almost gone!)
• District of Columbia on June 19th
• Puppet Camp Boston on June 22
• Chicago on July 23rd

And don’t forget about our previously announced our European camps in Dublin, Ireland on July 6th and Geneva, Switzerland on July 11th.

After the end of July we’ll be working to produce an epic PuppetConf in San Francisco on September 27th and 28th. Register now to guarantee a seat. Like many of our Puppet Camps, PuppetConf is sure to sell out.

We’re also happy to offer you a 10% discount to Velocity on June 25-28. Just use code PUPPETLABS when you register and then come find us at booth #517 and check out presentations from James Turnbull and Luke Kanies at Velocity.



We’re looking forward to connecting with you this summer.

]]> http://puppetlabs.com/blog/upcoming-puppet-events-new-camps-puppetconf-and-velocity/feed/ 0