<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi Brian,<br>
<br>
I checked the various PaaS platforms, almost all expect wsgi
python httpservers so that rules of ipython. Openshift allows
anything that speaks http but doesnt do websockets. I have an
openshift app of ipython that will fail at the websocket level.
dotCloud is the only one that plays well with ipython, the reason
being that their platform is based on zeromq.</tt><br>
<tt>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<br>
See;<br>
<a class="moz-txt-link-freetext" href="http://github.com/dotcloud/zerorpc-python">http://github.com/dotcloud/zerorpc-python</a><br>
<br>
<a
href="http://pycon-2012-notes.readthedocs.org/en/latest/dotcloud_zerorpc.html">http://pycon-2012-notes.readthedocs.org/en/latest/dotcloud_zerorpc.htm</a><br>
<br>
<br>
Shoibal.<br>
<br>
<br>
</tt>
<div class="moz-cite-prefix">On 09/05/2012 06:58 PM, Brian Granger
wrote:<br>
</div>
<blockquote
cite="mid:CAH4pYpR111aVcdgQo2+kNnta5xszOAtg+ij4DOBfFqO+KJYDXw@mail.gmail.com"
type="cite">
<pre wrap="">Shoibal,
Hi, these are things we are interested in. There are a number of
different issues you are bringing up:
* Making the notebook server multiuser aware. This is definitely on
our radar and we are trying to get this work funded through academic
grants. We are at the early stages of the planning of this.
* Running the notebook server on PaaS platforms. This is an entirely
separate issue that we will have to revisit in the future - stay tuned
for more on this in the coming months. One issue you will run into
though is that we rely on zeromq/pyzmq which definitely doesn't run on
most of the Paas vendors I know of.
Cheers,
Brian
On Wed, Sep 5, 2012 at 6:09 AM, Shoibal Chakravarty <a class="moz-txt-link-rfc2396E" href="mailto:shoibalc@gmail.com"><shoibalc@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I just got interested in the possibility of getting ipython html notebook
server on the various Platform as a Service (PaaS) ideas out there:
Openshift, dotcloud, heroku, appfog etc. I was interested in seeing if I
could get people to try out my other python projects [energy economics
modeling] without having to take the trouble of downloading and compiling a
lot of different packages. I would put everything required on one of these
free PaaS services and have them try it out via the ipython notebook
interface.
Carl Smith's notebookcloud (<a class="moz-txt-link-freetext" href="http://github.com/carlsmith">http://github.com/carlsmith</a>) was another
inspiration. The PaaS approach is a baby version of the AMI approach of
notebookcloud. I let the PaaS vendors take care of the building and
maintaining the AWS infrastructure. It also happens to be completely free
for small applications.
Most of the Paas services do not support websockets and and often expect
only wsgi compliant python web servers. Only dotcloud
(<a class="moz-txt-link-freetext" href="http://www.dotcloud.com/">http://www.dotcloud.com/</a>) seems to work for now with tornado and
websockets. See <a class="moz-txt-link-freetext" href="http://github.com/shoibalc/ipynbserver-dotcloud">http://github.com/shoibalc/ipynbserver-dotcloud</a>.
I am still concerned about security implications of the notebook server.
Ideally, I would like the following:
1. Let anybody login with a login/passwd or the various authentication
services.
2. Give them a secure walled-in temporary directory to work in, with
restricted shell function access.
3. Limit resources they use (memory, CPU load etc) and automatically log
them out if the violate this.
4. Limit sessions to xx minutes.
5. Set up a parallel database service for authentication and to let users
save their notebooks etc. (eg, MongoDB uses json as storage)
Which of these would be easily feasible? Especially point 2. Sage seems to
create (and later destroy) a temporary working directory for each cell and
severely limits shell access. One directory per login with limited outside
access might be better.
Please let me know what ideas/suggestions you have. Thanks a lot for
ipython!
-Shoibal.
_______________________________________________
IPython-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a>
<a class="moz-txt-link-freetext" href="http://mail.scipy.org/mailman/listinfo/ipython-dev">http://mail.scipy.org/mailman/listinfo/ipython-dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>