Re: [Condor-users] condor-administrators

[Jaime Frey <jfrey@xxxxxxxxxxx>]

On Dec 21, 2005, at 11:59 AM, Maxim Kovgan wrote:

> Hello, dear * !
>
> We have a condor pool.
> 2 'central managers' oredered with a HAD ( master, collector,
> negotiator, had )
> 2 submission machines (master,schedd only)
> about 200 nodes ( master,startd only )
> the collectors are running 6.7.13.
> 1/2 nodes are 6.7.8 and another half - 6.7.13
>
> We have 2 submission machines for one reason: we want to share this  
> pool
> via globus. The globus users will be mapped to local special users,  
> and
> will submit ONLY via one specific schedd, local normal user will  
> submit
> via another schedd only, the separation is done via unix group
> separation and restriction at login level.
>
> The pool overall works quite fine.
>
>
> 2 main problems:
>
> 1. custom configuration variables... how ?!
> I would want to have a convenient and fault tolerant way to define a
> special variable in ${HOSTNAME}.local file to designate the machine  
> has
> all globus software installed. e.g. I'd call it IS_LCG2_WN and  
> define it
> as True.
> I'd write:
> IS_LCG2_WN = True
> in the config file.
>
> on the schedd I'd add to the jobs' requirement:
> APPEND_REQUIREMENTS = ( IS_LCG2_WN =?= True )
> or maybe:
> APPEND_REQUIREMENTS = ( $(IS_LCG2_WN) =?= True )
> or
> APPEND_REQUIREMENTS = ( IS_LCG2_WN )
>
>
> and then the users of globus would have their jobs submitted only  
> to the
> chosen machines.
>
> Same would be nice with the execution machines' sides: on schedd I'd
> write:
>
> IS_LCG_SUBMISSION = True
>
> and on the startd's side I'd put something like
> RANK = 1 + 10 * IS_LCG_SUBMISSION
>
> etc.
>
> I of course tried all above options, and NONE worked.
> I did try to see what condor_config_val has to say about all of these,
> and condor_config_val always said that everything is OK, sir.
> yep, sure.
>
> I currently add FULL hostnames list in the append_requirements  
> variable.
> But this is UGLY.
> Is there another way ?

Adding attributes in the config file is not sufficient to have them  
appear in the job and machine ads. You have to tell Condor to include  
them. On the execute machines, add IS_LCG2_WN to the STARTD_EXPRS  
list in the config file. On the Globus submission node, use  
APPEND_REQUIREMENTS = (IS_LCG2_WN =?= True).

To include IS_LCG_SUBMISSION in the job ads, set SUBMIT_EXPRS =  
IS_LCG_SUBMISSION.

Don't forget to do a condor_reconfig to have the daemons pick up the  
changes.

> 2. User Environment.
> I wonder if there is a way to force users to have a special  
> Environment,
> inspite the user's will to define "Env = bla=blabla; etc." in the
> submission file.
> Is this possible at all ?
> According to the manual - no.
> (STARTER_* variables can be overridden by users in  the submit file )
>
> Note, I have read the related parts from the manual, but experiments
> showed something is wrong.

One way to do this is to use the USER_JOB_WRAPPER (see the manual for  
details).

+----------------------------------+---------------------------------+
|            Jaime Frey            |  Public Split on Whether        |
|        jfrey@xxxxxxxxxxx         |  Bush Is a Divider              |
|  http://www.cs.wisc.edu/~jfrey/  |         -- CNN Scrolling Banner |
+----------------------------------+---------------------------------+