This page aims to keep information public about Sage's infrastructure. Question mark means that the information is not confirmed, please edit if you know more.

Please mark which services still need to find a new home, with the system requirements and the deadline.

Current services

DNS

• registrant: was
• admin: was, schilly
• tech contact: was, schilly

ask.sagemath.org

• purpose: webserver wher users can get support
• hosted at: Ohio State University (Niles Johnson's university)
• technology used: ubuntu, nginx, uwsgi, postgesql, askbot
• resources needed: database on a separate VM, 2GB RAM, 10GB disk
• admin: niles, tmonteil, vedlecroix, slelievre, kcrisman, mhansen

• contact: sage-askbot-admin@googlegroups.com

build.sagemath.org

• purpose: distribute and gathers automatic binary building on volunteer's machines
• hosted at: ?UW?

• technology used: ubuntu, nginx: see buildbot for more details

• resources needed: ?CPU ?RAM ?DISK
• admin: ??
• contact: ??

cloud.sagemath.com

• what: a cloud service for computation and collaboration
• operated by: Sagemath, Inc

• url: http://cloud.sagemath.com

doc.sagemath.org, planet.sagemath.org, www.sagemath.org

• purpose: on-line browsable documentation + web homepage
• hosted at: github.io
• technology used: proprietary
• resources needed: 0 CPU, 0 RAM, 0 DISK
• admin: everyone who is on the github group for sagemath
• contact: schilly for the website

dockerhub

• purpose: docker container for SageMath

• url: https://hub.docker.com/u/sagemath/

• admin: vbraun, sebasguts

files.sagemath.org, old.files.sagemath.org

• purpose: main files, spkgs, and backup of "other" files

• what's at files.sagemath.org is exactly rsync.sagemath.org::sage

• old.files.sagemath.org has the old stable releases
• are the old development tarballs are still archived somewhere?
• hosted at: UW. Other places are the mirrors of it.
• contact: schilly, vbraun
• admin: ohanar?

git.sagemath.org, trac.sagemath.org

• purpose: development tools, they share the same host
• hosted at: ?UW?
• technology used: ubuntu, apache, git, trac
• resources needed: ?CPU ?RAM ?DISK
• admin: ?
• contact: ?

GitHub organization for SageMath

• url: http://github.com/sagemath

• admin: ??

patchbot.sagemath.org

• purpose: distribute and gathers automatic ticket testing on volunteer's machines
• hosted at: ?UW?

• technology used: centos, custom flask, mongodb, see buildbot for more details

• resources needed: Minimal CPU, RAM. ~25GB disk.
• admin: robertwb, chapoton
• contact: robertwb, chapoton

Packaging for Linux

arch-linux package

• purpose: easy-to-install arch-linux package
• maintainer: Antonio Rojas

• hosted at: https://www.archlinux.org/packages/community/x86_64/sagemath/

Fedora package

• purpose: easy-to-install Fedora package
• maintainer: Paulo Cesar Pereira de Andrade (pcpa)

• hosted at: https://apps.fedoraproject.org/packages/sagemath

• other link: https://fedoraproject.org/wiki/SIGs/SciTech/SAGE

Gentoo: Sage-on-Gentoo

• repository: https://github.com/cschwan/sage-on-gentoo

• admin: fbissey, cschwan

RPM package

• what: links to sagemath packages for the rpm package manager (Fedora, Mandriva)

• hosted at: http://rpmfind.net/linux/rpm2html/search.php?query=sagemath

Ubuntu PPA

• purpose: easy-to-install Ubuntu .deb packages
• hosted at: launchpad.net
• admin: pipedream

• contact: https://launchpad.net/~aims/+archive/ubuntu/sagemath

rsync.sagemath.org

• purpose: the seed for mirrors, see MirrorNetwork for more details

• hosted at: UW
• technology used: rsync
• resources needed:
  • CPU 1 core
  • RAM 2-3 gb (mostly for caching when calculating hashes)
  • DISK enough for all sage files (50+ GB)
• admin: schilly
• contact: schilly

sagecell.sagemath.org

• purpose: allow embedding sage computations within a webpage
• hosted at:
  • Goethe-Universität (Frankfurt, Germany)
  • Universidad Autónoma de Madrid (Madrid, Spain)
  • Google Compute Engine (Council Bluffs, Iowa, USA)
• technology used: production installation requires a dedicated server (either physical or virtual)
• resources needed:
  • RAM: 32GB recommended for smooth operation, 16GB may become enough in the future
  • CPU: the more the better for handling spikes in load and allowing parallel interacts, but any will do if necessary
  • DISK: must have BTRFS at least for /var/lib/lxc, SSD is preferable, 100GB should be sufficient for the foreseeable future
• admin: novoselt
• contact: novoselt

• available urls: http://aleph.sagemath.org, http://sagecell.sagemath.org

SageDebianLive

• purpose: a live usb stick with Debian, Sage, and more open-source software
• admin: tmonteil

• hosted at: http://sagedebianlive.metelu.net/

• mailing list: https://sagedebianlive.metelu.net/mailman/listinfo/devel

sagenb.org

• purpose: public notebook,

• state: end of life, replaced by http://cloud.sagemath.com

• volunteers: dimpase, tmonteil, vdelecroix

social networks

Facebook

• url: https://www.facebook.com/Sage-Math-26593144945/

• admin: schilly

Google+

• url: https://plus.google.com/+sagemath

• admin: schilly

Twitter

• url: https://twitter.com/sagemath

• admin: schilly

wiki.sagemath.org

• purpose: the wiki you are currently reading!
• hosted at: ?UW?
• technology used: ubuntu, apache, moinmoin
• resources needed: ?CPU ?RAM ?DISK
• admin: ?
• contact: ?
• possible issue in migration: it share the same db of users acounts than trac.

Planned services (wishlist)

schilly: who wishes this and did define those purposes based on what discussion?

backup

• purpose: backup between remote hosts, local backups can be destroyed
  • schilly: backup of what?

stats

• purpose: stop feeding google-analytics database
  • schilly: strong objection, we have a long time history stored there and it's far better than any other tools

• public stats are here http://www.histats.com/viewstats/?SID=1579950&f=2

  • novoselt: horrific page - I thought such blinking adds are a thing of the past, had to close it before finding any data

lists

• purpose: do not depend on googlegroups (see what happened with googleID on ask and sagenb)
  • schilly strong objection: what has this to do with google id?