control-repo-template/hieradata, branch 1.1.0-lndepuppetlabs/control-repo extended with not-so-core stuffhttps://git.pfeiffer.tech/control-repo-template/atom?h=1.1.0-lnde2017-11-15T17:24:40ZEnable Hiera 52017-11-15T17:24:40ZReid Vandewielereid@puppetlabs.com2017-11-15T17:24:40Zurn:sha1:7264b63d10ca828aff611d94aa730cc5451a7a5c
This commit enables the control repo to use Hiera 5 environment-level
hiera hierarchy. This means adding a hiera.yaml to the repo, and moving
hieradata/ => data/.
We should do this to the control-repo template new customers base off of
because in a Hiera 5 world, the global hiera.yaml should be very minimal
(possibly even ONLY having the console level), and everything else
(nodes, common) belongs in the environment hiera.yaml.
This control-repo template is how people start using Puppet. It should
reflect using our most modern technologies.
Remove max_requests_per_instance since hiera-eyaml is fixed2016-08-04T22:51:07ZNick Walkernick.walker@puppetlabs.com2016-08-04T22:51:07Zurn:sha1:5497d199b3c851a317638905e77f44f2fafc64d4
Prior to this commit, we mitigated issues with hiera-eyaml causing
a memory leak by setting max_requets_per_instance to 0
After this commit, we go back to the default for
max_requests_per_instance because the hiera-eyaml memory leak
has been resolved for months if you use the newest version
Reduce the scope of the control-repo to mostly an example2016-03-29T22:53:10ZNick Walkernick.walker@puppetlabs.com2016-03-23T17:31:33Zurn:sha1:2c98a9264c2070281dc7628d5bcb176eb0fdb200
Prior to this commit, the control-repo was an example of the
structure of a control repo but it also included puppet code to
help setup code manager and instructions to get that all setup
in a very specific way.
This was great for users that wanted to follow those instructions
exactly but wasn't great for people just looking for an example to
start from.
After this commit, the control-repo will be just an example once
again and a new repo somehwere else will pop up to provide the
explicit instructions on how to use the example with code manager.
There are links added to puppetlabs/control-repo to a new repo
that will have a version of the code that once lived in
puppetlabs/control-repo
Disable max-requests-per-instance to mitigate hiera-eyaml mem leak2016-02-24T19:47:27ZNick Walkernick.walker@puppetlabs.com2016-02-24T19:47:27Zurn:sha1:270bf0a53abd2c188916d1684af73c09b6bfcb04
Hiera-eyaml currently causes a memory leak in puppetsever when
max-requests-per-instnace is enabled. So, defaulting to disabling
max-requests-per-instance.
https://tickets.puppetlabs.com/browse/SERVER-1154
https://github.com/TomPoulton/hiera-eyaml/issues/163
Disable code manager webhook authentication2015-12-09T17:44:51ZNick Walkernick.walker@puppetlabs.com2015-11-18T18:15:04Zurn:sha1:947a5529a389a9f8d391fcfaa31db1e64b645705Enable code manager via param in common.yaml2015-11-26T00:06:29ZNick Walkernick.walker@puppetlabs.com2015-11-10T00:21:45Zurn:sha1:8c71bd0b13160f13eeb27613031be167e94f7adechange puppetserver heap to 192m2015-10-29T18:59:19ZNick Walkernick.walker@puppetlabs.com2015-10-29T18:59:19Zurn:sha1:3fcf6e3d5e631491272a39177448c97b431ea477Fix some embarassing typos2015-10-26T22:12:39ZNick Walkernick.walker@puppetlabs.com2015-10-26T22:12:39Zurn:sha1:1cb89d981a7845453529a3a86ac9a9b1254fe61fConfigure the MoM to update the classifier after deploying code2015-10-26T21:59:20ZNick Walkernick.walker@puppetlabs.com2015-10-26T21:59:20Zurn:sha1:92f8d2d251d9e6fde5c124cb9a6974b1455269f7
This entailed configring the classifier to never sync on a
schedule.
Changing environment_timeout to unlimited for all masters.
Setting a postrun command for r10k that would update the class
information in the classifier (the update-classes endpoint).
Change puppetdb heap size to 96MB from 64MB2015-10-16T21:28:17ZNick Walkernick.walker@puppetlabs.com2015-10-16T21:28:17Zurn:sha1:683a2209a66899647860416f7d66d9a6ee9dc24a