control-repo/site/role/manifests/all_in_one_pe.pp

class role::all_in_one_pe {

  include profile::puppetmaster
  include profile::git_webhook
  include profile::pe_postgresql_management

}
Update the README, add an all_in_one_pe role Updating README for instructions on how to use the control-repo by putting it in your own git server and then using the r10k answers during installation of PE. Removing the manifest for configuring r10k using zack/r10k. Added a role that can be used to bootstrap an all-in-one PE installation. 2015-08-13 21:10:29 +00:00			`class role::all_in_one_pe {`

Refactor puppetmaster and zack_r10k_webhook Moved the webhook resource out of puppetmaster and into zack_r10k to support exchaning code_manager in place of zack_r10k As a result I cleaned up some unnecessary parameters. Installing both the r10k webhook and the code_manager at this time for testing 2015-11-11 21:43:57 +00:00			`include profile::puppetmaster`
Create profile::git_webhook to abstract away the details Prior to this commit there were two possible webhooks - zack/r10k webhook - code manager I moved these two profiles under git_webhook and choose the correct one based on the version of PE being used. As a safety hatch, I provide the $force_zack_r10k_webhook param on profile::git_webhook in case someone needs to continue using it instead of code manager. 2015-12-21 23:19:38 +00:00			`include profile::git_webhook`
Add autovacuum settings to pe-postgresql In the past I've seen the console and puppetdb databases grow much larger than expected and I have a hypothesis that this is because the default 20% setting for autovacuum is too high for our workload. So, there's a potential that changing this to 1% might be too low and might reduce performance but it should reduce disk usage and it can always be tuned upward if the performance hit is too large, however, it is much more difficult to reduce the size of a database after it has grown too large. Basically, I'm erroring on the side of using less disk space and hopefully less outages due to running out of disk space and we can open a conversation on performance later if one needs to be had. 2015-12-29 22:30:58 +00:00			`include profile::pe_postgresql_management`
Update the README, add an all_in_one_pe role Updating README for instructions on how to use the control-repo by putting it in your own git server and then using the r10k answers during installation of PE. Removing the manifest for configuring r10k using zack/r10k. Added a role that can be used to bootstrap an all-in-one PE installation. 2015-08-13 21:10:29 +00:00
			`}`