Well, everything you said is true. But I need to recommend Sage for installation to other people.
I guess this is not very important at the first stage. So I'll proceed with Ganga and DIANE. Several admins from BalticGrid didn't object compiling Sage for installations, so an rpm package may not be needed too. Thank you for comments. It may have been a bad idea to cut Sage into pieces. I found SPD. A great thing that could be worked on. So for now there is nothing to say more in this topic. #Serge Jason Grout пишет: > Disclaimer: I may not know what I'm talking about here :). > > Serge A. Salamanka wrote: >> >> William Stein пишет: >>> On Tue, May 19, 2009 at 3:47 AM, Serge A. Salamanka <salsa-...@tut.by> >>> wrote: >>>> If no objection I'll post here for possible comments and guidelines. >>>> >>>> First thing that I'm trying to do is to make a distribution of SAGE that >>>> could be recommended for installation on worker nodes of large clusters >>>> in supercomputing centers. >>>> After BG-II project meeting it was decided to recommend Sage as a >>>> service for gLite-sites. >>>> So the need is to produce a safe package for WNs. >>>> Safe means secure and safe to install in the cluster infrastructure. >>> I think it is completely impossible to make Sage "secure and safe to >>> install". What >>> do you even mean by "secure and safe"? >>> >>> William >>> >> I mean that there should be no possibility to access the WN from outside >> using some unknown to me features of twisted. > > Wouldn't it be better to do a firewall and network filtering? Then you > aren't depending on a program playing nice. > > > >> It is better to strip off the software from unnecessary functionality. >> The worker node should (in my view) be able to execute sage and python >> scripts. Everything else is not needed. >> >> In the term of "safe" I put stability of use by many users in the system >> which is not going to stall the machine. > > > Well, again, you can do a fork bomb in most languages and stall a > machine. Seems like it'd be better to handle that problem via resource > limits. > > >> So, as it comes out of your question there is no point to do anything >> with Sage to install it on worker nodes. Might be the only thing is to >> pack it into rpm for Scientific Linux. > > Good point. > > Jason > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
