Guide to building Puppet agents.

Since any reasonable modern OS have puppet in the standard repositories, why do we build the puppet software ourselves?

There are several reasons for this:

• Ruby depends on dynamically loaded libraries, for example zlib and openssl. By including these into the EIS puppet package we eliminate the risk of an OS patch to break puppet

• Some OSes in EIS scope does not provide puppet at all, or an older version. We can build EIS puppet for these

• We get the same version of puppet on all EIS managed servers, implying that we can use the same puppet language features for all clients

• The EIS puppet package installs in /opt/puppet, thus it is possible to have the OS puppet package installed simultaneously

• A tailor-made package fits our requirements better

• RedHat 5 x86_64, i386
• RedHat 6 x86_64, i386
• Solaris 9 sparc
• Solaris 10 x86_64, sparc
• Solaris 11.1 x86_64, sparc
• Suse 9 x86_64, i386 (Uses RedHat 5 packages)
• Suse 10 x86_64, i386 (Uses RedHat 5 packages)
• Suse 11 x86_64, i386 (Uses RedHat 6 packages)
• Ubuntu 12.04 LTS x86_64

facter-1.7.1
hiera-1.2.1
puppet-3.2.2
ruby-1.8.7-p358
ruby-shadow-2.1.4
augeas-1.1.0
ruby-augeas-0.5.0
readline-6.2
openssl-0.9.8w
zlib-1.2.8

The following components are used.

• C compiler, usually gcc
• make and gmake
• perl
• fpm
• rpmbuild

/usr/sfw/bin/gcc 3.4.3, patched with https://www.openssl.org/~appro/values.c to get usable openssl libs

/usr/sfw/bin/gcc 3.4.3

build.pl will auto detect the system that you are on and build for it.

./bin/build.pl

./bin/build.pl -wrap no

This would build only zlib and openssl. Notice the names match the variables from settings.pl

./bin/build.pl -packages zlib128,openssl101e

./bin/build.pl -dump

scripts

main script that you run

Default settings

Settings specific to that platform

Directory where builds take place. Ignored by git

Logs to both of these files.

logs/build.$hostname-<pid>
logs/latest

Packages are extracted and built here, under <package_name>/

Packages are downloaded here.

Where built packages end up.

Patches to source code

Solaris builds its own packages without FPM

Everything else, uses FPM.

• build.pl builds everything in /opt/puppet
• copies /opt/puppet to fpmtop/
• copies fpmtop/init.d to fpmtop/etc/init.d
• produces package

Setup build environment.

yum -y install rpm rpm-devel rpm-build gcc gcc-c++ automake autoconf libtool rubygems
gem install -V fpm --no-ri --no-rdoc