Archive Trac dn airavata qa

Dn Airavata Qa

Legacy Trac archive page imported from dn_airavata_qa. Source: https://genapp.rocks/wiki/wiki/dn_airavata_qa. Review age, links, and examples before treating as current.

airavata q & a

• q: how do credentials work

  • a: see here

• q: explain how email monitoring works and how i set it up...

for 0.15 and 0.16 it is same.. you can set it on airavata-server.properties
you need to change following properties in there

#These properties will used to enable email base monitoring
email.based.monitor.host=imap.gmail.com
email.based.monitor.address=<redacted-email>
email.based.monitor.password=somepassword
email.based.monitor.folder.name=INBOX
# either imaps or pop3
email.based.monitor.store.protocol=imaps
#These property will be used to query the email server periodically. value in milliseconds(ms).
email.based.monitoring.period=10000

for 0.16, resource side email servers are set up at gfac-config.yaml.. So you can add your new compute resource / job manager there
resources:
- jobManagerType: PBS
commandOutputParser: org.apache.airavata.gfac.impl.job.PBSOutputParser
emailParser: org.apache.airavata.gfac.monitor.email.parser.PBSEmailParser
resourceEmailAddresses:
- <redacted-email> # gordon
- <redacted-email> # Bigred2
- root <<redacted-email>> # Bigred2
- root <<redacted-email>> # alamo

- jobManagerType: SLURM
    commandOutputParser: org.apache.airavata.gfac.impl.job.SlurmOutputParser
    emailParser: org.apache.airavata.gfac.monitor.email.parser.SLURMEmailParser
    resourceEmailAddresses:
      - SDSC Admin <<redacted-email>> # comet
      - <redacted-email> # stampede

  - jobManagerType: UGE
    commandOutputParser: org.apache.airavata.gfac.impl.job.UGEOutputParser
    emailParser: org.apache.airavata.gfac.monitor.email.parser.UGEEmailParser
    resourceEmailAddresses:
      - ls4.tacc.utexas.edu # contain Lonestar

  - jobManagerType: LSF
    commandOutputParser: org.apache.airavata.gfac.impl.job.LSFOutputParser
    emailParser: org.apache.airavata.gfac.monitor.email.parser.LSFEmailParser
    resourceEmailAddresses:
      - iu.xsede.edu # test resource mail address

  - jobManagerType: FORK
    commandOutputParser: org.apache.airavata.gfac.impl.job.ForkOutputParser

for 0.15, resource side email is hard coded in gfac/monitor/email/EmailBasedMonitor.java

• q: for email based monitoring... are the created SLURM/PBS etc scripts handling the email sending ? for FORK, do I have to do this in my code ? if so, is there example message content ?

for SLURM and PBS, we added it to job descriptor file..
e.g. 

#SBATCH --mail-user=<redacted-email>
#SBATCH --mail-type=ALL

for FORK you might need to do it in your code

e.g. for Stampede, generated mail subject looks like this
SLURM Job_id=6009354 Name=A1109785114 Ended, Run time 00:00:17, COMPLETED, ExitCode 0

• q: how do i setup AuthzToken for 0.16 ?

for java, it is something like this
AuthzToken token = new AuthzToken("empty_token");
System.out.println("API version is " + airavataClient.getAPIVersion(token));

and in airavata-server.properties, you can disable security
api.secured=true, set this to false

• q: airavata log shows [ERROR] The 'output.location' is not configured in settings!!! ...

add to airavata-server.properties file (& restart airavata):
output.location= 

• q: my variable command line inputs are not getting added to the generated slurm/pbs/etc script
• a: make sure experimentInputs:...:requiredToAddedToCommandLine is set to true