[Swift-devel] swift-on-ec2

[Ioan Raicu]

If a LRM can be configured by the virtual workspace service as part of 
the VMs, then its even easier for Falkon to work!  I don't see an LRM as 
being central and necessary though, as when the VM starts up, we could 
easily bootstrap the Falkon executors to start up and live forever (or 
at least while the VM is running).  We could host the disptacher 
off-site, or even on another EC2 VM... it all depends on how much the 
latency seems to affect Falkon performance. 

I assume that EC2 VMs have a public IP space that is not behind some 
site-wide firewall, right?  If not, then this could be a problem.

Ioan

Ben Clifford wrote:
> On Wed, 16 May 2007, Ian Foster wrote:
>
>   
>> If we configure the virtual cluster with a full LRM, as you propose (and 
>> it seems have already done--great work!), then we can use this to start 
>> Falkon executors--as we do today on regular clusters. So it seems to me 
>> that we have all we need. How about you and Ioan spend your time on 
>> Thursday running something on EC2, to make sure it sorks?
>>     
>
>   
>> Regarding choice of LRM: have you looked at SGE? That is what quite a 
>> few others seem to be using.
>>     
>
> That's probably a bunch of most unnecessary extra weight (== trouble) if 
> the images are specifically intended for use as swift+falkon. But useful 
> to have round if people want to do other things too.
>
>   

-- 
============================================
Ioan Raicu
Ph.D. Student
============================================
Distributed Systems Laboratory
Computer Science Department
University of Chicago
1100 E. 58th Street, Ryerson Hall
Chicago, IL 60637
============================================
Email: iraicu at cs.uchicago.edu
Web:   http://www.cs.uchicago.edu/~iraicu
       http://dsl.cs.uchicago.edu/
============================================
============================================

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20070516/54ae78bc/attachment.html>