Opened 20 years ago
Last modified 10 years ago
#1 new patch
IZ24: make qsub/qrsh .qtask-file aware
Reported by: | andreas | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | current |
Severity: | minor | Keywords: | clients |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=24]
Issue #: 24 Platform: All Reporter: andreas (andreas) Component: gridengine OS: All Subcomponent: clients Version: current CC: None defined Status: NEW Priority: P3 Resolution: Issue type: ENHANCEMENT Target milestone: --- Assigned to: roland (roland) QA Contact: roland URL: http://gridengine.sunsource.net/unbranded-source/browse/~checkout~/gridengine/doc/devel/rfe/job_category.txt?content-type=text/plain * Summary: make qsub/qrsh .qtask-file aware Status whiteboard: Attachments: Date/filename: Description: Submitted by: Thu Mar 21 06:53:00 -0700 2002: percmddef.patch Look for per-command defaults files (text/plain) Mike Jagdis Issue 24 blocks: Votes for issue 24: Opened: Mon Jul 30 01:40:00 -0700 2001 ------------------------ The qtask file gives an administrator a means to specify resource requests and other submit options for his users individually for each job type. Currently only qtcsh accesses the .qtask file. Qsub and qrsh (not in case of qrsh -inherit) should be enhanced in an analoguous fashion. Open questions are whether an additional submit switch is needed to allow for explicitly disabling qtask file consideration. ------- Additional comments from Mike Jagdis Thu Mar 21 06:51:38 -0700 2002 ------- Or we could just look for .../[.]sge_request.<cmd> and if it exists use it instead of .../[.]sge_request. In fact, here's a patch that does just that :-) ------- Additional comments from Mike Jagdis Thu Mar 21 06:53:18 -0700 2002 ------- Created an attachment (id=6) Look for per-command defaults files ------- Additional comments from andreas Tue Oct 12 06:48:38 -0700 2004 ------- Added link to spec document. ------- Additional comments from andreas Fri Nov 18 03:10:16 -0700 2005 ------- A qtask(1) file based job categories could be used to make lack of a means to request resources separately for master task as outlined in http://gridengine.sunsource.net/issues/show_bug.cgi?id=75 less urgent. With a -cat <category> switch one could "cultivate" the workaround ( well, I know this is *evil*) allowing administrators to prepare a qtask(1) file that maps descriptive job category names into job submit options fluent2 -pe mpich 2 -l fluent_paralell=0.5 fluent4 -pe mpich 4 -l fluent_paralell=0.25 fluent8 -pe mpich 8 -l fluent_paralell=0.125 an end user then would simply use # qsub -cat fluent2 fluent.sh # qsub -cat fluent4 fluent.sh # qsub -cat fluent8 fluent.sh further improvements to easen end user job submission could be achieved if qtask(1)-based job categories would support expressions such as fluent 2 -l fluent_paralell={1/$SLOTS} a fluent job then could be submitted like this # qsub -pe mpich 2 -cat fluent # qsub -pe mpich 4 -cat fluent # qsub -pe mpich 8 -cat fluent ------- Additional comments from pollinger Fri Dec 9 09:12:11 -0700 2005 ------- changed subcomponent ------- Additional comments from templedf Mon Jan 12 13:53:59 -0700 2009 ------- This should be a relatively easy RFE to address. The functionality is already built into JAPI to support the DRMAA job category job template attribute.
Attachments (1)
Change History (2)
Changed 10 years ago by dlove
comment:1 Changed 10 years ago by dlove
- Severity set to minor
- Type changed from enhancement to patch
Note: See
TracTickets for help on using
tickets.