[DRMAA-WG] maxSlots attribute

[Daniel Templeton]

Beyond being related to the parallel environments, slot availability is 
also governed by resource quota sets.  Note that slots in SGE are both a 
queue-level and host-level concept.  A single host might have two 
queues, each with 4 slots, but the host itself offers only 6.  That 
means two queue slots will always be empty, but which queue has them 
depends on the order the jobs are assigned.  Hence my previously stated 
reservations about including a queue concept.

Daniel

On 03/22/10 06:05, Daniel Gruber wrote:
> In SGE minSlots and maxSlots are in tight relation to the parallel
> environment
> which is reflected in the new standard with an configuration name. This
> inter-attribute dependency does not look like a very clean approach, which
> I mentioned also in the meeting.
> Regarding SGE minSlots,maxSlots and the queue name have not a mandatory
> relationship which means that selecting a special queue is not necessary
> in order
> to use the slots attribute.
>
> Regards
>
> Daniel
>
>
> On 03/22/10 13:53, Peter Tröger wrote:
>> Hi,
>>
>> with the latest decision from OGF28, we now have the queueMaxSlotsAllowed attribute in the MonitoringSession interface.
>>
>> Under this impression, I meanwhile wonder about the relation between minSlots / maxSlots and the (also newly added) queueName attribute in the job template. Can you specify minSlots / maxSlots without configuring a queueName to use ? And if yes, don't we need an according maxSlotsAllowed on DRM system level then  ?
>>
>> Best,
>> Peter.
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> --
>>    drmaa-wg mailing list
>>    drmaa-wg at ogf.org
>>    http://www.ogf.org/mailman/listinfo/drmaa-wg
>>
>
>
>
> --
>    drmaa-wg mailing list
>    drmaa-wg at ogf.org
>    http://www.ogf.org/mailman/listinfo/drmaa-wg