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 […]

ELK 6.5 stack on Raspberry Pi / Centos7

Summary The goal was to create a syslog server on a Raspberry Pi, so I can ship all my logs to a low power machine that’ll be on all the time. tl;dr – a bit optimistic. The limited memory would probably require Elasticsearch (ES) and Logstash (LS) on different machines. I think Logstash really wants […]