Re: [Condor-users] Suggestion for change in behaviour for windows Requirements. Was :RE: Problem Submitting Jobs in windows

[Ian Chesal <ICHESAL@xxxxxxxxxx>]

Actually, while we're talking about OpSys limitations: how about some distinctions automatically made for Linux systems? I have to define custom AlteraOperatingSystem and AlteraArchitecture attributes on my machines to tell the difference between a Red Hat Enterprise Linux 4 on 32-bit Intel machine and a Red Hat Enterprise Linux 5 on AMD 64-bit machine. You could use OpSysFamily as Matt suggests and set that to LINUX and then use OpSys to list the *specific* Linux version and distro used.

- Ian

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Matt Hope
Sent: Tuesday, February 24, 2009 10:16 AM
To: Condor-Users Mail List
Subject: [Condor-users] Suggestion for change in behaviour for windows Requirements. Was :RE: Problem Submitting Jobs in windows

I would suggest that, based on the number of times this is asked, the
number of times a job is dependent on a specific version of windows
(heck the number of times it is dependent even on a _minimum_ version of
windows) that this automatic behaviour on windows is NOT a good default.

I suggest that all supported platforms gain a new Attrbute OpSysFamily
For all currently supproted windows releases this would simply be WINNT
(vista hasn't changed enough to merit a distinction, windows 7 certainly
doesn't).
The default behaviour for the Requirements should be that:
If OpSys is specified anywhere in the requirements
    do not nothing
Else If OpSysFamily is specified anywhere in the requirements
    do nothing
Else If OpSysFamily is defined in the config
    add '&& (OpSysFamily == "$OpSysFamily")' to the requirements
Else
    current behaviour i.e. add '&& (OpSys == "$OpSys")'

On windows installs from a 7.odd number release onwards begin including
OpSysFamily in the default config file

If there are a large number of windows users who *don't* want this
behaviour that's fair enough.

If OpSysFaily becomes useful it can be used for other ports. I would
suggest that the standard universe ignores it but I have insufficient
experience in that to know how well standard universes can transition
the sort of version shift that would constitute a change in the OpSys
value anyway.

Matt

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Steil, Joshua
Sent: 23 February 2009 18:16
To: Condor-Users Mail List
Subject: Re: [Condor-users] Problem Submitting Jobs in windows

Okay got it figured out. To run on a non similar system (ie XP to Server
03) you have to specify:
Requirements = OpSys == "WINNT52"
In the submit file.

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Steil, Joshua
Sent: Monday, February 23, 2009 11:54 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] Problem Submitting Jobs in windows

Output from condor_q -l

MyType = "Job"
TargetType = "Machine"
ClusterId = 1
QDate = 1235404846
CompletionDate = 0
Owner = "aersiadm"
NTDomain = "ASI"
WindowsMajorVersion = 5
WindowsMinorVersion = 1
WindowsBuildNumber = 2600
WindowsServicePackMajorVersion = 2
WindowsServicePackMinorVersion = 0
WindowsProductType = 1
RemoteWallClockTime = 0.000000
LocalUserCpu = 0.000000
LocalSysCpu = 0.000000
RemoteUserCpu = 0.000000
RemoteSysCpu = 0.000000
ExitStatus = 0
NumCkpts_RAW = 0
NumCkpts = 0
NumJobStarts = 0
NumRestarts = 0
NumSystemHolds = 0
CommittedTime = 0
TotalSuspensions = 0
LastSuspensionTime = 0
CumulativeSuspensionTime = 0
ExitBySignal = FALSE
CondorVersion = "$CondorVersion: 7.2.1 Feb 19 2009 BuildID: 133382 $"
CondorPlatform = "$CondorPlatform: INTEL-WINNT50 $"
Iwd = "C:\condor\examples\printname"
JobUniverse = 5
Cmd = "C:\condor\examples\printname\printname.bat"
MinHosts = 1
MaxHosts = 1
CurrentHosts = 0
WantRemoteSyscalls = FALSE
WantCheckpoint = FALSE
RequestCpus = 1
JobStatus = 1
EnteredCurrentStatus = 1235404846
JobPrio = 1
NiceUser = FALSE
Env = "path=c:\winnt\system32"
EnvDelim = "|"
JobNotification = 2
WantRemoteIO = TRUE
UserLog = "C:\condor\examples\printname\printname.log"
CoreSize = 0
Rank = 0.000000
In = "/dev/null"
TransferIn = FALSE
Out = "printname.out"
StreamOut = FALSE
Err = "printname.err"
StreamErr = FALSE
BufferSize = 524288
BufferBlockSize = 32768
ShouldTransferFiles = "YES"
WhenToTransferOutput = "ON_EXIT"
TransferFiles = "ONEXIT"
ImageSize_RAW = 1
ImageSize = 1
ExecutableSize_RAW = 1
ExecutableSize = 1
DiskUsage_RAW = 1
DiskUsage = 1
RequestMemory = ceiling(ImageSize / 1024.000000) RequestDisk = DiskUsage
Requirements = (Arch == "INTEL") && (OpSys == "WINNT51") && (Disk >=
DiskUsage) && ((Memory * 1024) >= ImageSize) && (HasFileTransfer)
JobLeaseDuration = 1200 PeriodicHold = FALSE PeriodicRelease = FALSE
PeriodicRemove = FALSE OnExitHold = FALSE OnExitRemove = TRUE
LeaveJobInQueue = FALSE Arguments = ""
GlobalJobId = "Del62.ASI.COM#1.0#1235404846"
ProcId = 0
AutoClusterId = 0
AutoClusterAttrs =
"JobUniverse,LastCheckpointPlatform,NumCkpts,DiskUsage,ImageS
ize,Requirements,NiceUser,ConcurrencyLimits"
WantMatchDiagnostics = TRUE
LastRejMatchReason = "no match found"
LastRejMatchTime = 1235411016
ServerTime = 1235411223

Output from condor_q -ana 1.0

 ID      OWNER            SUBMITTED     RUN_TIME ST PRI SIZE CMD
---
001.000:  Run analysis summary.  Of 32 machines,
     32 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: Mon Feb 23 11:48:37 2009
        Reason for last match failure: no match found
WARNING:  Be advised:
   No resources matched request's constraints
   Check the Requirements expression below:
Requirements = (Arch == "INTEL") && (OpSys == "WINNT51") && (Disk >=
DiskUsage) && ((Memory * 1024) >= ImageSize) && (HasFileTransfer)


So it does seem that condor is requiring that the same architecture be
used. Does anyone know how to bypass this restriction? Or will setting a
requirement in the submit file to require the archetecture type to be
the same as the processing servers be sufficient?
________________________________________
From: condor-users-bounces@xxxxxxxxxxx
[condor-users-bounces@xxxxxxxxxxx] On Behalf Of Steven Timm
[timm@xxxxxxxx]
Sent: Monday, February 23, 2009 11:30 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] Problem Submitting Jobs in windows

On Mon, 23 Feb 2009, Steil, Joshua wrote:

> My current setup is as follows:
> All machines running condor 7.2.1
>
> 1 Condor Master (Master Machine)
> HP Proliant DL380 G4 running Windows Server 2003 32 bit This computer
> is set to submit only and never process.
>
> I have 4 servers (Processing Machines) that I have set up to always
run jobs they are configured as follows:
> Sun Fire x2250 running Windows Server 2003 64 bit These machines are
> set to submit and always process.
>
> I also have 1 test machine (Workstation) setup to submit jobs to the
condor master:
> Dell Precision Workstation running Windows XP 32 bit.
> This machine is set to submit only and never process.
>
> I am currently just running the example job printname. I've modified
the batch script to echo %computername% instead of net name so that I
get valid output.
>
>> From the Master Machine I am able to successfully submit and have
returned to me the example.
>> From the Processing machines I am able to successfully submit and
have returned to the me the example.
>> From the Workstation I can submit, however it never returns, error or
otherwise. I have checked the Master Machine logs and in the "Matchlog"
file I see:
> Rejected 1.0 user@xxxxxxxxxxx <192.168.1.137:3878>: no match found I
> have double checked and I am using the same user account to login and
run the program and the same credentials are being used to execute the
jobs.
> There are no requirements set in the submit file.

What does condor_q -l say on job 1.0?
I am no condor windows guru but I know that condor_submit usually tacks
on an architecture requirement which is equal to the machine on which
condor_submit is run, and if I recall correctly winxp and
win2k3 are different windows architectures according to condor.

What about condor_q -ana 1.0?

Steve



>
> Does anyone know what I'm doing wrong here?
>
>

--
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525
timm@xxxxxxxx  http://home.fnal.gov/~timm/ Fermilab Computing Division,
Scientific Computing Facilities, Grid Facilities Department, FermiGrid
Services Group, Assistant Group Leader.
_______________________________________________
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/
_______________________________________________
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/
_______________________________________________
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/

----
Gloucester Research Limited believes the information provided herein is reliable. While every care has been taken to ensure accuracy, the information is furnished to the recipients with no warranty as to the completeness and accuracy of its contents and on condition that any errors or omissions shall not be made the basis for any claim, demand or cause for action.
The information in this email is intended only for the named recipient.  If you are not the intended recipient please notify us immediately and do not copy, distribute or take action based on this e-mail.
All messages sent to and from this email address will be logged by Gloucester Research Ltd and are subject to archival storage, monitoring, review and disclosure.
Gloucester Research Limited, 5th Floor, Whittington House, 19-30 Alfred Place, London WC1E 7EA.
Gloucester Research Limited is a company registered in England and Wales with company number 04267560.
----

_______________________________________________
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/


Confidentiality Notice.
This message may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution,  or copying  of this message, or any attachments, is strictly prohibited.  If you have received this message in error, please advise the sender by reply e-mail, and delete the message and any attachments.  Thank you.