|
Size: 7272
Comment:
|
Size: 9107
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| Question mark means that the information is not confirmed, please edit if you know more. | 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 6: | Line 6: |
| Line 8: | Line 7: |
| Line 19: | Line 17: |
| * hosted at: Ohio State University (Niles Johnson's university) | * hosted at: [[https://www.osu.edu/|Ohio State University]] |
| Line 22: | Line 20: |
| * admin: niles, tmonteil, vedlecroix, slelievre, kcrisman, mhansen | * admin: niles, tmonteil |
| Line 24: | Line 22: |
| * local tech contact: David Alden, Josh Carroll * url: https://ask.sagemath.org |
|
| Line 25: | Line 25: |
| == cloud.sagemath.com == * what: a cloud service for computation and collaboration * operated by: Sagemath, Inc * url: http://cloud.sagemath.com * note: despite its name, this service is not operated by the SageMath community, but by a private company |
== 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 |
| Line 38: | Line 41: |
| * url: https://doc.sagemath.org https://planet.sagemath.org https://www.sagemath.org | |
| Line 39: | Line 43: |
| == files.sagemath.org, old.files.sagemath.org == | == files.sagemath.org, fileserver.sagemath.org, old.files.sagemath.org == |
| Line 47: | Line 51: |
| * url: http://files.sagemath.org http://fileserver.sagemath.org http://old.files.sagemath.org | |
| Line 50: | Line 55: |
| * hosted at: UW, going to move soon | * hosted at: google ? |
| Line 53: | Line 58: |
| * admin: currently, the people with root access are : kclawson,ohanar,vbraun,mderickx,robertwb,wstein,tmonteil,dimpase | * admin: people with root access: kclawson, ohanar, vbraun, mderickx, robertwb, wstein, dimpase |
| Line 55: | Line 60: |
| * url: https://git.sagemath.org https://trac.sagemath.org | |
| Line 57: | Line 63: |
| * url: http://github.com/sagemath | * url: https://github.com/sagemath |
| Line 59: | Line 65: |
== GitLab organization for SageMath == * url: https://gitlab.com/sagemath * admin: embray, jrueth |
|
| Line 62: | Line 73: |
| * hosted at: ?UW? | * hosted at: University of Washington |
| Line 67: | Line 78: |
| * url: http://build.sagemath.org | |
| Line 70: | Line 82: |
| * hosted at: ?UW? * technology used: centos, custom flask, mongodb, see [[buildbot]] for more details * resources needed: Minimal CPU, RAM. ~25GB disk. * admin: robertwb, chapoton * contact: robertwb, chapoton |
* 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 78: | Line 95: |
| * hosted at: UW | * hosted at: University of Washington |
| Line 82: | Line 99: |
| * RAM 2-3 gb (mostly for caching when calculating hashes) | * RAM 2-3 GB (mostly for caching when calculating hashes) |
| Line 86: | Line 103: |
| * url: http://rsync.sagemath.org == sageb0t == * purpose: turn pull requests on !GitHub into trac tickets * contact: robertwb |
|
| Line 90: | Line 112: |
| * 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 100: | Line 122: |
| * available urls: http://aleph.sagemath.org, http://sagecell.sagemath.org | * available urls: http://aleph.sagemath.org, https://sagecell.sagemath.org |
| Line 104: | Line 126: |
| * state: end of life, replaced by [[http://cloud.sagemath.com]] * volunteers to provide worksheets back to the users : dimpase, tmonteil, vdelecroix |
* state: end of life, replaced by [[https://cocalc.com/|CoCalc]] * volunteers to provide worksheets back to the users: dimpase, tmonteil, vdelecroix |
| Line 108: | Line 130: |
| * purpose: the wiki you are currently reading! * hosted at: UW, going to move soon |
* purpose: the wiki you are reading! * hosted at: moved to cloud.google.com ? |
| Line 112: | Line 134: |
| * admin: currently, the people with root access are : kclawson,wstein,ohanar,mmarco,tmonteil,dimpase | * admin: people with root access: kclawson, wstein, ohanar, mmarco, dimpase |
| Line 114: | Line 136: |
| * possible issue in migration: the db of user acounts is synced from trac when this latter is modified (incron) | * possible issue in migration: the database of user accounts is synced from trac when this latter is modified (incron) |
| Line 116: | Line 138: |
| == 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. == 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 == * purpose: distribute SageMath Docker images * hosted at: https://hub.docker.com/u/sagemath/ * admin: embray, jrueth * other: slelievre also has push access |
|
| Line 120: | Line 161: |
| * tmonteil: this is a ''whishlist'', not something collectively decided. Note however that almost nothing in the current framework was collectively discussed either. | * tmonteil: this is a ''wishlist'', not something collectively decided. Note however that almost nothing in the current framework was collectively discussed either. |
| Line 126: | Line 167: |
| * we got a VM at Orsay with 1Tb of disk, we are currently setting it up, and use it for more and more services. | * we got a VM at [[https://www.math.u-psud.fr/|Orsay math department]] with 1TB of disk, we are currently setting it up, and use it for more and more services. |
| Line 131: | Line 172: |
| * 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. |
* 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. |
| Line 140: | Line 181: |
| * 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 ? | * 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? |
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.
Contents
-
Current services
- DNS
- ask.sagemath.org
- backup
- 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
- GitHub organization for SageMath
- GitLab organization for SageMath
- build.sagemath.org
- patchbot.sagemath.org
- rsync.sagemath.org
- sageb0t
- sagecell.sagemath.org
- sagenb.org
- wiki.sagemath.org
- zulip.sagemath.org
- combinat.sagemath.org
- DockerHub organization
- Planned services (wishlist)
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
contact: [email protected]
- local tech contact: David Alden, Josh Carroll
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
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
GitHub organization for SageMath
- admin: schilly, vbraun
GitLab organization for 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: see buildbot for more details
- resources needed: ?CPU ?RAM ?DISK
- admin: ??
- contact: ??
patchbot.sagemath.org
- 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
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
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:
www.uni-frankfurt.de (Frankfurt, Germany)
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
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, 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, jrueth (saraedum) - as of 2020-05.
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
purpose: distribute SageMath Docker images
hosted at: https://hub.docker.com/u/sagemath/
- admin: embray, jrueth
- other: slelievre also has push access
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
- purpose: backup between remote hosts, local backups can be destroyed
- schilly: backup of what?
tmonteil: backup of the data of the services we maintain: ask, trac, git, wiki,... according to [https://groups.google.com/forum/#!msg/sage-devel/ed_ya-d-k_E/5csVA6wsCwAJ this] [http://comments.gmane.org/gmane.comp.mathematics.sage.devel/84894 post] there is currently no regular backup at all for those services (except ask, that benefits for a semi-automatic backup system), this is why i proposed to have a server dedicated to that, located in a different place than the other services.
we got a VM at Orsay math department with 1TB of disk, we are currently setting it up, and use it for more and more services.
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?