Am 09.04.2019 um 21:08 schrieb Mun Johl:
> Hi Reuti, > > One clarification question below ... > > On Tue, Apr 09, 2019 at 09:05 AM PDT, Reuti wrote: >>> Am 09.04.2019 um 17:43 schrieb Mun Johl <mun.j...@kazan-networks.com>: >>> >>> Hi Reuti, >>> >>> Thank you for your reply! >>> Please see my comments below. >>> >>> On Mon, Apr 08, 2019 at 10:27 PM PDT, Reuti wrote: >>>> Hi, >>>> >>>>> Am 09.04.2019 um 05:37 schrieb Mun Johl <mun.j...@kazan-networks.com>: >>>>> >>>>> Hi all, >>>>> >>>>> My company is hiring a contractor for some development work. As such, I >>>>> need to modify our grid configuration so that he only has access to a >>>>> single execution host. That particular host (let's call it serverA) >>>>> will not have all of our data disks mounted. >>>>> >>>>> NOTE: We are running SGE v8.1.9 on systems running Red Hat Enterprise >>>>> Linux v6.8 . >>>>> >>>>> I'm not really sure how to proceed. I'm thinking of perhaps creating a >>>>> new queue which only resides on serverA. >>>> >>>> There is no need for an additional queue. You can add him to the >>>> xuser_lists of all oher queues. But a special queue with a limited number >>>> of slots might give the contractor more priority to check his develoment >>>> faster. Depends on personal taste whether this one is preferred. This >>>> queue could have a forced complex with a high urgency, which he always >>>> have to request (or you use JSV to add this to his job submissions). >>> >>> How would I proceed if I did not create an additional queue? You have >>> me intrigued. That is, if I add him to the xuser_lists of all queues, >>> he wouldn't be able to submit a job, would he? Perhaps I'm confused. >> >> All entries in the (cluster) queue definition allow a list of different >> characteristics (similar to David's setup in the recent post): >> >> $ qconf -sq all.q >> ... >> user_lists NONE,[development_machine=banned_users] >> xuser_lists NONE,[@ordinary_hosts=banned_users] > > I created a host group of servers only accessible by employees (not the > contractor). And then I created an ACL named "contractors" which > contains the contractor's username. > > So if I want to forbid the "contractors" from accessing the @EmpOnly > servers on a given queue, would I simply modify the following > xuser_lists line in the queue file as shown below? > > xuser_lists NONE,[@EmpOnly=contractors] > > Best regards, > > -- > Mun > _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
