Differences between revisions 67 and 69 (spanning 2 versions)
Revision 67 as of 2019-04-01 18:51:15
Size: 8376
Editor: chapoton
Revision 69 as of 2019-08-22 18:35:10
Size: 8609
Editor: chapoton
Deletions are marked like this. Additions are marked like this.
Line 65: Line 65:
  * admin: embray ?   * admin: embray, jrueth
Line 77: Line 77:
  * hosted at: [[https://irma.math.unistra.fr/|IRMA]], Université de Strasbourg   * hosted at: [[https://irma.math.unistra.fr/|IRMA]], [[http://www.unistra.fr|Université de Strasbourg]]
Line 145: Line 145:
== DockerHub organization ==
  * purpose: distribute SageMath Docker images
  * hosted at: https://hub.docker.com/u/sagemath/
  * admin: embray, jrueth
  * other: slelievre also has push access

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


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


  • purpose: webserver where users can get support
  • hosted at: Ohio State University

  • technology used: ubuntu, nginx, uwsgi, postgesql, askbot
  • resources needed: database on a separate VM, 2GB RAM, 10GB disk
  • admin: niles, tmonteil, vdelecroix, slelievre, kcrisman, mhansen
  • contact: [email protected]

  • local tech contact: David Alden


  • purpose: keep the data of various services in a separate place
  • hosted at: Mathematics lab, University Paris South (Orsay)

  • technology used: debian, rsync, rssh, rsnapshot
  • resources needed: 1TB disk
  • admin: tmonteil, slelievre
  • local sage dev: slelievre
  • local tech contact: Mathilde Rousseau

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

files.sagemath.org, fileserver.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, going to move soon
  • technology used: ubuntu, apache, git, trac
  • resources needed: ?CPU ?RAM ?DISK
  • admin: people with root access: kclawson, ohanar, vbraun, mderickx, robertwb, wstein, tmonteil, dimpase
  • contact: no real organisation yet, go to sage-devel

GitHub organization for SageMath

GitLab organization for SageMath


  • 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: ??


  • purpose: distribute and gathers automatic ticket testing on volunteer's machines
  • hosted at: IRMA, Université de Strasbourg

  • technology used: ubuntu, nginx, uwsgi, flask, mongodb, see patchbot for more details

  • application source code: https://github.com/sagemath/sage-patchbot

  • resources needed: Minimal CPU, RAM. ~50GB disk.
  • admin: chapoton, tmonteil
  • root access: chapoton, tmonteil
  • contact: chapoton, tmonteil
  • local sage dev: chapoton
  • local tech contact: Alain Sartout


  • 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


  • purpose: turn pull requests on GitHub into trac tickets

  • contact: robertwb


  • purpose: allow embedding sage computations within a webpage
  • hosted at:
  • 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, https://sagecell.sagemath.org


  • purpose: public notebook,
  • state: end of life, replaced by CoCalc

  • volunteers to provide worksheets back to the users: dimpase, tmonteil, vdelecroix


  • purpose: the wiki you are reading!
  • hosted at: UW, going to move soon (moved to cloud.google.com ?)
  • technology used: ubuntu, apache, moinmoin
  • resources needed: ?CPU ?RAM ?DISK
  • admin: people with root access: kclawson, wstein, ohanar, mmarco, tmonteil, dimpase
  • contact: no real organisation yet, go to sage-devel
  • possible issue in migration: the database of user accounts is synced from trac when this latter is modified (incron)


  • purpose: chat system
  • hosted at: cloud.google.com
  • resources needed: a dedicated VM with 2-4GB of RAM
  • admin: roed


  • purpose: ? (holds a copy of the mercurial patches of sage-combinat)
  • hosted at: UW ?
  • technology used: ?
  • resources needed: ?CPU ?RAM ?DISK
  • admin: people with root access: schilly?
  • contact: ?

DockerHub organization

Planned services (wishlist)

  • schilly: who wishes this and did define those purposes based on what discussion?
  • tmonteil: this is a wishlist, not something collectively decided. Note however that almost nothing in the current framework was collectively discussed either.



  • 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
    • tmonteil: i hope this long time history could be easily fetched in some open format, or does this mean that we locked ourselves there? (being locked would imply that this tool is among the worst)
    • tmonteil: better for who? for google and the NSA to which we currently provide all our visitors IPs? There is a serious privacy issue with such analytics saas 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
    • tmonteil: note that free software alternative do exist


  • 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?
    • tmonteil: googleID is an example of a service that was stopped by google, with strong consequences on our side (some people not able to connect anymore (e.g. on ask.sagemath.org), or not able to retrieve their work (e.g. on sagenb.org)). What will happen when google will decide that googlegroups will be shut down? Would we be able to discuss with them about this issue?

Infrastructure (last edited 2019-12-04 08:37:43 by chapoton)