Differences between revisions 23 and 89 (spanning 66 versions)
Revision 23 as of 2015-05-21 10:37:48
Size: 3474
Editor: tmonteil
Comment:
Revision 89 as of 2022-04-23 00:18:54
Size: 7072
Editor: mkoeppe
Comment:
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:

[[PageOutline]]
Line 9: Line 12:
  * admin: was
  * tech contact: was
  * admin: was, schilly
  * tech contact: was, schilly
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:
== 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


== 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
  * url: https://doc.sagemath.org https://planet.sagemath.org https://www.sagemath.org

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

== 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 ==
  * url: https://github.com/sagemath
  * admin: schilly, vbraun

== GitLab organization for SageMath ==

  * url: https://gitlab.com/sagemath
  * admin: embray, jrueth
Line 24: Line 84:
  * hosted at: ?UW?
  * technology used: ubuntu, nginx: see [[buildbot]] for more details
  * hosted at: University of Washington
  * technology used: ubuntu, nginx; using using the continuous integration framework of http://buildbot.net/
Line 27: Line 87:
  * admins: ?robertwb?
  * contact: ?robertwb?


== doc.sagemath.org and www.sagemath.org ==
  * purpose: on-line browsable documentation + web homepage
  * hosted at: github.io via fastly.net ?
  * technology used: proprietary?
  * resources needed: ?CPU ?RAM ?DISK
  * admins: ?schilly?
  * contact: ?schilly?


== git.sagemath.org and 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
  * admins: ?schilly?
  * contact: ?schilly?
  * admin: ??
  * contact: ??
  * url: http://build.sagemath.org
Line 51: Line 93:
  * hosted at: ?UW?
  * technology used: ubuntu, custom flask code?, see [[buildbot]] for more details
  * resources needed: ?CPU ?RAM ?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: ?GCE?
  * technology used: ?
  * resources needed: ?CPU ?RAM ?DISK
  * admins: ?schilly?
  * contact: ?schilly?
  * 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
Line 75: Line 118:
  * hosted at: University of Frankfurt
  * technology used: ?
  * resources needed: ?CPU ?RAM ?DISK
  * admins: ?novoselt? ?Sven Koeppel? ?pokal-taskforce?
  * contact: sage-notebook@googlegroups.com
  * hosted at:
    * [[Goethe-Universität|www.uni-frankfurt.de]] (Frankfurt, Germany)
    * [[https://www.uam.es|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, https://sagecell.sagemath.org
Line 81: Line 131:
== wiki.sagemath.org ==
  * purpose: the wiki you are reading!
  * #33725: Migrate wiki.sagemath.org to trac.sagemath.org/wiki
  * hosted at: [[https://lipn.univ-paris13.fr/|LIPN (CS lab)]], University Paris North (Villetaneuse)
  * contact: sagemath-admins@googlegroups.com
  * 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)

== DockerHub organization ==
  * purpose: distribute SageMath Docker images
  * hosted at: https://hub.docker.com/u/sagemath/
  * admin: embray, jrueth
  * other: slelievre also has push access

= Defunct services =
Line 84: Line 153:
  * 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; redirects to [[https://cocalc.com/|CoCalc]]
 * volunteers to provide worksheets back to the users: dimpase, tmonteil, vdelecroix
Line 87: Line 156:
== sageb0t ==
  * purpose: turn pull requests on !GitHub into trac tickets
  * contact: robertwb
Line 88: Line 160:
== wiki.sagemath.org ==
  * purpose: the wiki you are currently reading!
  * hosted at: ?UW?
  * technology used: ubuntu, apache, moinmoin
  * resources needed: ?CPU ?RAM ?DISK
  * admins: ?schilly?
  * contact: ?schilly?
  * possible issue in migration: it share the same db of users acounts than trac.


= Planned services (wishlist) =

== backup ==
  * purpose: backup between remote hosts, local backups can be destroyed

== stats ==
  * purpose: stop feeding google-analytics database

== lists ==
  * purpose: do not depend on googlegroups (see what happened with googleID on ask and sagenb)
== zulip.sagemath.org ==
  * purpose: chat system
  * state: has been replaced by https://sagemath.zulipchat.com/

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.

PageOutline

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: sage-askbot-admin@googlegroups.com

  • 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

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

wiki.sagemath.org

  • purpose: the wiki you are reading!
  • #33725: Migrate wiki.sagemath.org to trac.sagemath.org/wiki
  • hosted at: LIPN (CS lab), University Paris North (Villetaneuse)

  • contact: sagemath-admins@googlegroups.com

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

DockerHub organization

Defunct services

sagenb.org

  • purpose: public notebook,
  • state: end of life; redirects to CoCalc

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

sageb0t

  • purpose: turn pull requests on GitHub into trac tickets

  • contact: robertwb

zulip.sagemath.org