I think it would be better to set
OPSYS = WINDOWS
in the configuration file for all of your pre-7.7 Windows nodes. rather
than defining your own OpSysGeneric and ArchGeneric.
The fact that OpSysGeneric was defeating the default
inclusion of OpSys in Requirements was unintentional.
I would call it a bug that we fixed, except until this moment I
didn't even know that this behavior existed.
Alternatively, you can use a regular _expression_ to match of the WIN*
machines, This is what I usually use:
Requirements = Arch != "ARM" &&
regexp("^WIN",OpSys)
-tj
TJ,
I know that, but for older
versions
this lead to a requirements _expression_ as follow:
Requirements = (OpSys ==
"WINNT51""
|| OpSys == "WINNT52" || OpSys == "WINNT60" || OpSys
== "WINNT61") && (Arch == "INTEL" || Arch ==
"X86_64")
that is to long and to make it
easier
for the user I created ArchGeneric = "INTEL" and OpSysGeneric
= "WINNT" and so the requirements expressions becomes
Requirements = (OpsysGeneric ==
"WINNT")
&& (ArchGeneric == "INTEL")
and in the presence of any OpSys*
and
Arch*, parameters OpSys and Arch (respectively) were not
automatically
added to the requirements _expression_ (Look in my previous email
the output
for condor_q -analyze for version 7.6.6 that shows this
behavior). When
I omit any OpSys* and Arch* parameter, then Arch and Opsys were
included
automatically.
Now in version 7.8.x series this
behavior
seems to have been changed and this makes the requirements
_expression_ longer
to include the new OpSys (WINDOWS) and Arch (INTEL and X86_64).
Is there any way to have the
older behavior
working in the new 7.8.x series of HTCondor?
Klaus
You can defeat the automatic addition of
Target.Arch and
Target.OpSys in V7.8 by adding your own
statements to the Requirements _expression_ that reference these
attributes.
Requirements = Target.Arch != "Atom" &&
Target.OpSys != "LINUX"
For instance.
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/
_______________________________________________
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/
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/
|