Project

General

Profile

Feature #17931

Add "HOLD/RELEASE Jobs button"

Added by Anna Mazzacane about 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
10/17/2017
Due date:
% Done:

100%

Estimated time:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

HOLD function can be applied in two different ways:

- Hold running/idle jobs ( from the campaign submission level (bunch of jobs) to the a single job).
- Hold (future) launches.

This refers to the first.


Related issues

Copied to Production Operations Management Service (POMS) - Feature #17934: Add "HOLD/RELEASE Launches button(s)"Closed10/17/2017

History

#1 Updated by Marc Mengel about 3 years ago

  • Copied to Feature #17934: Add "HOLD/RELEASE Launches button(s)" added

#2 Updated by Marc Mengel about 3 years ago

  • Subject changed from Add "HOLD/RELEASE button" to Add "HOLD/RELEASE Jobs button"
  • Description updated (diff)

#3 Updated by Marc Mengel about 3 years ago

This should go anywhere we currently have the kill jobs "Trash" icon in the GUI for running jobs. WE had discussed using play and pause icons for this, possibly we should use stop instead of the trash icon we have now.


<bel-kwinith>$ grep kill.*trash  *.py templates/*.html
CampaignsPOMS.py:                extramap[jjid] = '<a href="{}/kill_jobs?task_id={:d}"><i class="ui trash icon"></i></a>'.format(
TaskPOMS.py:                extramap[jjid] = '<a href="%s/kill_jobs?job_id=%d"><i class="ui trash icon"></i></a>' % (self.poms_service.path, jh.job_id)
templates/campaign_info.html:        <a href="{{pomspath}}/kill_jobs?campaign_id={{Campaign.campaign_id}}"><i class="external trash icon" data-content="Kill jobs in Campaign" data-variation="basic"></i>Kill Jobs for Campaign</a>
templates/job_table.html:                    <a href="%s/kill_jobs?job_id={{job['jobsub_job_id']}}"><i class="ui trash icon"></i></a>

Then we need to make the link for "kill" take an argument as to whether it is a kill, hold, or release, and pass it through...

<bel-kwinith>$ grep 'def kill_jobs' poms_service.py JobsPOMS.py
poms_service.py:    def kill_jobs(self, campaign_id=None, task_id=None, job_id=None, confirm=None):
JobsPOMS.py:    def kill_jobs(self, dbhandle, campaign_id=None, task_id=None, job_id=None, confirm=None):

and then in JobsPOMS.py we need to use that parameter to decide whether to call jobsub_rm, jobsub_hold, or jobsub_release...

#4 Updated by Marc Mengel almost 3 years ago

  • % Done changed from 0 to 80

Mostly done, needs testing.
a74af864

Possible issues; authentication for jobsub_release versus jobsub_rm seems to be different for no apparent reason(?).

#5 Updated by Marc Mengel almost 3 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 80 to 100

#6 Updated by Anna Mazzacane over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF