From a0780a6a33358c5b94a633ea5bf3e99a692ef864 Mon Sep 17 00:00:00 2001 From: Sam Thursfield Date: Thu, 5 Jun 2014 17:40:02 +0100 Subject: Prevent distbuild nodes from filling up their disks Distbuild workers run `morph gc` before running a build, to remove stale artifacts, but it turns out that they were configured in such a way that the command didn't do anything. Because of this, it was possible for distbuild nodes to break due to filling up their disks with cached git repos and artifacts. --- distbuild.configure | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/distbuild.configure b/distbuild.configure index bf145b14..65ac47e3 100644 --- a/distbuild.configure +++ b/distbuild.configure @@ -60,9 +60,6 @@ install -d -o 0 -g 0 -m 0755 "$1/srv/distbuild" # use. However, the setting may only be set for the distbuild # initiator (which is what the user invokes), so in ALL other # configuration files we unset it. -# -# We disable the disk space requirement checks on non-worker nodes. -# They don't make sense unless you're building locally. cat < "$1/etc/morph.conf" [config] @@ -73,8 +70,8 @@ tempdir = /srv/distbuild/tmp trove-host = $TROVE_ID trove-id = $TROVE_ID controller-initiator-address = $CONTROLLERHOST -tempdir-min-space = 0 -cachedir-min-space = 0 +tempdir-min-space = 4G +cachedir-min-space = 4G build-ref-prefix = $TROVE_ID artifact-cache-server = http://${ARTIFACT_CACHE_SERVER}:8080/ git-resolve-cache-server = http://${TROVE_ID}:8080/ -- cgit v1.2.1