Hi Zack, It would be very convenient to have a read-only public copy of the paddles database. So that anyone can run a command like this: paddles=paddles.front.sepia.ceph.com run=loic-2016-01-29_00:40:06-upgrade:hammer-hammer-backports---basic-vps eval filter=$(curl --silent http://$paddles/runs/$run/ | jq '.jobs[] | select(.status == "dead" or .status == "fail") | .description' | while read description ; do echo -n $description, ; done | sed -e 's/,$//') to schedule a run of failed jobs. It could be done by activating continuous archiving of the pgsql wal (http://www.postgresql.org/docs/9.4/static/continuous-archiving.html) which can then be used to udpate the read-only copy. It is non intrusive for the running paddles and there is plenty of space to keep these. ubuntu@pulpito:~$ hostname --fqdn pulpito.front.sepia.ceph.com ubuntu@pulpito:~$ df -h / Filesystem Size Used Avail Use% Mounted on /dev/sda1 351G 5.6G 328G 2% / Do you think that's something sensible ? Cheers -- Loïc Dachary, Artisan Logiciel Libre -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
