Re: [Condor-users] Condor $(OpSys) and $(Arch) parameter

[kschwarz@xxxxxxxxxxxxxx]

Hi Matt,

Recalling this discussion thread, I
was now trying to use the suggested parameters in a requirements _expression_,
and I am getting the job stuck in the queue.
The submit description file is as follow:

Universe   = vanilla
requirements = ArchGeneric == "INTEL" &&
OpSysGeneric == "WINNT"
should_transfer_files = YES
when_to_transfer_output = ON_EXIT_OR_EVICT
Executable = simple.bat
Arguments  = 4 12
Log        = simple.log
Output     = simple.out
Error      = simple.err
Queue

It was submitted from a Linux machine
to a Windows Condor Pool (Manager and Execute machines OS is Windows XP
Pro).

o24003:/home/pcd/10238/SD/Condor-test/509-linux_submit/01
$ condor_submit linux_submit-01.sub
Submitting job(s).
Logging submit event(s).
1 job(s) submitted to cluster 7.
o24003:/home/pcd/10238/SD/Condor-test/509-linux_submit/01
$ condor_q -b


-- Submitter: o24003.hpc.sjk.emb : <10.13.10.97:35227>
: o24003.hpc.sjk.emb
---
007.000:  Run analysis summary.  Of 42 machines,
     42 are rejected by your job's
requirements
      0 reject your job because of
their own requirements
      0 match but are serving users
with a better priority in the pool
      0 match but reject the job for
unknown reasons
      0 match but will not currently
preempt their existing job
      0 are available to run your job
        No successful match recorded.
        Last failed match: Fri
Oct 30 15:07:52 2009
        Reason for last match
failure: no match found

WARNING:  Be advised:
   No resources matched request's constraints

The Requirements _expression_ for your job is:

( target.ArchGeneric == "INTEL" &&
target.OpSysGeneric == "WINNT" ) &&
( target.Disk >= DiskUsage ) && ( ( target.Memory
* 1024 ) >= ImageSize ) &&
( target.HasFileTransfer )

    Condition        
                Machines Matched
   Suggestion
    ---------        
                ----------------
   ----------
1   target.ArchGeneric == "INTEL"  
  0                  
REMOVE
2   target.OpSysGeneric == "WINNT"
   0                
  REMOVE
3   ( target.Disk >= 1 )      
       42
4   ( ( 1024 * target.Memory ) >= 1 ) 42
5   ( target.HasFileTransfer )    
   42
o24003:/home/pcd/10238/SD/Condor-test/509-linux_submit/01
$ condor_config_val STARTD_ATTRS -v
STARTD_ATTRS: GridApps, Group, COLLECTOR_HOST_STRING,
ArchGeneric, OpSysGeneric, COLLECTOR_HOST_STRING
  Defined in '/dtemastr/PCD/GRID/CONDOR/3-pool/NPT/o24003/linux/condor_config.thishost',
line 19.

o24003:/home/pcd/10238/SD/Condor-test/509-linux_submit/01
$

On one execute node of the condor pool
the result of condor_config_val
command is:

C:\Temp>condor_config_val -v STARTD_ATTRS ArchGeneric
OpSysGeneric
STARTD_ATTRS: GridApps, Group, COLLECTOR_HOST_STRING,
ArchGeneric, OpSysGeneric, COLLECTOR_HOST_STRING
  Defined in '\\SMBSJK05\grid_env\CONDOR\3-pool\NPT\PC284419\condor_config.thishost',
line 24.

ArchGeneric: INTEL
  Defined in '\\SMBSJK05\grid_env\CONDOR\1-start\condor_config.master.PC284419',
line 15.

OpSysGeneric: WINNT
  Defined in '\\SMBSJK05\grid_env\CONDOR\1-start\condor_config.master.PC284419',
line 16.


C:\Temp>

What is worg?

Klaus

kschwarz@xxxxxxxxxxxxxx
Sent by: condor-users-bounces@xxxxxxxxxxx

22/09/2009 08:50

Please respond to
Condor-Users Mail List <condor-users@xxxxxxxxxxx>

To	Condor-Users Mail List <condor-users@xxxxxxxxxxx>
cc
Subject	Re: [Condor-users] Condor $(OpSys) and $(Arch) parameter

Great, Mat. 
It worked as I needed. 

Klaus

Matthew Farrellee <matt@xxxxxxxxxx>
Sent by: condor-users-bounces@xxxxxxxxxxx

17/08/2009 13:36

Please respond to
Condor-Users Mail List <condor-users@xxxxxxxxxxx>

To	Condor-Users Mail List <condor-users@xxxxxxxxxxx>
cc
Subject	Re: [Condor-users] Condor $(OpSys) and $(Arch) parameter

kschwarz@xxxxxxxxxxxxxx wrote:
> Hi all,
> 
> Is there any parameter that is similar to the $(OpSys) but returns
a 
> generic name for the operational system instead of the different versions
> of Windows platforms (for instance!)? The same is valid for the $(Arch)
> parameter.
> What I want to do is to use this parameter (let say $(OpSysGeneric))
to be 
> referenced in the requirements of a job or to configure Platform-Specific
> Configuration Files. See examples below.
> 
> Requirements = (OpSysGeneric == "WINNT")
> 
> instead of
> 
> Requirements = (OpSys == "WINNT51" || OpSys == "WINNT52"
|| OpSys == 
> "WINNT60" || OpSys == "WINNT61")    
          ## and so on!
> 
> and
> 
> condor_config.SUN.SOLARIS
> condor_config.INTEL.LINUX
> condor_config.INTEL.WINNT
> 
> LOCAL_CONFIG_FILE = $(ETC)/condor_config.$(ARCHGENERIC).$(OPSYSGENERIC),
\
>                    
                     
      $(ETC)/$(HOSTNAME).local
> 
> instead of
> 
> condor_config.SUN5x.SOLARIS25
> condor_config.SUN4x.SOLARIS25
> condor_config.SUN4x.SOLARIS26
> condor_config.INTEL.LINUX
> condor_config.INTEL.WINNT51
> condor_config.INTEL.WINNT52
> condor_config.INTEL.WINNT60
> condor_config.INTEL.WINNT61
> 
> LOCAL_CONFIG_FILE = $(ETC)/condor_config.$(ARCH).$(OPSYS), \
>                    
$(ETC)/$(HOSTNAME).local
> 
> where the WINNTnn are really copies of WINNT51 !
> 
> It will be helpful to simplify its usage. Any suggestions? If not
> available yet, could it be included in a future Condor version?
> 
> Thanks, Klaus

Other than doing what Dan mentioned, you can define ArchGeneric and OpSysGeneric
yourself, e.g.

ArchGeneric = SUN
OpSysGeneric = WINNT
STARTD_ATTRS = ArchGeneric, OpSysGeneric
LOCAL_CONFIG_FILE = $(ETC)/condor_config.$(ArchGeneric).$(OpSysGeneric),
$(ETC)/$(HOSTNAME).local

This gives you ArchGeneric and OpSysGeneric attributes on all your slots,
useful for Requirements expressions, and lets you specify the local config
file using the same values.

It requires that you have a different global condor_config file for each
ArchGeneric/OpSysGeneric combination that makes sense (I'd like to see
SUN.WINNT running).

You could probably write a boot script that modified condor_config to set
*Generic in some expected way.

Best,


matt
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at: 
https://lists.cs.wisc.edu/archive/condor-users/

---

This message is intended solely for the
use of its addressee and may contain privileged or confidential information.
All information contained herein shall be treated as confidential and shall
not be disclosed to any third party without Embraer’s prior written approval.
If you are not the addressee you should not distribute, copy or file this
message. In this case, please notify the sender and destroy its contents
immediately.
Esta mensagem é para uso exclusivo de seu destinatário e pode conter informações
privilegiadas e confidenciais. Todas as informações aqui contidas devem
ser tratadas como confidenciais e não devem ser divulgadas a terceiros
sem o prévio consentimento por escrito da Embraer. Se você não é o destinatário
não deve distribuir, copiar ou arquivar a mensagem. Neste caso, por favor,
notifique o remetente da mesma e destrua imediatamente a mensagem._______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at: 
https://lists.cs.wisc.edu/archive/condor-users/

---

This message is intended solely for the
use of its addressee and may contain privileged or confidential information.
All information contained herein shall be treated as confidential and shall
not be disclosed to any third party without Embraer’s prior written approval.
If you are not the addressee you should not distribute, copy or file this
message. In this case, please notify the sender and destroy its contents
immediately.
Esta mensagem é para uso exclusivo de seu destinatário e pode conter informações
privilegiadas e confidenciais. Todas as informações aqui contidas devem
ser tratadas como confidenciais e não devem ser divulgadas a terceiros
sem o prévio consentimento por escrito da Embraer. Se você não é o destinatário
não deve distribuir, copiar ou arquivar a mensagem. Neste caso, por favor,
notifique o remetente da mesma e destrua imediatamente a mensagem.