Populate user email address in the forms from REMOTE_USER

[GKlouse (Greg Klouse)]

Is there a way I can pull the current user’s email address to automatically populate a field in the form.yml and submit.yml files for an interactive vnc submit?

Ultimately, I would like to add the option to my form which will enable slurm to email the user when the current session is at 50,80,90, and 100% time limit. You have implemented a similar option with the “bc_email_on_started” option, and I would like to just pull the user’s email to add it into the submit.yml automatically based on the current user.

Thanks,
Greg

[travert (Travis Ravert)]

@GKlouse

Is there a way I can pull the current user’s email address to automatically populate a field in the form.yml and submit.yml files for an interactive vnc submit?

I’m not entirely sure to be honest. There is a previous thread around some questions about how the emailing works, with a suggestion of how to set headers with this information in the cluster config here:

Global email setting

To verify, the goal is to set the email argument for each user, for each interactive app, in a single place. What resource manager are you using? Out of the box we don’t support this, but we have discussed adding support for this type of thing, as we would find it very useful as well. These are some related issues we have currently opened up: https://github.com/OSC/ood_core/issues/97 - want the ability to add default submission arguments in the cluster config for every job submitted through…

Which is a bit older and was linked form another conversation around getting emails for jobs here:

E-mail to user at job start,

There has been some discussion earlier on different sites implementing e-mail alerts when OOD jobs start, via the bc_email_on_started attribute. For the user to get the e-mail, the scheduler needs to also have the e-mail address of the user and turn on the option to feed in that e-mail (in SLURM –mail-user). I can put this in each app’s submit.yml.erb (e.g., in our case –mail-user=$USER@utah.edu), but, given the amount of apps we have it’d be easier if this could be a global option for all jobs…

In short, I’m not sure of a way to pull this to populate the form and submit unless you can glean something from those posts.

[mcuma (Martin Cuma)]

Hi everyone, we do this in submit.yml.erb:

<%-
emailcmd = '/uufs/chpc.utah.edu/sys/bin/CHPCEmailLookup.sh ’ + ENV[“USER”]
emailaddr = %x[ #{emailcmd}]
-%>

---

batch_connect:
template: vnc
script:
email: <%= emailaddr %>

The /uufs/chpc.utah.edu/sys/bin/CHPCEmailLookup.sh is a script that matches the Linux user name with the e-mail address in our database. That is more robust than the previous setting we had:
email: <%= ENV[“USER”] %>@utah.edu
because some users use other e-mail addresses than our domain.

You could do the same thing in the form.yml.erb to display the e-mail address in the submission form.

HTH.

[GKlouse (Greg Klouse)]

Thanks guys for the feedback. I ended up using a text input widget for the email address within the form, then calling that variable in the submit.yml like this:

… “–mail-user”, “#{email}”, “–mail-type”, “TIME_LIMIT_50,TIME_LIMIT_80,TIME_LIMIT_90,TIME_LIMIT”]

I didn’t realize how easy this was to implement, so I am happy with the result =)