production-config: Increase LogsMinSpaceMby etc.

osstest does not currently try to estimate the prospective disk use in
logs/ etc. of a flight before it starts; nor does it aggregate the
disk requirements of multiple concurrent flights.

Instead, it has a hardcoded minimum, which is enforced (by expiry) at
the start of each flight.  It must be large enough for all in-progress
flights.  This turns out not to be true any more, because of expansion
of both the number of different osstest branches, and because of
expansion of the number of jobs per flight, and because of expansion
of the activities within each job.

So, well, let's double it.

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>

diff --git a/production-config b/production-config
index 0e6a51e9fe543e13addcb71066684a432f46cb01..ca594bd6ae46c1fb7bd261fc515d191ef50658a0 100644 (file)
--- a/production-config
+++ b/production-config
@@ -40,9 +40,9 @@ PubBaseDir /home/logs
 
 OverlayLocal /home/osstest/overlay-local
 
-LogsMinSpaceMby= 10*1e3
+LogsMinSpaceMby= 20*1e3
 LogsMinExpireAge= 86400*4
-LogsPublishMinSpaceMby= 10*1e3
+LogsPublishMinSpaceMby= 20*1e3
 LogsPublishMinExpireAge= 86400*7
 
 TestHostKeypairPath /home/osstest/.ssh/id_rsa_osstest