[Swift-devel] Re: coaster features

Zhao Zhang zhaozhang at uchicago.edu
Thu May 14 11:36:14 CDT 2009


Cool, Thanks, Mihael.

Mihael Hategan wrote:
> On Thu, 2009-05-14 at 09:56 -0500, Zhao Zhang wrote:
>   
>> Hi, Mihael
>>
>> I am making a coaster test plan now, so that will be good if you could 
>> help me clear what features of coaster are available in the current 
>> implementation.
>>
>> 1) Multiple coaster on 1 compute node.
>>     This feature is documented, but I am not sure if is working or not.
>>     
>
> Yes, this is supposed to work.
>
>   
>> 2) coasterWorkerMaxwalltime
>>     This is working.
>> 3) coasterInternalIP
>>     I know this one is working, as I have already complete tests with 
>> this parameter.
>>     I am not clear under what context do we need this feature. One I 
>> could think of is that "using notification instead of status file". Is 
>> there any other
>>     condition or any specific site requires this feature?
>>     
>
> I'm not sure how you know it's working if you don't know what it's
> supposed to do.
>   
Yes, there is a test case in Ben's test suite using the 
coasterInternalIP variable. Things I know is that the test returned 
successful.
> Without this, workers use the external IP (the one the service is
> started with) to contact the service. With it, one can force the workers
> to contact a specific IP after starting. This is needed if the worker
> nodes don't generally have access to the outside of the cluster.
>
> This has nothing to do with notification or status files. If this
> setting is required (due to the network configuration of the cluster)
> and it is not specified, the coasters won't work at all.
>
>   
>> 4) coasterDataProvider
>>     This is working now.
>>     
>
> I don't know what that is.
>   
This is the "<filesystem provider="coaster" url="gt2://grid.myhost.org" 
/>" from http://www.ci.uchicago.edu/swift/guides/userguide/coasters.php.

zhao
>   
>> 5) Block Allocation
>>     Is this being implemented soon, or do we decide to postpone this 
>> feature?
>>     
>
> The priority of this item has, again, become the highest.
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>   



More information about the Swift-devel mailing list