Our application will be simple, as its goal is only to demonstrate a daemon that needs to be managed via init.d and packaged as an RPM.
Complete Continuous Deployment Using Puppet and Pulp - Part 1 - the Machines
You’re going to need a minimum of 4 servers. Before you freak out, that’s to keep things simple. Again, calm down. Also, you’ll see I like CentOS. All the servers I built were CentOS 6.5 x86_64
Complete Continuous Deployment Using Puppet and Pulp - Overview
This will be by far my biggest post to date. I’ve been asked from multiple sources about the system I’ve set up at my current company, so this is a very small version of it. By the end of this, assuming you follow along, you’ll have a multiple node system set up that will deploy a linux service, packaged as an RPM, to internal Yum feeds, with Puppet along the way to keep this continuously deployed. The puppet module I’ll write to do this will also be continuous, with all changes to it causing tests to run, and r10k to redeploy them if successful.
UDOO and an Arduino LCD
I have continued to want more out of my UDOO, so I decided to make use of a cracked LCD I had sitting around from Adafruit, by having the UDOO display system information to it.
UDOO and SATA - the Definitive Guide
I’ve recently purchase a udoo. I am in love with it, however I had issues trying to boot from SATA.
Puppet and MarkLogic
I’ve recently been writing a few modules for my current job, and have seen some missing modules on the puppetforge. One of which is something to maintain a MarkLogic instance.