leap_platform.git/puppet/modules, branch 0.7.1 [leap_platform] Merge remote-tracking branch 'kwadrolab/static-amber-7231' into develop 2015-07-21T19:55:41+00:00 Micah Anderson micah@leap.se 2015-07-21T19:55:41+00:00 cdadd9c1c26efd61c98a810206a06ce5b7302701 Conflicts: puppet/modules/site_static/manifests/init.pp Change-Id: I090b1cb3cbe3c4d01a2c640ae3a370b17e722e12 
Conflicts:
	puppet/modules/site_static/manifests/init.pp

Change-Id: I090b1cb3cbe3c4d01a2c640ae3a370b17e722e12
Increase tapicero heatbeat nagios checks (#7275) 2015-07-21T19:47:44+00:00 Micah Anderson micah@leap.se 2015-07-21T19:47:44+00:00 21af45fd2156e16786e3476c779115662ecb72a7 Increase warning/critical thresholds for time between tapicero heartbeat checks so it will emit less false positives Change-Id: I0f97373d88658b7f17b2c4e8c1963198dc3f66ed 
Increase warning/critical thresholds for time between tapicero heartbeat
checks so it will emit less false positives

Change-Id: I0f97373d88658b7f17b2c4e8c1963198dc3f66ed
Fix leap-mx logrotation to work with twistd (#7058) 2015-07-21T15:00:50+00:00 Micah Anderson micah@leap.se 2015-07-21T15:00:50+00:00 7c071c8e5953922040175c9bfdb458effb982847 We don't want to try and create the log file, twistd will do that. Don’t rename the log file from mx.log to mx.log.0, instead just copy it to mx.log.1, and then clear out mx.log so it’s empty (this is needed because leap-mx might assume that its file descriptor is still valid and continue trying to write to it, without this, leap-mx might lose data because it’ll assume the original log file is still around and continue to write to it, even though it’s gone)It’s a little dangerous because it’s possible that you might lose some logged data between the time that logrotate copies the new log file and truncates the old file (Caveat administrator). Finally, we don't want logrotate to complain if it finds mx.log, its ok if its there. Change-Id: I9952627f4d47e7a89a2915f6b72d82f9e6ca0d8b 
We don't want to try and create the log file, twistd will do that.

Don’t rename the log file from mx.log to mx.log.0, instead just copy it
to mx.log.1, and then clear out mx.log so it’s empty (this is needed
because leap-mx might assume that its file descriptor is still valid and
continue trying to write to it, without this, leap-mx might lose data
because it’ll assume the original log file is still around and continue
to write to it, even though it’s gone)It’s a little dangerous because
it’s possible that you might lose some logged data between the time that
logrotate copies the new log file and truncates the old file (Caveat
administrator).

Finally, we don't want logrotate to complain if it finds
mx.log, its ok if its there.

Change-Id: I9952627f4d47e7a89a2915f6b72d82f9e6ca0d8b
minor linting 2015-07-21T14:19:23+00:00 Micah Anderson micah@leap.se 2015-07-21T14:19:23+00:00 d609a948520e38feb79892eec6c80f3915940444 fix double quotes and indentation Change-Id: I79c28159d17e6256db3094f413d61dcdc9520dc6 
fix double quotes and indentation

Change-Id: I79c28159d17e6256db3094f413d61dcdc9520dc6
bump amber version, taking care of puppet ordering with require. 2015-07-14T13:55:49+00:00 kwadronaut kwadronaut@autistici.org 2015-07-14T13:55:49+00:00 c5f1790602b2a987f7cfb18b0da8e11e692cdd40 






Merge branch 'develop' of ssh://leap.se/leap_platform into develop
2015-07-09T19:18:21+00:00

elijah
elijah@riseup.net

2015-07-09T19:18:21+00:00

2d50141b8b0b223e3b437ff3bda0dd2dc7a64ef5












use latest amber for static nodes.
2015-07-09T19:18:03+00:00

elijah
elijah@riseup.net

2015-07-09T19:18:03+00:00

1e872b71382f94f9c2d63ccbcaa43ca7d6741b42












Clean up left-over files from old way of leap-mx logging, this should
2015-07-07T20:22:36+00:00

Micah Anderson
micah@leap.se

2015-07-07T20:22:36+00:00

ec24733308676d6822aaeaae6c17b042f7e2bf14

stop the logrotate cron errors from happening. (#7058)

Change-Id: Iceaeb8c17600fc23d2b1ca075546f8573c145760





stop the logrotate cron errors from happening. (#7058)

Change-Id: Iceaeb8c17600fc23d2b1ca075546f8573c145760







check_mk should not falsely report multiple instances running (#6866)
2015-07-07T14:36:30+00:00

varac
varacanero@zeromail.org

2015-07-07T14:30:42+00:00

7e6b3939a69f11d23ed1c876060025fbe694704d

Change-Id: Ie7943c9a541c3cd2feac7686ed1092aadc5a7c7a





Change-Id: Ie7943c9a541c3cd2feac7686ed1092aadc5a7c7a







Ignore openvpn logwatch warnings (#6867)
2015-07-07T14:04:40+00:00

varac
varacanero@zeromail.org

2015-07-07T14:04:40+00:00

3cb5ae59d51d85cde704214dcea7c65da2bf6e94

These are warnings that might have different origins, each of
them we don't want to alarm the admin:

- A bitmask client bug (user will poke the client devs if things
  break, and they will go after it)
- A simple network failure, packets might get cut of
- Malicious user tries to temper with TLS handshakes - this gets
  more interesting, but still (like ssh bruteforce attacs) an admin
  would not want to get annoyed by this by default, but they still
  have the option to use log analysers of their choice if they want
  to investigate this.

Change-Id: I23ca3b700e41f22f34ad3346ed4e647b86000bb2





These are warnings that might have different origins, each of
them we don't want to alarm the admin:

- A bitmask client bug (user will poke the client devs if things
  break, and they will go after it)
- A simple network failure, packets might get cut of
- Malicious user tries to temper with TLS handshakes - this gets
  more interesting, but still (like ssh bruteforce attacs) an admin
  would not want to get annoyed by this by default, but they still
  have the option to use log analysers of their choice if they want
  to investigate this.

Change-Id: I23ca3b700e41f22f34ad3346ed4e647b86000bb2