-
-
Notifications
You must be signed in to change notification settings - Fork 529
Infrastructure
Kwankyu Lee edited this page Feb 14, 2025
·
105 revisions
This page keeps public information about the infrastructure of the SageMath organization. Question mark means that the information is not confirmed, please edit if you know more.
- main service: maintenance of github.com/sagemath
- managers (as of 2025-02): @roed314, @saraedum, @fchapoton, @haraldschilly, @jhpalmieri, @jplab, @nthiery, @vbraun, @williamstein
- main service: maintenance of github.com/sponsors/sagemath
- managers (as of 2024-06): @dimpase, @haraldschilly
- main service: maintenance of gitlab.com/sagemath
- managers (as of 2024-06): @roed.math, @dimpase, @embray, @fchapoton2, @harald.schilly, @saraedum, @defeo, @master.sage, @nthiery, @slel, @videlec
- main service: maintenance of opencollective.com/sage_math
- managers (as of 2024-06): @dimpase, @haraldschilly
- main service: maintenance of projects deployed to the Python Package Index (PyPI)
- main service: maintenance of hub.docker.com/u/sagemath
- managers (as of 2024-06): @saraedum, @mkoeppe, @soehms, [email protected]
- main service: maintenance of docs deployed to sagemath.netlify.app
- managers (as of 2025-01): @kwankyu
- main service: maintenance of mailing groups in https://groups.google.com
- main service: maintenance of sagemath.zulipchat.com
- managers (as of 2024-06): @roed
- test only, created in 2024-06
- main service: maintenance of sagemath-test.discourse.group
- managers: @mkoeppe, @dimpase
- application created in April 2024
- contacts: @mkoeppe, @kwankyu
- manager (as of 2024-06): @tobiasdiez (see https://gitpod.io/members)
- registrant: @was
- admin: @was, @schilly
- tech contact: @was, @schilly
- as of 2024-06, hosted at sagemath.openbsd.amsterdam; [email protected] forwarding
- admin: @dimpase
- tech contact: @dimpase
- in operation since 2022
- admin: @wstein
- purpose: webserver where users can get support
- hosted at: LIPN (CS lab), University Paris North (Villetaneuse)
- contact:
[email protected](rejects mail as of 2024-06) - 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
- Migration discussion (2024-06): https://groups.google.com/g/sage-devel/c/9uX5j4x1Nsg, https://ask.sagemath.org/question/78069/migrating-asksagemathorg-to-discourse/
- 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 :
- purpose: on-line browsable documentation + web homepage
- hosted at: github.io (sagemath/documentation, sagemath/planet, sagemath/sagemath.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
- 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: vbraun
- provides buildbot workers: Jan Groenewald (as of 2024-06)
- 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
- purpose: allow embedding sage computations within a webpage
- hosted at:
- 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
- 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, 150GB or more
- admin: novoselt
- contact: novoselt
- #33725: Migrate wiki.sagemath.org to more suitable places
- hosted at: LIPN (CS lab), University Paris North (Villetaneuse)
- contact: [email protected]
- admin: tmonteil
- local sage dev: tmonteil
- technology used: unprivileged LXC, debian, nginx, certbot, uwsgi, moinmoin, jsmath, docutils
- formerly hosted at: cloud.google.com
- database of user accounts used to be synced from trac (incron); as of 2024-06, managed manually, see https://wiki.sagemath.org/#About_this_wiki
- static site serving redirects to GitHub, https://github.com/sagemath/trac.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?
- https://groups.google.com/g/sage-devel/c/GYKHtknK-CA
Mark which services still need to find a new home, with the system requirements and the deadline.
- purpose: public notebook,
- state: end of life; redirects to CoCalc
- volunteers to provide worksheets back to the users: dimpase, tmonteil, vdelecroix
- purpose: turn pull requests on GitHub into trac tickets
- contact: robertwb
- purpose: chat system
- state: has been replaced by and redirects to https://sagemath.zulipchat.com/
- purpose: development tools
- state: has been replaced by using GitHub for development
- purpose: main files, spkgs, and backup of "other" files
- what's at files.sagemath.org is exactly rsync.sagemath.org::sage
- hosted at: UW. Other places are the mirrors of it.
- contact: schilly, vbraun
- admin: ohanar?