[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] Requirements automatic settings changed in V7.8.6?




Todd,

Thanks for your refreshing on OpSys and how it could be defined. But essentially this is not my question.
My question is why the behavior of adding OpSys and Arch into the requirements _expression_ was changed.

In versions previous to v7.8.x, if I create an OpSys* macro (in our case OpSysGeneric = "WINNT"), the OpSys macro is not included in the requirements, and is only included in the absence of any OpSys* macro. In version 7.8.x something was changed and the default behavior is to include OpSys even when I include OpSys* (OpSysGeneric in our case). The same happens with Arch* macro (ArchGeneric = "INTEL").

A job submitted to v7.6.6 shows the following result for condor_q -analyze:

 The Requirements _expression_ for your job is:

( ( target.ArchGeneric == "INTEL" && target.OpSysGeneric == "WINNT" ) &&
( target.Machine == "PC315284.corp.ad.emb" ) ) && ( TARGET.Disk >=
DiskUsage ) &&
( ( TARGET.Memory * 1024 ) >= ImageSize ) &&
( ( RequestMemory * 1024 ) >= ImageSize ) && ( TARGET.HasFileTransfer )

and for version 7.8.6 shows:

 The Requirements _expression_ for your job is:

( ( target.ArchGeneric == "INTEL" && target.OpSysGeneric == "WINNT" ) &&
( target.Machine == "PC315284.corp.ad.emb" ) ) && ( TARGET.Arch ==
"X86_64" ) &&
( TARGET.OpSys == "WINDOWS" ) && ( TARGET.Disk >= RequestDisk ) &&
( TARGET.Memory >= RequestMemory ) &&
( ( TARGET.HasFileTransfer ) || ( TARGET.FileSystemDomain ==
MY.FileSystemDomain ) )


My questions are:
1) Is there any strong reason for this change in the automatic _expression_ inclusion?
2) Is there any way to have the prior behavior working in v7.8.x?

If not, there is only one way to proceed: I should forget the old local settings and explicitly define all OpSys and Arch possibilities in the Requirements _expression_ when my executable is 32 bits and could run on any version of Windows and Condor version.

Best regards,
Klaus




Todd Tannenbaum <tannenba@xxxxxxxxxxx>

18/12/2012 15:46

To
HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
cc
kschwarz@xxxxxxxxxxxxxx, condor-users@xxxxxxxxxxx
Subject
Re: [HTCondor-users] Requirements automatic settings changed in V7.8.6?





Essentially, by default in v7.6.x on Windows set OpSys to be a specific
flavor of Windows, e.g.

   OpSys = WINNT51

and now in v7.8.x, OpSys is just set to be Windows by default (which is
what most users wanted, because for the most part all the different
versions of windows behave the same), and there are a bunch of
additional attributes with more detailed information designed to be used
easily with requirements, e.g.
   OpSys = "WINDOWS"
   OpSysLegacy = "WINNT61"
   OpSysName = "Windows7"
   OpSysMajorVer = 601
   OpSysShortName = "Win7"
   OpSysAndVer = "WINDOWS601"
   OpSysVer = 601
   OpSysLongName = "Windows 7 SP1"

An important point to know is that OpSys can be specified in your config
file - HTCondor only sets OpSys up to a default if it is unspecified.
What changed in v7.6 to v7.8 is the default value for OpSys.  So Klaus,
perhaps all you want to do is put an entry in your condor_config on your
v7.8 machines to override OpSys to be what you want, aka what it was in
v7.6.  So you could put in your condor_config

  OpSys = WINNT51

or whatever.  This specified value for OpSys will also be picked up by
condor_submit when it writes the default requirements.

Hope the above helps,
Todd


On 12/14/2012 11:43 AM, kschwarz@xxxxxxxxxxxxxx wrote:
>
> Hi,
>
> I am having problem with the automatic Requirements generated in the
> v7.8.6. When I submit a job from my PC using version 7.6.6 the
> Requirements _expression_ obtained using condor_q -analyze command is as
> follow:
>
> C:\_WORKAREA\__DEV__\04-v7.8.6\01-00-simple>condor_q -ana
>
>
> -- Submitter: PC303344.corp.ad.emb : <10.3.28.200:21942> :
> PC303344.corp.ad.emb
> ---
> 001.000:  Run analysis summary.  Of 1123 machines,
>     1123 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 match but are currently offline
>        0 are available to run your job
>          No successful match recorded.
>          Last failed match: Fri Dec 14 15:26:54 2012
>          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.Machine == "PC315284.corp.ad.emb" ) ) && ( TARGET.Disk >=
> DiskUsage ) &&
> ( ( TARGET.Memory * 1024 ) >= ImageSize ) &&
> ( ( RequestMemory * 1024 ) >= ImageSize ) && ( TARGET.HasFileTransfer )
>
>      Condition                 Machines Matched    Suggestion
>      ---------                 ----------------    ----------
> 1   ( target.Machine == "PC315284.corp.ad.emb" )0
> MODIFY TO "NB341776.corp.ad.emb"
> 2   ( TARGET.Disk >= 1 )        1122
> 3   target.ArchGeneric == "INTEL"   1123
> 4   target.OpSysGeneric == "WINNT"    1123
> 5   ( ( 1024 * TARGET.Memory ) >= 1 ) 1123
> 6   ( ( 1024 * ceiling(ifThenElse(JobVMMemory isnt
> undefined,JobVMMemory,9.765625000000000E-004)) ) >= 1 )
> 1123
> 7   ( TARGET.HasFileTransfer )    1123
>
> C:\_WORKAREA\__DEV__\04-v7.8.6\01-00-simple>
>
>
>
> Now when I submit the same job using version 7.8.6, the output of
> condor_q -analyze is:
>
>
> C:\_WORKAREA\__DEV__\04-v7.8.6\01-00-simple>condor_q -ana
>
>
> -- Submitter: PC303344.corp.ad.emb : <10.3.28.200:43344> :
> PC303344.corp.ad.emb
> ---
> 002.000:  Run analysis summary.  Of 21 machines,
>       21 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 match but are currently offline
>        0 are available to run your job
>          No successful match recorded.
>          Last failed match: Fri Dec 14 15:04:27 2012
>
>          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.Machine == "PC315284.corp.ad.emb" ) ) && ( TARGET.Arch ==
> "X86_64" ) &&
> ( TARGET.OpSys == "WINDOWS" ) && ( TARGET.Disk >= RequestDisk ) &&
> ( TARGET.Memory >= RequestMemory ) &&
> ( ( TARGET.HasFileTransfer ) || ( TARGET.FileSystemDomain ==
> MY.FileSystemDomain ) )
>
>      Condition                 Machines Matched    Suggestion
>      ---------                 ----------------    ----------
> 1   ( target.Machine == "PC315284.corp.ad.emb" )2
> 2   ( TARGET.OpSys == "WINDOWS" )   14                  MODIFY TO "WINNT52"
> 3   target.OpSysGeneric == "WINNT"    20
> 4   target.ArchGeneric == "INTEL"   21
> 5   ( TARGET.Arch == "X86_64" )     21
> 6   ( TARGET.Disk >= 1 )        21
> 7   ( TARGET.Memory >= ifthenelse(MemoryUsage isnt
> undefined,MemoryUsage,1) )
> 21
> 8   ( ( TARGET.HasFileTransfer ) || ( TARGET.FileSystemDomain ==
> "PC303344.corp.ad.emb" ) )
> 21
>
> Conflicts:
>
>    conditions: 1, 2
> ERROR "Assertion ERROR on (current != dummy)" at line 519 in file
> c:\condor\execute\dir_1816\userdir\src\condor_utils\list.h
>
> C:\_WORKAREA\__DEV__\04-v7.8.6\01-00-simple>
>
>
> now the _expression_  ( TARGET.Arch == "X86_64" ) && ( TARGET.OpSys ==
> "WINDOWS" ) appeared, that is not in the previous version.
>
> How can i change this behavior? because we created ArchGeneric and
> OpSysGeneric to deal with the different versions of Windows.
>
> What about the ERROR message in the output for v7.8.6?
>
> Any other suggestion?
>
> Thanks,
> Klaus
> /
> /
> ------------------------------------------------------------------------
> /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./
>
>
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/
>


--
Todd Tannenbaum <tannenba@xxxxxxxxxxx> University of Wisconsin-Madison
Center for High Throughput Computing   Department of Computer Sciences
HTCondor Technical Lead                1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132                  Madison, WI 53706-1685



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.