puppet apply #5 – roles and profiles

what are roles and profiles? Roles and profiles are the recommended way from Puppet to organise code. Documentation elsewhere on this includes: https://puppet.com/docs/pe/2017.2/r_n_p_full_example.html Summary: Each node / server / puppet agent has a single role. Webserver, database server, jenkins server, blog-webserver, customer-databaseserver, and so on.  Whatever makes sense in your environment. Profiles provide useful functionality […]

puppet apply #4 – a profile

Putting all our code in site.pp isn’t very scalable. We want to follow Puppet best practise and use roles and profiles, so: cd control-repo # I’m going to assume this from now on git checkout puppetapply02 If you look at manifests/site.pp, there’s an include statement. This is the basis of how node classification is generally done. […]

puppet apply #3 – control repo entry point

Puppet apply and the puppet master need to start somewhere when compiling a puppet catalog. When control repo is used by the puppet master, the manifests/ directory is this start;  or entry point. Puppet apply needs to be told what to run; point it at a directory with puppet manifests in them, and it’ll process […]

puppet agent, centos 7 and raspberry pi

There’s no armv7l packages of the puppet agent, so I need to run it from source. The docs for doing this date back to 3.8. Also helped by this post by Brandon Martin. I’ll be looking to run the following client version to match my PE install. # puppet –version 4.10.12 Pre-requisites Applicable requirements come […]