PuppetConf DevDay 2013 Cut-sheet

centos_6_vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

# For the most part, this is a stock config from `vagrant init`

Vagrant.configure("2") do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "centos-64-x64-novm"
 
  config.vm.provision :shell, :path => "puppet-bootstrap.sh"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.
  # More boxes can be found here: http://puppet-vagrant-boxes.puppetlabs.com/

  # config.vm.box_url = "http://puppet-vagrant-boxes.s3.amazonaws.com/debian-70rc1-x64-vf503.box"

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # config.vm.network :forwarded_port, guest: 80, host: 8080

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network :private_network, ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network :public_network

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider :virtualbox do |vb|
  #   # Don't boot with headless mode
  #   vb.gui = true
  #
  #   # Use VBoxManage to customize the VM. For example to change memory:
  #   vb.customize ["modifyvm", :id, "--memory", "1024"]
  # end
  #
  # View the documentation for the provider you're using for more
  # information on available options.

  # Enable provisioning with Puppet stand alone.  Puppet manifests
  # are contained in a directory path relative to this Vagrantfile.
  # You will need to create the manifests directory and a manifest in
  # the file base.pp in the manifests_path directory.
  #
  # An example Puppet manifest to provision the message of the day:
  #
  # # group { "puppet":
  # #   ensure => "present",
  # # }
  # #
  # # File { owner => 0, group => 0, mode => 0644 }
  # #
  # # file { '/etc/motd':
  # #   content => "Welcome to your Vagrant-built virtual machine!
  # #               Managed by Puppet.\n"
  # # }
  #
  # config.vm.provision :puppet do |puppet|
  #   puppet.manifests_path = "manifests"
  #   puppet.manifest_file  = "init.pp"
  # end

  # Enable provisioning with chef solo, specifying a cookbooks path, roles
  # path, and data_bags path (all relative to this Vagrantfile), and adding
  # some recipes and/or roles.
  #
  # config.vm.provision :chef_solo do |chef|
  #   chef.cookbooks_path = "../my-recipes/cookbooks"
  #   chef.roles_path = "../my-recipes/roles"
  #   chef.data_bags_path = "../my-recipes/data_bags"
  #   chef.add_recipe "mysql"
  #   chef.add_role "web"
  #
  #   # You may also specify custom JSON attributes:
  #   chef.json = { :mysql_password => "foo" }
  # end

  # Enable provisioning with chef server, specifying the chef server URL,
  # and the path to the validation key (relative to this Vagrantfile).
  #
  # The Opscode Platform uses HTTPS. Substitute your organization for
  # ORGNAME in the URL and validation key.
  #
  # If you have your own Chef Server, use the appropriate URL, which may be
  # HTTP instead of HTTPS depending on your configuration. Also change the
  # validation key to validation.pem.
  #
  # config.vm.provision :chef_client do |chef|
  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
  #   chef.validation_key_path = "ORGNAME-validator.pem"
  # end
  #
  # If you're using the Opscode platform, your validator client is
  # ORGNAME-validator, replacing ORGNAME with your organization name.
  #
  # If you have your own Chef Server, the default validation client name is
  # chef-validator, unless you changed the configuration.
  #
  #   chef.validation_client_name = "ORGNAME-validator"
end

change_puppet_versions.sh

# Once you have your vagrant virtual machine running, with Puppet installed, you can use these commands to change your Puppet version. 

# Examples with Yum: (or use install/upgrade verbs)
yum downgrade puppet-2.6.18-1.el6
yum downgrade puppet-2.7.23-1.el6
yum downgrade puppet-3.0.0-1.el6

# Examples with Apt:
apt-get install puppet=2.6.18-1puppetlabs1 puppet-common=2.6.18-1puppetlabs1
apt-get install puppet=2.7.23-1puppetlabs1 puppet-common=2.7.23-1puppetlabs1
apt-get install puppet=3.2.4-1puppetlabs1 puppet-common=3.2.4-1puppetlabs1

editors.txt

If you're interested in Geppetto, you can download it here: http://cloudsmith.github.io/geppetto/download.html

Vim Plugins Worth Noting
---
vim-pathogen (for plugins)
snipmate (like TextMate)
tabular
syntastic
mv-vim-puppet

links.txt

http://www.vagrantup.com/
http://puppet-vagrant-boxes.puppetlabs.com/

ex. vagrant box add centos-64-x64-4210-nocm http://puppet-vagrant-boxes.puppetlabs.com/centos-64-x64-vbox4210-nocm.box

# For bootstrap, place the relevant script into your Vagrant folder:
https://github.com/hashicorp/puppet-bootstrap

using_inifile.pp

# you can use puppetlabs/inifile to set your modulepath in puppet.conf to include the shared folder from Vagrant.

# First, install the module on your VM
puppet module install puppetlabs/inifile

# Then, create this manifest somewhere in that VM
#ex: puppet_conf.pp
ini_setting { 'my modulepath':
  ensure  => present,
  path    => '/etc/puppet/puppet.conf',
  section => 'main',
  setting => 'modulepath',
  value   => '/etc/puppet/modules:/usr/share/puppet/modules:/vagrant',
}

# Finally, run Puppet Apply with that manifest to apply it.
puppet apply puppet_conf.pp

I would suggest using vundle (https://github.com/gmarik/vundle) over pathogen for managing your plugins. It's a little more modern, easier to manage.

Awesome, thank you!