Differences between revisions 82 and 83
⇤ ← Revision 82 as of 2021-05-17 17:36:23 →
Size: 9496
Editor: tmonteil
Comment:
← Revision 83 as of 2022-04-06 18:03:19 → ⇥
Size: 7026
Editor: mkoeppe
Comment: Remove outdated "wishlist"
Deletions are marked like this. Additions are marked like this.
Line 162: Line 162:

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

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

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

  1. Current services
    1. DNS
    2. ask.sagemath.org
    3. backup
    4. doc.sagemath.org, planet.sagemath.org, www.sagemath.org
    5. files.sagemath.org, fileserver.sagemath.org, old.files.sagemath.org
    6. git.sagemath.org, trac.sagemath.org
    7. GitHub organization for SageMath
    8. GitLab organization for SageMath
    9. build.sagemath.org
    10. patchbot.sagemath.org
    11. rsync.sagemath.org
    12. sageb0t
    13. sagecell.sagemath.org
    14. sagenb.org
    15. wiki.sagemath.org
    16. zulip.sagemath.org
    17. DockerHub organization

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

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

Infrastructure (last edited 2023-02-23 20:12:25 by mkoeppe)