Opened 12 years ago
Last modified 10 years ago
#624 new enhancement
IZ2891: Restrict interactive jobs to certain users
Reported by: | opoplawski | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | sge | Version: | 6.2u1 |
Severity: | Keywords: | GEP | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2891]
Issue #: 2891 Platform: All Reporter: opoplawski (opoplawski) Component: gridengine OS: All Subcomponent: GEP Version: 6.2u1 CC: None defined Status: NEW Priority: P4 Resolution: Issue type: ENHANCEMENT Target milestone: --- Assigned to: andre (andre) QA Contact: andre URL: * Summary: Restrict interactive jobs to certain users Status whiteboard: Attachments: Issue 2891 blocks: Votes for issue 2891: Opened: Mon Jan 26 11:58:00 -0700 2009 ------------------------ It would be nice to be able to restrict interactive jobs to particular users. ------- Additional comments from reuti Mon Jan 26 12:12:00 -0700 2009 ------- Making a special queue for interactive use and attach a user list there should do the trick (qtype INTERACTIVE, and remove INTERACTIVE from the other queue). ------- Additional comments from opoplawski Mon Jan 26 13:25:38 -0700 2009 ------- I suppose so, but I find the massive proliferation of different queues on the same hosts for slightly different purposes very confusing and hard to maintain. ------- Additional comments from reuti Mon Jan 26 14:10:43 -0700 2009 ------- I on my side like this setup, as the idea behind SGE is in general: specify resource requests and SGE will select an appropriate queue for you. This way you also have the option to grant different h_rt et al. to each queue, means different users could get different restrictions for their interactive work. Nevertheless, with the upcoming JSV (job submission verfier) you could put the test for the eligible users there and reject users you don't like to do interactive work. ------- Additional comments from crei Thu Feb 26 01:36:20 -0700 2009 ------- setting to P4 since there is a workaround
Note: See
TracTickets for help on using
tickets.