One of the things that we're looking to (hopefully) have implemented for
Beaker 0.17 is a redesign of the usage reminder email system so that it
sends at most one email per user per day (currently, it can send one
email per reserved system per user per day, and so nobody will ever turn
it on for a large Beaker installation).
The full proposal is available at
the core part is the design of the reminder email itself:
[Beaker] Usage report for <name> (<date>)
Your reservations of the following systems in <Beaker instance FQDN> are
going to expire within 24 hours. If you wish to ensure you retain the
contents of these systems, please extend your reservation.
Expiry Date FQDN
2014-05-15 05:18:01 +10:00 host.beakerlab.example.com
The following systems have been allocated to you in <Beaker instance FQDN>
for more than <X> days and have other recipes queued for execution. Please
return them if you are no longer using them.
Duration Waiting FQDN
7 days 1 recipe host2.beakerlab.example.com
The following jobs you submitted to <Beaker instance FQDN> have been queued
for more than <X> days. Please cancel them if they are no longer relevant,
or perhaps arrange a loan of an appropriate system or systems
Start time Delayed Job
2014-05-15 05:18:01 +10:00 https://<Beaker instance FQDN>/jobs/4594
The proposal has more details on what would trigger the specific entries
in the email.
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane
Testing Solutions Team Lead