DeskTux

Linux on Desktops

User Tools

Site Tools


apps:puppet

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
apps:puppet [2019-08-10 20:21]
jens Adding git section
apps:puppet [2019-08-31 17:59] (current)
jens Fixing messed up headers
Line 1: Line 1:
 ====== Puppet ====== ====== Puppet ======
-Even if you manage just a handful or two servers, [[https://puppet.com/|Puppet]] can already help you to save loads of time and ensures all your systems run in the desired state.+Even if you manage just a handful or two of servers, [[https://puppet.com/|Puppet]] can already help you to save loads of time and ensures all your systems run in the desired state.
  
 Somehow, I could not find very many or good manuals on how to set up your own (basic) Puppet server on Debian, so I decided to write my own. Somehow, I could not find very many or good manuals on how to set up your own (basic) Puppet server on Debian, so I decided to write my own.
  
-==== Installation & Configuration ====+===== Installation & Configuration =====
 The installation in Debian (10 or later) is -- as always in Debian -- straight forward. Just run an The installation in Debian (10 or later) is -- as always in Debian -- straight forward. Just run an
  
   apt install puppet puppet-master vim-puppet   apt install puppet puppet-master vim-puppet
      
-That last package is not really needed but comes in really handy when editing your Puppet manifests in vim and you want syntax highlighting. While this would be more needed on a [[git]] client it also is nice to have on the Puppet master.+That last package is not really needed but comes in really handy when editing your Puppet manifests in vim and you want syntax highlighting. While this would be more needed on a [[:apps:git|git]] client it also is nice to have on the Puppet master.
  
 As for the main configuration file ''/etc/puppet/puppet.conf'' I leave the Debian standard for what it is. As for the main configuration file ''/etc/puppet/puppet.conf'' I leave the Debian standard for what it is.
  
-==== Manifests ====+===== Manifests =====
 Your manifests should be in ''/etc/puppet/code/'' and the basic structure looks like this: Your manifests should be in ''/etc/puppet/code/'' and the basic structure looks like this:
  
Line 28: Line 28:
                 ├── module2                 ├── module2
                 │   ├── examples                 │   ├── examples
-                │   ├── manifests +                │   ├── files 
-                │   └── files+                │   └── manifests
                 └── moduleX                 └── moduleX
                     ├── examples                     ├── examples
Line 53: Line 53:
 That way, you can easily test the code of that module by using ''puppet apply -t init.pp''. That way, you can easily test the code of that module by using ''puppet apply -t init.pp''.
  
-Of course, before testing your code, you should first run it through ''puppet parser validate'' and ''puppet-lint''. However, this is not a Puppet code manual, you should check their [[https://puppet.com/docs/puppet/6.7/puppet_index.html|excellent documentation]] for that.+Of course, before testing your code, you should first run it through ''puppet parser validate'' and ''puppet-lint''. However, this is not a Puppet code manual, you should check their [[https://puppet.com/docs|excellent documentation]] for that.
  
-==== Connecting Clients ====+===== Connecting Clients =====
 Of course, your Puppet master will be useless if it only manages itself. To connect clients to your Puppet master, make sure it is reachable on port 8140/TCP (both IPv4 and IPv6 work). Of course, your Puppet master will be useless if it only manages itself. To connect clients to your Puppet master, make sure it is reachable on port 8140/TCP (both IPv4 and IPv6 work).
  
Line 74: Line 74:
 To accept that certificate just run ''puppet cert sign client.system.tld'' and you are good to go. From now on, that system will be managed by your Puppet master. To test this you can run a ''puppet agent -t'' on the client. To accept that certificate just run ''puppet cert sign client.system.tld'' and you are good to go. From now on, that system will be managed by your Puppet master. To test this you can run a ''puppet agent -t'' on the client.
  
-=== Removing clients ===+==== Removing clients ====
 In case you need to remove (decommission) a client, you can list all available certificates with ''puppet cert list -a'' and then ''puppet cert clean <client.name.tld>''. Don't forget to remove that client from backup and monitoring ;-) In case you need to remove (decommission) a client, you can list all available certificates with ''puppet cert list -a'' and then ''puppet cert clean <client.name.tld>''. Don't forget to remove that client from backup and monitoring ;-)
  
-===== And now? ===== +====== What next====== 
-Now, it might be a good idea to manage your Puppet code from your workstation using [[git]]. That way you do not need to log in to the Puppet master all the time to make changes to your code as root.+Now, it might be a good idea to manage your Puppet code from your workstation using [[:apps:git|git]]. That way you do not need to log in to the Puppet master all the time to make changes to your code as root.
apps/puppet.1565461291.txt.gz · Last modified: 2019-08-10 20:21 by jens