bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Servers & Workflows/Linux/Automation/Puppet/Puppet Deployment.md

Browse Source
This commit is contained in:
Nicole Rappe
2024-10-03 21:15:06 -06:00
parent ff87a59438
commit 4218e2fff3
1 changed files with 0 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
Servers & Workflows/Linux/Automation/Puppet/Puppet Deployment.md
View File

@ -56,34 +56,6 @@ At this point, you want to ensure that the device being managed by the agent is
``` sh
puppet agent --test
```
??? Legacy PuppetDB Deployment (Not Recommended)
### Install PuppetDB
At this point, we will install PuppetDB, which will add extra reporting and management functionality for Puppet to the Puppet server.
``` sh
# Install PuppetDB
yum install -y puppetdb
# Install PuppetDB Module
puppet module install puppetlabs-puppetdb
```
Now we need to configure a manifest file on the Puppet Server running PuppetDB, in this case, the same exact server that runs the Puppet Server itself. Create the following file if it does not already exist:
```json title="/etc/puppetlabs/code/environments/production/manifests/site.pp"
node 'lab-puppet-01.bunny-lab.io' {
# Include the puppetdb class with custom parameters
class { 'puppetdb':
listen_address => '0.0.0.0', # Allows access from all network interfaces
}
# Configure the Puppet Server to use PuppetDB
include puppetdb::master::config
}
```
Finally, we want to apply the configuration changes we made:
``` sh
sudo puppet agent -t
```
## Install r10k
At this point, we need to configure Gitea as the storage repository for the Puppet "Environments" (e.g. `Production` and `Development`). We can do this by leveraging a tool called "r10k" which pulls a Git repository and configures it as the environment in Puppet.