puppet_puppet.git - [puppet

Age	Commit message (Collapse)	Author
2013-05-20	fix template	mh

2013-05-20	correct naming	mh

2013-05-20	add a simple dashboard setup	mh

2013-05-20	if it runs with passenger there is no such service	mh

2013-05-20	fix inheriting	mh

2013-05-20	update to latest config.ru	mh

2013-04-08	puppet is in bin not sbin	mh

2013-04-07	also use new naming convention on linux	mh

2012-12-07	fix an issue if nothing got compiled	mh

2012-12-07	improve puppet munin plugin	mh

2012-12-07	correct env var	mh

2012-12-06	use correct location to get logs	mh

2012-08-26	improve testing for service	mh

2012-06-18	this has no params	mh

2012-06-18	cleanup param mes	mh

2012-06-17	pass also these params	mh

2012-06-17	correct param naming	mh

2012-06-13	take hiera out of the params	mh

2012-06-10	we support now also 2.7 - 0.24 should not anymore be around	mh

2012-06-10	stop the puppet service by default on cron	mh

2012-06-10	fix cron time	mh

2012-06-10	use another source for the master	mh

2012-06-10	use proper variable name	mh

2012-06-08	new style for 2.7	mh

2011-07-07	linux is the kernel not the operating system	mh

2011-07-07	README typo	mh

2011-07-07	implement setting reports cleanup dir the old way	mh

2011-07-07	Revert "migrate cleanup_reports to parametrized classes as this makes it ↵	mh
	much more configurable" This reverts commit 0f4718f062f7419092f69dcdd951339a466a79b8. Unfortuantely due to puppet bug #5517 we currently can't do it that nice so we need to hack around things https://projects.puppetlabs.com/issues/5517
2011-07-07	Revert "fix variable naming"	mh
	This reverts commit 0fd0df89f4a0bd0700b3260a4c40041c59f65660.
2011-07-07	fix variable naming	mh

2011-07-07	migrate cleanup_reports to parametrized classes as this makes it much more ↵	mh
	configurable
2011-07-07	also don't do anything on undef - maybe once puppet will return undef on ↵	mh
	undefined variables
2011-05-21	Fix development environment's modules path.	intrigeri

2011-05-07	Fix probable typos.	intrigeri

2011-05-07	Merge remote branch 'immerda/master'	intrigeri

2011-05-07	Install puppetmaster-common package.	intrigeri
	This should fix the remaining issues from https://labs.riseup.net/code/issues/2928
2011-05-07	Inherit from the right base class.	intrigeri

2011-04-17	no need to log to the console as we don't use puppets logging feature	mh

2011-04-03	find not search	mh

2011-04-03	fix lastruncheck to be compatible for 2.6.7	mh

2011-03-29	the % needs to be double-escaped so puppet doesn't complain like this:	Micah Anderson
	Mar 29 14:08:23 puppetmaster puppet-master[26637]: Unrecognised escape sequence '\%' in file /etc/puppet/modules/puppet/manifests/cron/linux.pp at line 17
2011-03-28	percent is magic in crontabs and needs to be escaped	Matt Taggart

2011-03-28	need to escape the $ in the variables	Micah Anderson

2011-03-28	add missing redirection to /dev/null for the first puppet restart: #2690	Micah Anderson

2011-03-28	update cronjob to capture the return code output as suggested by LeLutin in ↵	Micah Anderson
	https://labs.riseup.net/code/issues/2819
2011-03-22	fix syntax error from previous commit	Micah Anderson

2011-03-22	add debian-specific puppetmaster require parameter package override	Micah Anderson

2011-03-22	minor formatting fix for standardization	Micah Anderson

2011-03-15	instead of using $RANDOM, which isn't POSIX, we get even more esoteric by ↵	Micah Anderson
	pulling 2 bytes from /dev/urandom, giving them to od which turns them into unsigned decimals, and then we bitshift the output, either by 5 or 6 depending on if we are replacing $RANDOM/100060 (right sift by 5 is the same as dividing by 2^N, or /32) or $RANDOM/200060 (range of [0,983]) Thanks to dkg for working through this with me, not only did he come up with it faster than a human brain should be able to function, he had the patience to explain all the individual pieces that I did not understand to me.
2011-03-15	change the cronjob so that the failure to find any ↵	Micah Anderson
	(^err:\|^alert:\|^emerg:\|^crit:) in the output from the puppet run doesn't leave us with a '1' return code from grep. On Debian Squeeze systems, this problem would result in cron reporting that the cron command failed with an exit status 1: /USR/SBIN/CRON[24107]: (CRON) error (grandchild #24108 failed with exit status 1) This was because grep returns a '1' if it fails to find a match. We don't want the failure to find failure messages to produce a failure, so this checks the return code of the grep and fixes it to be '0' if there were no such failure log messages. This is a bit ugly, if you ask me. We are already, unfortunately, swallowing the puppetd return code with the grep. It seems like these sorts of log messages should be retrieved via reports, logcheck, or something other than this grep of the output of the cronjob.