<div dir="ltr">Hi Doug,<div><br></div><div>Nice idea! I initially thought a notebook or perhaps an additional tab in the notebook would be a good way for these features to be introduced. Maybe that could be down the line with some support. For now I am focused on some basic command line tools. </div>
<div><br></div><div>I think once I get a good test framework going it will be easy enough to prototype a few additional ideas and notebooks are a good way of doing that. </div><div><br></div><div>I think the next step for me is to write a layer of indirection over the client code so that I can have a common base for GUI and command line interfaces (keen to make ipcluster_cli).</div>
<div><br></div><div>At the moment the watcher tool is *very* basic but that will improve as I have time. I would appreciate any help, I think the IPython parallel framework is excellent!</div><div class="gmail_extra"><br clear="all">
<div>Cheers,</div><div><br></div><div>Nathan.</div><br><div class="gmail_quote">On 21 April 2014 22:33, Doug Blank <span dir="ltr"><<a href="mailto:doug.blank@gmail.com" target="_blank">doug.blank@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Nathan, thanks for making this, and sharing! <div>
<br></div><div>Would it be possible to make this type of code run in a notebook itself? I know the GUI allows listing, selection of items, and possibly selection of items for additional detail/control. But it might be a nice use-case to see if you make the new widgets do what you want, and if not, what is missing.</div>
<div><br></div><div>I'm looking forward to trying this out (and perhaps helping), especially once we get our 3rd party kernel working with the parallel/distributed interface.</div><span class=""><font color="#888888"><div>
<br></div><div>-Doug</div></font></span></div><div class=""><div class="h5">
<div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Apr 19, 2014 at 11:46 PM, Nathan Faggian <span dir="ltr"><<a href="mailto:nathan.faggian@gmail.com" target="_blank">nathan.faggian@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi, <div><br></div><div>I have started a small (spare time) project called "ipcluster_tools", which is available here:</div>
<div> <a href="https://github.com/nfaggian/ipcluster_tools" target="_blank">https://github.com/nfaggian/ipcluster_tools</a><br>
</div><div><br></div><div>Using the client connection it is pretty easy to poll the state of the cluster thanks to the advice from MinRk. Using this knowledge I built a *very* basic tool to visualise the state of jobs but I would really like to try and write some tests now. </div>
<div><br></div><div>Any pointers would be great -- so far I have just used a notebook to inject jobs and used the graphical interface to spin up workers. Since I prefer pytest I would like to try and make something like a "funcarg" that spins up a server (prefer function scope) but the setup and tear-down may be expensive: </div>
<div> </div><div> <a href="http://pytest.org/latest/funcargs.html" target="_blank">http://pytest.org/latest/funcargs.html</a><br></div><div><br></div><div>When I get the tests going to a reasonable level I will change the way that the watcher works. The goal is to (if there is a backend that stores information) be able to introspect metadata also. </div>
<div><br></div><div>If anyone is keen to help out please fork the repository!</div><div><br></div><div>Cheers,</div><div><br></div><div>Nathan</div><div><div><div><br></div><div><div class="gmail_extra"><div class="gmail_quote">
On 16 April 2014 12:18, Nathan Faggian <span dir="ltr"><<a href="mailto:nathan.faggian@gmail.com" target="_blank">nathan.faggian@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi MinRk, <div><br></div><div>Thanks for the quick response, that is going to be a great help!</div>
<div><br></div><div>Cheers,</div><div><br></div><div>Nathan.</div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">
On 16 April 2014 12:01, MinRK <span dir="ltr"><<a href="mailto:benjaminrk@gmail.com" target="_blank">benjaminrk@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">The method you are probably interested in is `Client.queue_status(verbose=True)`, which lets you see at what jobs are queued, running, etc. and where. If you want to resubmit a job, you would use the `resubmit` method, or abort a queued job with `abort`. Do note that killing isn't supported yet in IPython, though you can probably set this up fairly easily (trivially, if all your engines are local), as described here:<div>
<br></div><div><a href="http://mail.scipy.org/pipermail/ipython-dev/2014-March/013426.html" target="_blank">http://mail.scipy.org/pipermail/ipython-dev/2014-March/013426.html</a><br></div><div><br></div></div><div class="gmail_extra">
<br>
<br><div class="gmail_quote"><div><div>On Tue, Apr 15, 2014 at 6:51 PM, Nathan Faggian <span dir="ltr"><<a href="mailto:nathan.faggian@gmail.com" target="_blank">nathan.faggian@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div>
<div dir="ltr">Hi, <div><br></div><div>I am interested in building an ipengine status tool for IPython using Qt. I was wondering if I could get some direction on querying the HUB to get a list of jobs, I have read the "iopubwatcher" example from MinRk, which seems like a good starting point. </div>
<div><br></div><div>Though, I am not sure if I should be using the interface provided by the client for this task because it seems like two clients don't share metadata - one client doesn't know what the other has submitted (I may easily be wrong here).</div>
<div><br></div><div>Hope my question isn't too vague -- I am interested in being able to point and click on jobs and perform some simple things like kill/re-submit them - it would be really useful!</div><div><br></div>
<div>Thanks in advance for any advice, </div><span><font color="#888888"><div><br></div><div>Nathan.</div><div><br></div></font></span></div>
<br></div></div>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org" target="_blank">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org" target="_blank">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
<br></blockquote></div><br></div></div></div></div></div>
</blockquote></div> </div></div></div></div></div>
<br>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org" target="_blank">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br></blockquote></div></div></div>