Differences between revisions 67 and 76 (spanning 9 versions)
Revision 67 as of 2019-04-01 18:51:15
Size: 8376
Editor: chapoton
Comment:
Revision 76 as of 2019-12-04 08:37:43
Size: 9029
Editor: chapoton
Comment:
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
  * url: https://ask.sagemath.org
Line 26: Line 27:
  * hosted at: [[http://www.math.u-psud.fr/?lang=fr|Mathematics lab]], University Paris South (Orsay)   * hosted at: [[https://www.math.u-psud.fr/?lang=fr|Mathematics lab]], Université Paris Sud (Orsay)
Line 40: Line 41:
  * url: https://doc.sagemath.org https://planet.sagemath.org https://www.sagemath.org
Line 49: Line 51:
  * url: http://files.sagemath.org http://fileserver.sagemath.org http://old.files.sagemath.org
Line 52: Line 55:
  * hosted at: UW, going to move soon   * hosted at: google ?
Line 57: Line 60:
  * url: https://git.sagemath.org https://trac.sagemath.org
Line 59: Line 63:
  * https://github.com/sagemath   * url: https://github.com/sagemath
Line 64: Line 68:
  * https://gitlab.com/sagemath
  * admin: embray ?
  * url: https://gitlab.com/sagemath
  * admin: embray, jrueth
Line 69: Line 73:
  * hosted at: ?UW?   * hosted at: University of Washington
Line 74: Line 78:
  * url: http://build.sagemath.org
Line 77: Line 82:
  * 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 86: Line 91:
  * url: https://patchbot.sagemath.org
Line 89: Line 95:
  * hosted at: UW   * hosted at: University of Washington
Line 97: Line 103:
  * url: http://rsync.sagemath.org
Line 124: Line 131:
  * hosted at: UW, going to move soon (moved to cloud.google.com ?)   * hosted at: moved to cloud.google.com ?
Line 139: Line 146:
  * hosted at: UW ?   * hosted at: cloud.google.com ?
Line 144: Line 151:

== 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

DNS

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

ask.sagemath.org

  • 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
  • url: https://ask.sagemath.org

backup

  • purpose: keep the data of various services in a separate place
  • hosted at: Mathematics lab, Université Paris Sud (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

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

git.sagemath.org, trac.sagemath.org

  • purpose: development tools, they share the same host
  • hosted at: google ?
  • 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
  • url: https://git.sagemath.org https://trac.sagemath.org

GitHub organization for SageMath

GitLab organization for SageMath

build.sagemath.org

  • purpose: distribute and gathers automatic binary building on volunteer's machines
  • hosted at: University of Washington
  • technology used: ubuntu, nginx: see buildbot for more details

  • resources needed: ?CPU ?RAM ?DISK
  • admin: ??
  • contact: ??
  • url: http://build.sagemath.org

patchbot.sagemath.org

rsync.sagemath.org

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

  • hosted at: University of Washington
  • 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
  • url: http://rsync.sagemath.org

sageb0t

  • purpose: turn pull requests on GitHub into trac tickets

  • contact: robertwb

sagecell.sagemath.org

  • 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

sagenb.org

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

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

wiki.sagemath.org

  • purpose: the wiki you are reading!
  • hosted at: 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)

zulip.sagemath.org

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

combinat.sagemath.org

  • purpose: ? (holds a copy of the mercurial patches of sage-combinat)
  • hosted at: cloud.google.com ?
  • 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.

backup

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

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?
    • 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 2023-02-23 20:12:25 by mkoeppe)