[IPython-dev] IPython notebook on Windows Azure

Fernando Perez fperez.net at gmail.com
Thu Jun 7 21:10:29 EDT 2012

On Thu, Jun 7, 2012 at 3:17 PM, Thomas Kluyver <takowl at gmail.com> wrote:
> Ah, apologies for stealing your thunder ;-). There was a bit of buzz
> about Linux instances on Azure, which made me go and look at it.

We were also busy today turning in a report for a grant that has
funded much of the recent parallel work, so we just didn't have any
time to do decent PR, thanks for pitching in, actually!

> We should make sure this - and equivalent instructions for AWS - are
> clearly linked from our own site.

By all means do so, if you have a minute.  If not I'll try to spend
some time on the site this weekend.

> Also, if we're getting people to install from master, we should think
> a bit about the future:
> - These docs will probably be around for some time: will we always
> recommend installing unreleased versions, or is that just while the
> notebook is still improving so rapidly?

I'd hope that will change over time and we'll settle into a slower
pace, but we're not there yet.  Note that we can update these
instructions as well (not immediately, but we can feed updates to MS
on them, it was actually a very nice workflow with markdown docs on
github, believe it or not.  As Brian says, the azure stuff has come a
*long* ways, and in more than one aspect it was much nicer to set up
than Amazon is).

One thing we didn't know (or maybe it wasn't available when we set
things up, I'm honestly not sure) was that it's possible to freeze the
instances and offer them up.  What I'd like to do is eventually to
offer stable instances with ubuntu and windows and everything
pre-loaded, from a reasonably solid version (even if it's a git master
checkout, but at least one *we* are sure of).  Just like Justin does
with Starcluster.

During the introduction today I saw how to do it, and it was very
straightforward, I just wasn't aware of this before.  We'll look into
it soon.

> - What's the upgrade situation? We could easily end up with lots of
> people running arbitrary development releases from whichever day they
> ran the setup, with no obvious 'update' command.

git pull, baby :)

> For the latter point, I think Ubuntu with Julian's ipython-dev PPA is
> a decent answer. It delivers new versions automatically, but if we
> break something and the tests fail, no new package is built until the
> tests are passing again. It also simplifies installation, because it
> automatically pulls in pyzmq and tornado.

True.  When we set things up, the ubuntu images weren't ready yet so
we had to go with Suse; today I would have used ubuntu, obviously.



More information about the IPython-dev mailing list