Hi Reuti,
thank you for your quick reply!
Quoting Reuti <[email protected]>:
Hi,
Am 27.04.2011 um 17:46 schrieb [email protected]:
I have some problems configuring my gridengine setup right.
In order to test a cluster setup I want to restrict a queue to
dedicated users. To achieve this I made an ACL and added it to the
xuser_list from the queue:
$ qconf -au my_list my_username
it's the other way round:
$ qconf -au reuti tester
added "reuti" to access list "tester"
Sorry for that, I twisted the two arguments in my eMail, not in the
commandline.
$ qconf -mq my.q
...
user_lists NONE
xuser_lists my_list
...
But instead of revoking qsub commands I can still submit jobs from
user "my_username".
Adding something to xuser_lists will block user(s) to use this
resource. But jobs from my_username should never ever being scheduled
to this queue. This doesn't mean that you can't submit at all - the
job will just hang there when there is no other queue. You can submit
with "-w e" get an error when there is no suitable queue at all.
Ok, now it makes much more sense to me. But how can I block a job from
execution, or even better, from submission, which is submitted to a
certain queue from a user which is on the blocklist? If the job is
submitted to this queue it should not end up in another queue. Is this
possible?
Another thing I want to do right is that I want to be able to submit
jobs to a queue which has currently no execution hosts registered.
Why do you want to do so?
Although there are situations when you want to submit to a queue, the
paradigm in SGE is to request resources and SGE will select an
appropriate queue for you, which will fulfill the resource request.
Submitting to a queue is more Torque-style.
Can you rephrase the problem by requesting memory, walltime,
diskspace, cores... or a complex having a certain value? Something
like:
$ qsub -l cpu_type=propeller job.sh
The thing is, I want users to submit to a special queue "cloud.q". As
soon as there is need for new resources they will be added dynamically
to GE. Otherwise there will be no hosts. Afterwards they will be killed
and disconnected from GE.
I know, that GE is not intended to be used that way, but tests show
that it is capable of. And to reduce cloud usage, I want to restrict
this queue.
I hope this makes thing clearer.
Regards,
Stephan
-- Reuti
After submission I add an execution host to my_hostlist and the job
gets executed. For this purpose I've added "localhost" to
my_hostlist... otherwise gridengine won't accept any jobs for this
queue:
$ qconf -mq my.q
qname my.q
hostlist @my_hostlist localhost
...
I have a feeling that this isn't the best solution for my problem.
Does anybody know how to do this right?
Thanks in advance!
Regards,
Stephan
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
