[Swift-devel] testing

[Michael Wilde]

Also, please put in this description the requirements that we're working 
under:

- node IP connectivity
- security
- central (head) node load limits
- central (head) node job time limits
   (eg managed headnodes)
- accounting info for all resources used
   (ie generates OSG accounting records)
- etc

That will help the design converge.

On 3/18/09 12:18 PM, Michael Wilde wrote:
> Mihael, please create a design note on how coaster bootstrap and 
> communication works, and use that as the basis for getting agreement on 
> the approach and the range of options needed, and for getting input.
> 
> That design description probably exists in various material you have, 
> and can be brief.
> 
> On 3/18/09 10:40 AM, Mihael Hategan wrote:
>> On Wed, 2009-03-18 at 15:20 +0000, Ben Clifford wrote:
>>> On Wed, 18 Mar 2009, Mihael Hategan wrote:
>>>
>>>> Ben, the point is to run with one of the scheduler providers, not 
>>>> gram2.
>>> That is also bad for OSG, as far as I can tell because it screws up 
>>> accounting which is done in GRAM, not in the LRM.
>>>
>>> Pretty much what I'm asserting is that both the head job and the 
>>> worker jobs need to be run through Conodr-G/gridmanager/gram2 (in my 
>>> understanding of what OSG requires).
>>>
>>
>> Ok. Back to the drawing board.
>>
>>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel