On Wed, Apr 1, 2015 at 9:54 PM, William Stein <wst...@gmail.com> wrote:
> If somebody from JH decides to explain how every point above is > slightly wrong, that would be nice, since I can't imagine that they > aren't wrong! > Actually, I don't see any major errors in there :) Just to add some detail, the basic design of JH is: out of the box, assume: 1. local Unix auth (PAM) 2. for each authenticated user, you start their notebook as a local subprocess. That makes it very easy to run it in your typical 'university research group' environment, where there's some NFS server under a desk a beefy shared unix box where the group members all SSH in. But both #1 and #2 above are separately customizable. What Jess did was to replace #1 with Github auth, and #2 with a fairly sophisticated Docker setup (she ended up contributing fixes to Docker Swarm just as it was released). With said customizations, the same basic architecture should be usable in some other scenarios, just as Jess has demonstrated. JH doesn't have out of the box any of the many sophisticated features that SMC has, nor is most of that stuff on our roadmap. Lots of what William has done there is needed to provide a robust, 24/7 service with (hopefully :) paying customers, and we're not doing any of that. I do hope that SMC will be very successful, and we do talk to William every time we have a chance to share ideas, brainstorm, etc. Cheers f -- Fernando Perez (@fperez_org; http://fperez.org) fperez.net-at-gmail: mailing lists only (I ignore this when swamped!) fernando.perez-at-berkeley: contact me here for any direct mail -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
