llama com gracedb

Download and install the GWHEN Kerberos keytab used for accessing GraceDB on production machines. You will need access to LLAMA S3 to do this (see llama.com.s3 for details). If you are running on your personal computer, just use kinit your.username@LIGO.ORG to get access to GraceDB.

usage: llama com gracedb [-h] [-l LOGFILE]
                         [-v {debug,info,warning,error,critical,none}]
                         {fetch,install,rm}

Positional Arguments

subcmd

Possible choices: fetch, install, rm

If fetch is specified, download the robot keytab from LLAMA S3 if it is not currently installed (this requires you to have LLAMA S3 credentials, which you don’t need unless you are a developer; if you’re just a user, use kinit instead of this keytab). If install is specified, fetch the keytab if missing and generate Kerberos credentials with it, installing them to /root/cilogon_cert. If rm is specified, run kdestroy to deactivate those credentials and delete /root/cilogon_cert. Also remove the keytab file from local storage. (default: install)

Default: “install”

logging settings

-l, --logfile

File where logs should be written. By default, all logging produced by llama run goes to both an archival logfile shared by all instances of the process as well as STDERR. The archival logfile can be overridden with this argument. If you specify /dev/null or a path that resolves to the same, logfile output will be suppressed automatically. Logs written to the logfile are always at maximum verbosity, i.e. DEBUG. (default: /dev/null)

Default: “/dev/null”

-v, --verbosity

Possible choices: debug, info, warning, error, critical, none

Set the verbosity level at which to log to STDOUT; the --logfile will ALWAYS receive maximum verbosity logs (unless it is completely supressed by writing to /dev/null). Available choices correspond to logging severity levels from the logging library, with the addition of none if you want to completely suppress logging to standard out. (default: info)

Default: “info”