Thanks for the help, Chris. Rick Reynolds -- "I used to think the human brain was the most fascinating part of the body. Then I realized, well, look what's telling me that." -- Emo Phillips
On Oct 5, 2011, at 3:34 PM, Chris Dagdigian wrote: > > That's the right way to do it but you don't need to do it at the queue > level if you don't want. > > You can assign attributes to the nodes themselves and then request them > like... > > qsub -hard -l resourceX=TRUE ./path-to-my-job.script > > That will run on any queue and only on hosts where the boolean > comparison matches. > > The advantage of tagging hosts and requesting those host-specific tags > is that you don't have to create and manage a pile of queues with > different resources attached. The philosophy of SGE is "minimal queues > with each user responsible for requesting the resources he/she needs in > order to be successful" > > -Chris > > > > Rick Reynolds II wrote: >> We're planning to use SGE to send jobs to a set of worker machines. Those >> worker machines are each connected to specific and different pieces of >> hardware. So a specific job would need to be mapped to a specific worker >> machine that was connected to the appropriate hardware. >> >> The worker machines themselves all look pretty much the same (same kind of >> machines, same OS, etc.). So I'm looking at differentiating the queues via >> the complex attributes. E.g. giving each queue a Type via a string value >> that must be matched by 'qsub -l<attr>=<val>' kinds of commands. >> >> Is this the only option in SGE for differentiating queues/machines based on >> attributes that aren't part of the worker machine itself? I.e. are the >> complex attributes the only way of "tagging" machines or queues? >> >> Thanks, >> Rick Reynolds This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof. _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
