Skip to content

Testing jobsub_lite under POMS

Jump to bottom
Marc Mengel edited this page Oct 5, 2022 · 17 revisions

If you want to use production POMS to test jobsub_lite, you have currently to do some gymnastics. For the moment, I recommend putting these in a POMS login_setup config, then you can choose that login_setup for a given campaign to test. It also needs to be a login_setup because you need to point at a different launch host.

So in the POMS menu, under Configure Work, choose "Compose Login Setup"; pick one of your existing ones and clone it with the coppy icon: copy_icon This should give you an edit window that lets you

  • set the Name to something useful (like the original with _lite on the end).
  • set the Host to fifeutilgpvm02.fnal.gov

and add / change Setup items, which are all on one continuous line of shell script. To whatever you had you should append the following items, separated by semicolons.

  • unsetup -j jobsub_client -- to use the RPM-installed jobsub_lite instead
  • export JOBSUB_CLIENT_DIR=/opt/jobsub_lite/bin-- let poms_jobsub_wrapper find jobsub_submit until we get a new version. (This may be redundant with the previous item..)
  • export IFDH_TOKEN_ENABLE=1 -- to enable ifdh using tokens
  • export IFDH_PROXY_ENABLE=0 -- to disable ifdh using proxies
  • setup -j ifdhc v2_6_6, -j ifdhc_config v2_6_6 -- version where tokens work (mostly)
  • export JOBSUB_CLIENT_DIR=/opt/jobsub_lite/bin -- for poms_jobsub_wrapper to run the right jobsub_submit...
  • export BEARER_TOKEN_FILE=/tmp/token$$ --to make a fresh token for the submit
  • export _condor_SEC_CREDENTIAL_STORER=/bin/true -- to not call condor_vault_storer (the production token push did this for you)

And then for production campaigns:

  • htgettoken --nokerberos --nooidc -r production -i %(experiment)s --credkey=%(experiment)spro/managedtokens/fifeutilgpvm01.fnal.gov" -a fermicloud543.fnal.gov

Or for analysis campaigns:

  • htgettoken --nokerberos --nooidc -r production -i %(experiment)s --vaulttokeninfile=$UPLOADS/bt_%(experiment)s_Analysis_%(experimenter)s -a fermicloud543.fnal.gov

Also note that analysis users will need to upload a vault token, using the latest poms_client upload file script: ./upload_file --vaulttoken
which you can download here: https://cdcvs.fnal.gov/redmine/projects/prod_mgmt_db/repository/revisions/develop/raw/poms_client/bin/upload_file

Clone this wiki locally