[Swift-devel] iPython parallel coasters

[Tim Armstrong]

Sure, I just think the problem is that it hasn't been an urgent priority
for anyone.  I don't think there's a blocking problem it's just a bunch of
integration and testing work to get it going well.  I was planning to do
the bits I need to do over the summer and start bugging people about it as
well.


On Thu, May 29, 2014 at 3:43 PM, Michael Wilde <wilde at anl.gov> wrote:

>
> On 5/29/14, 3:32 PM, Tim Armstrong wrote:
>
>> Aside from It seems that it would be difficult (impossible?) to build
>> things like provider staging on top of this.
>>
> I'd envision using GridFTP for staging; it seems to be well-callable from
> Python, as demonstrated by the GO transfer client (as well as, I think,
> SAGA).
>
> Having said all that - and started this thread - I'd also like to see the
> coaster binding to Swift/T actually work to the point of user-readiness.
>
> I've got to believe, Mihael, Justin, Tim, and Yadu, that if you set your
> mind to this and worked closely on it, you could jointly break through all
> current problems and actually make this work, provider-staging included.
>
> - Mike
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20140529/25342eec/attachment.html>