[IPython-dev] IPython AWS Extension
Carl Smith
carl.input at gmail.com
Sat Jun 30 14:49:16 EDT 2012
This is one of the things I'm looking at currently. I'm playing with having
an S2 based config that all instances for that user share. Then having a
magic for mounting volumes to the filesystem. On a new instance, you'd just
do something like
%aws -m myvol ~/carl
and it'd mount myvol and set it up to auto mount on reboot until/unless you
said not to.
This is going to be the approach for all new features I'm thinking.
This way users can edit the code and I can hopefully divide the feature set
into gists and get some help from IPython users that want low barrier to
entry, one file problems to play with.
On Jun 30, 2012 6:08 PM, "Fernando Perez" <fperez.net at gmail.com> wrote:
> Hi Carl,
>
> On Sat, Jun 30, 2012 at 8:02 AM, Carl Smith <carl.input at gmail.com> wrote:
> > I've been looking at where to go with the NotebookCloud app I've been
> > working on and decided it would better to add new features to the user's
> > IPython setup, rather than NBC itself.
> >
> > The AMI includes boto already, a Python AWS library, and it's very good,
> but
> > it can still often take a while to get anything done. Mounting a dataset
> for
> > example.
> >
> > Now, I'm looking to write a library for the AMI that makes AWS easier to
> use
> > from the Notebook.
> >
> > Does this sound like the best way to go?
>
> That definitely sounds useful; I still think that easy, persistent
> storage support for the user's notebooks at least, but home directory
> ideally, would be good to have.
>
> Cheers,
>
> f
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20120630/fc43b534/attachment.html>
More information about the IPython-dev
mailing list