Currently, the notion of "Submission Delegates" is part of the Enhanced
User Groups design proposal:
http://beaker-project.org/dev/proposals/enhanced-user-groups.html#submiss...
However, looking at some of the feedback that led to the creation of
that feature, I'm wondering if it actually makes sense for "Submission
Delegates" to be a group level feature. Since the only permission it
grants is the ability to submit jobs, perhaps it would make more sense
for it to be pulled out to a separate design proposal as a *user* level
feature?
Then the job header in the XML could just gain a "user=<username>"
attribute (similar to the just added "group=<groupname>" attribute), and
all we would do on the back end is add an informational
"submitting_user" field to jobs in the database, and allow individual
*users* to nominate other users as submission delegates.
This seems like it would be simpler to implement and manage, and also
better serve the intended use case of allowing an external automated
service that simplifies scheduling and submission of jobs on behalf of
various users.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Testing Solutions Team Lead
Beaker Development Lead (
http://beaker-project.org/)