This week I had to do a few installations of Puppet Enterprise on an EC2 instance. Although this seemed like a simple enough task, I did hit upon one annoying issue. I was doing a Monolithic installation as it was just for testing, I had done this several times on Digital Ocean external link and locally using a Vagrant box external link with no issue at all. Reading through the documenation I had to open the following...
Around this time last year I blogged about Upgrading my servers to CentOS 7 external link, the post contained a link to a script which I wrote to deploy a Puppet Master & Agent and some updated instructions for installing on RHEL / CentOS 7. As those instructions no longer work, and I needed to install a Puppet Master to have a play with I decided to update the installation script....
Yesterday, I had day out of the office with Danny external link at the 2014 London PuppetCamp external link. It was the first time I had attended a PuppetLabs event, though I have streamed plenty of video from past camps and conferences. It was interesting to see how best practices had moved on (answer, lots) since I first had my Puppet epiphany over a year ago. For me, and in no order, the most interesting talks were …....
==PLEASE NOTE: THESE INSTRUCTIONS ARE NOW OUTDATED, SEE THIS POST FOR AN UPDATE external link== After I dabbled with CentOS 7 external link a few weeks ago I decided to take the plunge and upgrade the few servers I run at DigitalOcean external link to CentOS 7. I run two machines, one is a Puppet and Salt Master, the second runs Docker. Puppet Master Server A while back I added a few bash scripts to deploy both a Puppet Master & Agent external link to GitHub, as Puppet provide a repo for CentOS 7 I decided to just update the installation script to use this repo and then give ago....
I have been playing my Digital Ocean external link server a lot recently. Breaking it, fixing it and then rebuilding it, while I had documented my puppet installation external link it was getting to be a pain to copy and paste with each rebuild, so I pulled together a few scripts external link from various sources to make the rebuilds a little less of a chore. To install fresh Puppet Master all I need to do now is run the following command;...
Vagrant allows developers to bring up local development machines in a controlled method using pre-built configuration files called boxes. Once a box has been installed on the developers local machine it can be powered on with the following command; vagrant up When the box is brought up it automatically provisions itself using a number of provisioners including Puppet, this means that the production deployment scripts can also be run on local development copies of the instances....
This post assumes that you are starting with a clean minimal CentOS 6.4 64bit server and you have a full hostname set. Puppet Server Installation …… # Hostname — Make sure the host name it set to puppet.yourdomain.com and that you replace references in this file # Install puppet & epel repos yum install -y http://yum.puppetlabs.com/el/6/products/i386/puppetlabs-release-6-6.noarch.rpm http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm # Download puppet-server from Puppet Labs, apache and necessary dependencies yum install -y vim-enhanced puppet-server httpd httpd-devel mod_ssl ruby-devel rubygems gcc-c++ curl-devel zlib-devel make automake openssl-devel rubygem-rack rubygem-passenger-native-libs rubygem-passenger-native rubygem-passenger rubygem-fastthread libev mod_passenger git # Start Puppet-Server /etc/init....