[Beaker-devel] Proposal: revised "nag email" system

Nick Coghlan ncoghlan at redhat.com
Wed Aug 7 04:39:57 UTC 2013


I just filed https://bugzilla.redhat.com/show_bug.cgi?id=994325 with a
new proposed design for the nag email system. This may be a good one to
squeeze into 0.15, as it should be a fairly isolated change (just the
nag_email.py script) and significantly less annoying than the current
approach for users with lots of systems reserved that aren't in high
demand :)

The main changes proposed are to make it:

1. User based, so each user gets at most one email per run
2. Need based, as we only care about systems with "waiting" recipes
3. More helpful, by providing some relevant search links


Example email sketch quoted from the RFE:

=========
[Beaker] Systems allocated to <username> (<date>)
=========
Hi <name>,

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.

System Reservations

  Duration    Waiting     FQDN
   23 days   3 recipes    host.beakerlab.example.com

All systems reserved by you: https://<Beaker instance
FQDN>/?systemsearch-0.table=System%2FUser&systemsearch-0.keyvalue=&systemsearch-0.operation=is&systemsearch-0.value=<username>

System Loans

  Duration    Waiting    FQDN
    7 days   1 recipe    host2.beakerlab.example.com

All systems loaned to you: https://<Beaker instance
FQDN>/?systemsearch-0.table=System%2FLoanedTo&systemsearch-0.keyvalue=&systemsearch-0.operation=is&systemsearch-0.value=<username>

=========

Cheers,
Nick.

-- 
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane

Testing Solutions Team Lead
Beaker Development Lead (http://beaker-project.org/)


More information about the Beaker-devel mailing list