The Problem Need to deploy a new Puppet Enterprise cluster with a PuppetMaster, PuppetConsole and a PuppetDB while avoiding typos and misconfigurations. Also need to deploy to several environments using a consistent configuration.
The Solution Use Ansible to deploy Puppet onto freshly built servers that contain just a SysAdmins SSH public key.
The Goal A repeatable and documented way to deploy the very finicky Puppet installer in any environment needed from local vagrants to the clouds of vSphere, AWS, RackSpace or Digital Ocean.
The Goal Install Oscar Use Oscar to build a local PuppetMaster & Agent config Use Vagrant to start the PuppetMaster & Agent Install VirtualBox - https://www.virtualbox.org/wiki/Downloads Vagrant - Oscar works with Vagrant version 1.3.4 - http://downloads.vagrantup.com/tags/v1.3.4 Oscar - https://github.com/adrienthebo/oscar sandor@theargo> vagrant plugin install oscar Add a Vagrant Box sandor@theargo> vagrant box add centosPupLabs http://puppet-vagrant-boxes.puppetlabs.com/centos-64-x64-vbox4210-nocm.box What that does:
sandor@theargo> vagrant box add boxName http://url.box Downloads the .
The Goal Setup vim to edit Puppet Manifests using a few good tools that will get you to pass Puppet Lint tests.
The Links PuppetLabs - link
vim-puppet - link
vim tabular - link
vim syntastic - link
Vim-Pathogen Vim-Pathogen on github
sandor@theargo mkdir -p ~/.vim/autoload ~/.vim/bundle sandor@theargo cd ~/.vim/autoload sandor@theargo curl -o pathogen.vim https://raw.github.com/tpope/vim-pathogen/master/autoload/pathogen.vim Add these settings to .vimrc