Differences between revisions 27 and 84 (spanning 57 versions)
Revision 27 as of 2015-06-08 06:05:59
Size: 4810
Editor: robertwb
Comment:
Revision 84 as of 2022-04-18 03:30:53
Size: 7065
Editor: mkoeppe
Comment: replace link to almost empty "buildbot" page by link to buildbot.net
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page aims to keep information public about Sage's infrastructure. Question mark means that the information is not confirmed, please do not hesitate to edit if you know more. 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... and '''note the date of your update''' so that current and stale information can be distinguished.
Line 4: Line 5:

<<TableOfContents()>>
Line 13: Line 16:
  * 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
  * admins: niles, tmonteil, vedlecroix, slelievre, kcrisman, mhansen
  * purpose: webserver where users can get support
  * hosted at: [[https://lipn.univ-paris13.fr/|LIPN (CS lab)]], University Paris North (Villetaneuse)
Line 19: Line 19:
  * url: https://ask.sagemath.org
  * admin: tmonteil
  * local sage dev: tmonteil
  * technology used: unprivileged LXC, debian, nginx, uwsgi, postgesql, askbot
  * issues : upgrade askbot to further versions is pretty painful (broken database migration scripts)
  * formerly hosted at: [[https://www.osu.edu/|Ohio State University]] (thanks !)
    * resources needed: database on a separate VM, 2GB RAM, 10GB disk
    * admin: niles, tmonteil
    * local tech contact: David Alden, Josh Carroll
    * technology used: ubuntu, nginx, uwsgi, postgesql, askbot
    * there are two machines : ask-sagemath and ask-sagemath-db
Line 21: Line 32:

== 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
  * admins: ??
  * contact: ??
== backup ==
  * purpose: keep the data of various services in a separate place
  * hosted at: [[https://www.math.u-psud.fr/?lang=fr|Mathematics lab]], Université Paris Sud (Orsay)
  * technology used: debian, rsync, cron
  * resources needed: 1TB disk
  * admin: tmonteil, slelievre
  * local sage dev: slelievre
  * local tech contact: Mathilde Rousseau
  * currently keeping a daily backup of :
    * https://ask.sagemath.org
    * https://wiki.sagemath.org
Line 31: Line 45:
== doc.sagemath.org planet.sagemath.org www.sagemath.org == == doc.sagemath.org, planet.sagemath.org, www.sagemath.org ==
Line 36: Line 50:
  * admins: everyone who is on the github group for sagemath   * admin: everyone who is on the github group for sagemath
Line 38: Line 52:
  * url: https://doc.sagemath.org https://planet.sagemath.org https://www.sagemath.org
Line 39: Line 54:
== 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?
  * url: http://files.sagemath.org http://fileserver.sagemath.org http://old.files.sagemath.org
Line 40: Line 64:
== git.sagemath.org and trac.sagemath.org == == git.sagemath.org, trac.sagemath.org ==
Line 42: Line 66:
  * hosted at: ?UW?   * hosted at: google ?
Line 45: Line 69:
  * admins: ?
  * contact: ?
  * admin: people with root access: kclawson, ohanar, vbraun, mderickx, robertwb, wstein, dimpase
  * contact: no real organisation yet, go to sage-devel
  * url: https://git.sagemath.org https://trac.sagemath.org
Line 48: Line 73:
== GitHub organization for SageMath ==
  * url: https://github.com/sagemath
  * admin: schilly, vbraun

== GitLab organization for SageMath ==

  * url: https://gitlab.com/sagemath
  * admin: embray, jrueth

== build.sagemath.org ==
  * purpose: distribute and gathers automatic binary building on volunteer's machines
  * hosted at: University of Washington
  * technology used: ubuntu, nginx; using using the continuous integration framework of http://buildbot.net/
  * resources needed: ?CPU ?RAM ?DISK
  * admin: ??
  * contact: ??
  * url: http://build.sagemath.org
Line 51: Line 93:
  * hosted at: ?UW?
  * technology used: ubuntu, custom flask, mongodb, see [[buildbot]] for more details
  * resources needed: Minimal CPU, RAM. ~25GB disk.
  * admins: robertwb
  * contact: robertwb

== PPA ==
  * purpose: easy-to-install Ubuntu .deb packages
  * hosted at: launchpad.net
  * admins: pipedream
  * contact: https://launchpad.net/~aims/+archive/ubuntu/sagemath
  * hosted at: [[https://irma.math.unistra.fr/|IRMA]], [[http://www.unistra.fr|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
  * url: https://patchbot.sagemath.org
Line 66: Line 106:
  * hosted at: UW   * hosted at: University of Washington
Line 70: Line 110:
     * RAM 2-3 gb (mostly for caching when calculating hashes)      * RAM 2-3 GB (mostly for caching when calculating hashes)
Line 72: Line 112:
  * admins: schilly   * admin: schilly
Line 74: Line 114:
  * url: http://rsync.sagemath.org
Line 75: Line 116:
== sageb0t ==
  * purpose: turn pull requests on !GitHub into trac tickets
  * contact: robertwb
Line 79: Line 123:
    * Goethe-Universität (Frankfurt, Germany)
    * Universidad Autónoma de Madrid (Madrid, Spain)
    * [[Goethe-Universität|www.uni-frankfurt.de]] (Frankfurt, Germany)
    * [[https://www.uam.es|Universidad Autónoma de Madrid]] (Madrid, Spain)
Line 87: Line 131:
  * admins: novoselt   * admin: novoselt
Line 89: Line 133:
  * available urls: http://aleph.sagemath.org, https://sagecell.sagemath.org
Line 93: Line 137:
  * state: end of life, still needs some support to provide backup of their worksheets to former users
  * volunte
ers: dimpase, tmonteil, vdelecroix
  * state: end of life, replaced by [[https://cocalc.com/|CoCalc]]
  * volun
teers to provide worksheets back to the users: dimpase, tmonteil, vdelecroix
Line 98: Line 141:
  * purpose: the wiki you are currently reading!
  * hosted at: ?UW?
  * technology used: ubuntu, apache, moinmoin
  * resources needed: ?CPU ?RAM ?DISK
  * admins: ?
  * contact: ?
  * possible issue in migration: it share the same db of users acounts than trac.
  * purpose: the wiki you are reading!
  * hosted at: [[https://lipn.univ-paris13.fr/|LIPN (CS lab)]], University Paris North (Villetaneuse)
  * contact: [email protected]
  * url: https://wiki.sagemath.org
  * admin: tmonteil
  * local sage dev: tmonteil
  * technology used: unprivileged LXC, debian, nginx, certbot, uwsgi, moinmoin, jsmath, docutils
  * formerly hosted at: cloud.google.com
  * possible issue in migration: the database of user accounts is synced from trac when this latter is modified (incron)
Line 106: Line 151:
== sagemath files ==
  * purpose: main files for rsync and backup of "other" files
  * hosted at: UW and other places ?
  * schilly: this should get its own subdomain files.sagemath.org
== zulip.sagemath.org ==
  * purpose: chat system
  * hosted at: cloud.google.com
  * resources needed: a dedicated VM with 2-4GB of RAM
  * admin: roed, jrueth (saraedum) - as of 2020-05.
Line 111: Line 157:

= 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?
== 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... and note the date of your update so that current and stale information can be distinguished.

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: LIPN (CS lab), University Paris North (Villetaneuse)

  • contact: [email protected]

  • url: https://ask.sagemath.org

  • admin: tmonteil
  • local sage dev: tmonteil
  • technology used: unprivileged LXC, debian, nginx, uwsgi, postgesql, askbot
  • issues : upgrade askbot to further versions is pretty painful (broken database migration scripts)
  • formerly hosted at: Ohio State University (thanks !)

    • resources needed: database on a separate VM, 2GB RAM, 10GB disk
    • admin: niles, tmonteil
    • local tech contact: David Alden, Josh Carroll
    • technology used: ubuntu, nginx, uwsgi, postgesql, askbot
    • there are two machines : ask-sagemath and ask-sagemath-db

backup

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

  • technology used: debian, rsync, cron
  • resources needed: 1TB disk
  • admin: tmonteil, slelievre
  • local sage dev: slelievre
  • local tech contact: Mathilde Rousseau
  • currently keeping a daily backup of :

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, 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; using using the continuous integration framework of http://buildbot.net/

  • 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: LIPN (CS lab), University Paris North (Villetaneuse)

  • contact: [email protected]

  • url: https://wiki.sagemath.org

  • admin: tmonteil
  • local sage dev: tmonteil
  • technology used: unprivileged LXC, debian, nginx, certbot, uwsgi, moinmoin, jsmath, docutils
  • formerly hosted at: cloud.google.com
  • 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, jrueth (saraedum) - as of 2020-05.

DockerHub organization