Differences between revisions 43 and 69 (spanning 26 versions)
Revision 43 as of 2016-03-23 19:35:05
Size: 8746
Editor: chapoton
Comment: typo + moving things
Revision 69 as of 2019-08-22 18:35:10
Size: 8609
Editor: chapoton
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:

<<TableOfContents()>>
Line 15: Line 17:
  * hosted at: Ohio State University (Niles Johnson's university)   * hosted at: [[https://www.osu.edu/|Ohio State University]]
Line 18: Line 20:
  * admin: niles, tmonteil, vedlecroix, slelievre, kcrisman, mhansen   * admin: niles, tmonteil, vdelecroix, slelievre, kcrisman, mhansen
Line 20: Line 22:
  * local tech contact: David Alden
Line 21: Line 24:
== cloud.sagemath.com ==
  * what: a cloud service for computation and collaboration
  * operated by: Sagemath, Inc
  * url: http://cloud.sagemath.com
== backup ==
  * purpose: keep the data of various services in a separate place
  * hosted at: [[http://www.math.u-psud.fr/?lang=fr|Mathematics lab]], University Paris South (Orsay)
  * technology used: debian, rsync, rssh, rsnapshot
  * resources needed: 1TB disk
  * admin: tmonteil, slelievre
  * local sage dev: slelievre
  * local tech contact: Mathilde Rousseau
Line 34: Line 41:
== dockerhub ==
  * purpose: docker container for SageMath
  * url: https://hub.docker.com/u/sagemath/
  * admin: vbraun, sebasguts

== files.sagemath.org, old.files.sagemath.org ==
== files.sagemath.org, fileserver.sagemath.org, old.files.sagemath.org ==
Line 53: Line 55:
  * 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, tmonteil, dimpase
Line 57: Line 59:
  * url: http://github.com/sagemath   * https://github.com/sagemath
Line 59: Line 61:

== GitLab organization for SageMath ==

  * https://gitlab.com/sagemath
  * admin: embray, jrueth
Line 70: Line 77:
  * 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

== GSoC, Google Summer of Code ==
  * url: http://wiki.sagemath.org/GSoC
  * admin up to 2015: schilly
  * 2016: schilly

== Packaging for Linux ==

=== arch-linux package ===
  * purpose: easy-to-install arch-linux package
  * maintainer: Antonio Rojas
  * hosted at: https://www.archlinux.org/packages/community/x86_64/sagemath/

=== Fedora package ===
  * purpose: easy-to-install Fedora package
  * maintainer: Paulo Cesar Pereira de Andrade (pcpa)
  * hosted at: https://apps.fedoraproject.org/packages/sagemath
  * other link: https://fedoraproject.org/wiki/SIGs/SciTech/SAGE

=== Gentoo: Sage-on-Gentoo ===
  * repository: https://github.com/cschwan/sage-on-gentoo
  * admin: fbissey, cschwan

=== RPM package ===
  * what: links to sagemath packages for the rpm package manager (Fedora, Mandriva)
  * hosted at: http://rpmfind.net/linux/rpm2html/search.php?query=sagemath

=== Ubuntu PPA ===
  * purpose: easy-to-install Ubuntu .deb packages
  * hosted at: launchpad.net
  * admin: 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
Line 114: Line 93:
     * RAM 2-3 gb (mostly for caching when calculating hashes)      * RAM 2-3 GB (mostly for caching when calculating hashes)
Line 119: Line 98:
== sageb0t ==
  * purpose: turn pull requests on !GitHub into trac tickets
  * contact: robertwb
Line 122: Line 105:
    * 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 132: Line 115:
  * available urls: http://aleph.sagemath.org, http://sagecell.sagemath.org

== SageDebianLive ==
  * purpose: a live usb stick with Debian, Sage, and more open-source software
  * admin: tmonteil
  * hosted at: http://sagedebianlive.metelu.net/
  * mailing list: https://sagedebianlive.metelu.net/mailman/listinfo/devel
  * available urls: http://aleph.sagemath.org, https://sagecell.sagemath.org
Line 142: Line 119:
  * state: end of life, replaced by [[http://cloud.sagemath.com]]
  * volunteers: dimpase, tmonteil, vdelecroix

== social networks ==

=== Facebook ===
  * url: https://www.facebook.com/Sage-Math-26593144945/
  * admin: schilly

=== Google+ ===
  * url: https://plus.google.com/+sagemath
  * admin: schilly

=== Twitter ===
  * url: https://twitter.com/sagemath
  * admin: schilly
  * state: end of life, replaced by [[https://cocalc.com/|CoCalc]]
  * volunteers to provide worksheets back to the users: dimpase, tmonteil, vdelecroix
Line 160: Line 123:
  * purpose: the wiki you are currently reading!
  * hosted at: UW, going to move soon
  * purpose: the wiki you are reading!
  * hosted at: UW, going to move soon (moved to cloud.google.com ?)
Line 164: Line 127:
  * admin: currently, the people with root access are : kclawson,wstein,ohanar,mmarco,tmonteil,dimpase   * admin: people with root access: kclawson, wstein, ohanar, mmarco, tmonteil, dimpase
Line 166: Line 129:
  * 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 168: Line 131:
== zulip.sagemath.org ==
  * purpose: chat system
  * hosted at: cloud.google.com
  * resources needed: a dedicated VM with 2-4GB of RAM
  * admin: roed

== combinat.sagemath.org ==
  * purpose: ? (holds a copy of the mercurial patches of sage-combinat)
  * hosted at: UW ?
  * 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 172: Line 154:
  * 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 178: Line 160:
     * 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 182: Line 165:
    * 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 191: Line 174:
     * 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.

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: Ohio State University

  • technology used: ubuntu, nginx, uwsgi, postgesql, askbot
  • resources needed: database on a separate VM, 2GB RAM, 10GB disk
  • admin: niles, tmonteil, vdelecroix, slelievre, kcrisman, mhansen
  • contact: [email protected]

  • local tech contact: David Alden

backup

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

  • technology used: debian, rsync, rssh, rsnapshot
  • 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

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?

git.sagemath.org, trac.sagemath.org

  • purpose: development tools, they share the same host
  • hosted at: UW, going to move soon
  • technology used: ubuntu, apache, git, trac
  • resources needed: ?CPU ?RAM ?DISK
  • admin: people with root access: kclawson, ohanar, vbraun, mderickx, robertwb, wstein, tmonteil, dimpase
  • contact: no real organisation yet, go to sage-devel

GitHub organization for SageMath

GitLab organization for SageMath

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
  • 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: UW
  • 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:
  • 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: UW, going to move soon (moved to cloud.google.com ?)
  • technology used: ubuntu, apache, moinmoin
  • resources needed: ?CPU ?RAM ?DISK
  • admin: people with root access: kclawson, wstein, ohanar, mmarco, tmonteil, 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

combinat.sagemath.org

  • purpose: ? (holds a copy of the mercurial patches of sage-combinat)
  • hosted at: UW ?
  • technology used: ?
  • resources needed: ?CPU ?RAM ?DISK
  • admin: people with root access: schilly?
  • contact: ?

DockerHub organization

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

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?

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