[jsdl-wg] IndividualCPUCount

Andreas Savva andreas.savva at jp.fujitsu.com
Tue Aug 22 04:30:48 CDT 2006


Could you put this on the errata tracker so we don't forget?

I think you are reading a lot more into the difference in wording than
was intended.

Andreas

Peter G. Lane wrote:
> Would it be possible to change the description of IndividualCPUCount to
> say simply that it specifies the required number of CPUs instead of the
> number to be allocated. The way it's worded now, match making based on
> the actual number of CPUs (i.e Condor) seems improperly represented by
> this element. Making it a little more general allows for the
> interpretation that a host must at very least have a certain number of
> CPUs, but it does not dictate the number of CPUs actually being
> allocated for the job. Resource managers such as LSF and PBS that only
> operate using CPU allocations could still be considered included in the
> description because if an allocation is successful then obviously the
> host must have that many CPUs.
> 
> In addition, the following elements are worded similarly to
> IndividualCPUCount so as to effectively prohibit purely match making as
> opposed to strict allocation of host resources:
> 
> IndividualVirtualMemory
> IndividualDiskSpace
> TotalDiskSpace
> 
> For what it's worth, the rest of Resources' elements seem to be worded
> more generally (i.e. "required by the job" as opposed to "allocated to
> the job"). Derive from that what you will. ;-)
> 
> Peter

-- 
Andreas Savva
Fujitsu Laboratories Ltd





More information about the jsdl-wg mailing list