Currently POMS uses a separate package "poms_jobsub_wrapper" to integrate job submission with POMS; now that the interface is (we believe) stable, we would like to move that into jobsub_submit and jobsub_submit_dag.
The option would be something like
which would do the following:
- call from the poms_client package's poms_client.py:
tid = get_task_id_for(campaign_id, user, command_line, parent_task_id=os.environ.get('POMS_PARENT_TASK_ID',None), test=os.environ.get('POMS_TEST',None) )
and then emulate adding:
-e POMS_CAMPAIGN_ID \ -e POMS_TASK_ID \ -l "+FIFE_CATEGORIES='\"POMS_TASK_ID_$POMS_TASK_ID,POMS_CAMPAIGN_ID_$POM S_CAMPAIGN_ID$POMS_CAMPAIGN_TAGS\"'" \ -l "+POMS_TASK_ID=$POMS_TASK_ID" \ -l "+POMS_CAMPAIGN_ID=$POMS_CAMPAIGN_ID" \
to the command line. Then users can pass --poms_campaign_id rather than use the poms_jobsub_wrapper package, which could be dropped.
#7 Updated by Marc Mengel 12 months ago
We should update this, the list of things to do has gotten longer :-)
The latter can be much simpler, since jobsub already has the jobid and doesn't need to parse its own output...