[Swift-devel] iPython parallel coasters

[Tim Armstrong]

So you're suggesting to try to speak the IPython protocol and somehow
thread task descriptions through that and run the command-line app on the
other end?

It's partially documented but they seem a little vague about backwards
compatibility and whether it's an official public interface.
http://ipython.org/ipython-doc/2/development/messaging.html

Aside from It seems that it would be difficult (impossible?) to build
things like provider staging on top of this.

I just tend to think that trying to integrate with existing code causes at
least as many problems as it solves unless the other system was really
carefully designed to be a building block for other systems.  The design
seems to assume throughout that your tasks are going to be a Python
function.  If anything we might want something that provides lower-level
functionality that isn't specialised for running Python functions.

- Tim



On Thu, May 29, 2014 at 1:47 PM, Mihael Hategan <hategan at mcs.anl.gov> wrote:

> I was exploring AMQP as an alternative to writing my own protocol (which
> turned out to be coasters) somewhere before I started working on Swift.
> In spirit, it seemed to do exactly what I wanted. Unfortunately, there
> were no reasonable implementations at the time, which I see has changed.
>
> So I do think this is worth exploring although I'm not quite sure about
> the moving parts part. The outsides of things can be deceiving.
>
> Mihael
>
> On Thu, 2014-05-29 at 10:47 -0500, Michael Wilde wrote:
> > [Moving this part of the discussion to a new thread.]
> >
> > Seems like less moving parts than coasters: it would all be in Python
> > (instead of Java + Perl); would have iPython community support; and
> > would be based on a standard protocol (ZeroMQ implementation of AMQP).
> >
> > iPython parallel has almost the exact same process architecture as Swift
> > Coasters.
> >
> > Seemed worth exploring.
> >
> > - Mike
> >
> > On 5/29/14, 10:28 AM, Tim Armstrong wrote:
> > > ...
> > >
> > > What's the motivation for the IPython idea? It feels like a lot of
> moving
> > > parts to me.
> > >
> > > - TIm
> > >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20140529/24dbdd18/attachment.html>