small preconfigured virtual sage server
Emil Widmann
windows.
I have build a small preconfigured Sage server. some technical data:
+ Format: OVA
+ tested with Virtualbox
+ NO Guest Additions installed (please disable Mouse Pointer
Integration, that's a nuisance)
+ based on the live cd
+ download size 576 MB
+ initial size on Disk (extracted ca 2 GB)
+ maximum Disk size 20 GB
+ Cut down Sage (version 4.6 just application, no developement)
+ initial setting 500 MB virtual RAM, "bridget" Network Adapter
+ boots into gui
+ plotting in R should work
+ ssh client / daemon for remote access
+ scripts (desktop Icons) for starting sage CLI, notebook (single
user, http) or multiuser (https, up to 29 simultanious users)
+ servers run as restricted user "sageadmin"
+ removed some applications from the live CD and cleaned up the menus
+ the system uses uncompressed File system (contrary to Live CD) to
gain some speed
+ I also removed unnecessary drivers and lots off applications (e.g.
abiword).
download link
http://boxen.math.washington.edu/home/emil/VM/slvms-b2.ova
I made also a live CD/USB iso image for this, it is possible to run a
multi user sage server from it, but probably only usable for
restricted demo purposes. For real use you would have to install it
somewhere or at least shift the /home directory with the notebook data
to a physical drive and symlink it.
http://boxen.math.washington.edu/home/emil/sagelive/sage-lite-serverb1.iso
(392 MB)
Why?
Virtual images are the most popular sage distribution. I don't want'
to rival the offical Fedora build. But I have the feeling that some
people for their first contact with sage might feel more comfortable
when they have a gui user interface.
I would like to develop this a bit more, maybe even start the server
in terminal and have only optional gui. So any feedback is very
welcome.
Some issues:
- I have an expired certificate, so if I connect via https to the
server I get a security warning - I don't know how this could be
fixed.
- I also have no experience with memory and disk storage capacity. I
guess 29 users it to much, but what can be handled
- And I also would have a good documentation how to use it, so if
there are open questions, thats a good starting point to improve the
docs.
- The live CD distro is not really built as multiuser systems, so I
had real work to make the necessary tweaks. But I am not really a
Linux specialist, nor good with networks, security etc, so I would
help if somebody with clue could have a look on those parts.
thanks in advance
emil
NOTE: This is not the official sage vm image
official image (MIRRORS): http://www.sagemath.org/download-windows.html
Recently published: GENTO VM Image:
http://www.google.com/url?sa=D&q=http://riemann.unizar.es/sagevm/Sage.ova
whats the difference? Those images are bigger, no gui, but full
fledged, so you can start to develop sage right away. Maybe they are
also a bit faster (no graphic running).
William Stein
> It's no secret I consider virtualisation the way to go with sage on
> windows.
> I have build a small preconfigured Sage server. some technical data:
>
> + Format: OVA
> + tested with Virtualbox
> + NO Guest Additions installed (please disable Mouse Pointer
> Integration, that's a nuisance)
> + based on the live cd
> + download size 576 MB
> + initial size on Disk (extracted ca 2 GB)
> + maximum Disk size 20 GB
> + Cut down Sage (version 4.6 just application, no developement)
Why 4.6 rather than 4.7.x? Sage-4.6 is over a year old and a huge
amount has been fixed since then. It can be really hard dealing with
user bug reports when their version of Sage is so old.
Other than that, very cool that you got this to fit into 576MB!!
Just out of curiosity, does using a non-compressed file system really
measurably help with speed? When I used to make a compressed
puppy-linux based live VM, it was pretty cool to be able to have the
extracted version also be small (I think it was << 1GB *extracted*).
William
Emil Widmann
On Nov 15, 7:23 pm, William Stein <wst...@gmail.com> wrote:
about version:
I tried to make a new version with the new micro release build option.
But I had some doctest errors and then I decided to take my old
slimmed down version because I expect it is still several 100 MB
smaller than the new one. I am no size fanatic, but I work on a normal
PC 1 GB RAM, and for my work with this stuff it is easier to have
smaller filesizes etc. If I have some sage builds and some Virtual
disks around I am constantly at my disk size limit. I want to
concentrate on the UI, the docs, the server setup etc. Replacing the
sage version is easy. If I had more time I would do both in parallel.
about file systems:
With the live CD I have no noticable performance loss with the
squashed filesystem (I have no real benchmark though) I think this is
related to the ratio of RAM to your programs. If the compressed parts
can be held in memory than it is almost the same speed to uncompress
it insitu than to fetch uncompressed data from hd. But in the virtual
machine I have only 500 MB Ram so Virtualisation + squashed filesystem
feels definitly slower than a normal install - maybe if you could run
the virtual machine with 1 GB+ it would again be the same.
In every case uncompressed filesystem allows lower minimal ram, I have
not tested but I should run in 256 MB. And boot up time is only 50 %.
I am not sure but I do suspect some remaining bit trash in the 576 MB
virtual disk, but the size of ova from this version built with
compressed filesystems should be around 400 MB.
<< 1 GB extracted :-) ? must have been at least 2 years ago ...
emil
William Stein
It was two years ago. It was that small because I used a compressed
read only file system with a read-write layer on top of it. Here's
the discussion:
http://groups.google.com/group/sage-windows/browse_thread/thread/810263b3cf8f48b7
It was 700MB after install.
I made it by taking a stock Puppy Linux Virtual machine, then
extracting a sage binary into it, then putting that in a compressed
file system, then layering a non-compressed filesystem on top, so
users could still edit the sage install.
-- William
> emil
>
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "sage-windows" group.
> To post to this group, send email to sage-w...@googlegroups.com.
> To unsubscribe from this group, send email to sage-windows...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sage-windows?hl=en.
>
>
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
Emil Widmann
> > << 1 GB extracted :-) ? must have been at least 2 years ago ...
>
> It was two years ago. It was that small because I used a compressed
> read only file system with a read-write layer on top of it. Here's
> the discussion:
> http://groups.google.com/group/sage-windows/browse_thread/thread/810263b3cf8f48b7
stopped.
> It was 700MB after install.
699 MB, but it had Latex, Lyx, Texmacs, octave and other utilities
included. Thats impossible now.
> I made it by taking a stock Puppy Linux Virtual machine, then
> extracting a sage binary into it, then putting that in a compressed
> file system, then layering a non-compressed filesystem on top, so
> users could still edit the sage install.
I don't know if Barry Kauler invented it himself, but it works quite
reliably and fast.
I also announced this here (with screenshot), maybe I get some
testers :-)
http://murga-linux.com/puppy/viewtopic.php?t=62231&start=58
Emil Widmann
Sage Lite Server2 (iso file)
http://boxen.math.washington.edu/home/emil/sagelive/sage-lite2.iso
Small virtual machine + server (398 MB, ova format - Virtual Box)
http://boxen.math.washington.edu/home/emil/VM/sage-lite2.ova
The ssh keys for the server were broken, so I made it that they are
generated at first boot (you can refresh them with calling
fix-ssh-keys.sh from command line).
cheers
emil