Differences between revisions 24 and 48 (spanning 24 versions)
Revision 24 as of 2015-05-24 16:47:41
Size: 4205
Editor: schilly
Comment:
Revision 48 as of 2016-07-18 08:00:44
Size: 7422
Editor: slelievre
Comment: Add sageb0t
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.
Line 4: Line 5:


<<TableOfContents()>>
Line 13: Line 18:
  * purpose: webserver wher users can get support   * purpose: webserver where users can get support
Line 17: Line 22:
  * admins: niles, tmonteil, vedlecroix, slelievre, kcrisman, mhansen   * admin: niles, tmonteil, vedlecroix, slelievre, kcrisman, mhansen
Line 20: 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
Line 21: Line 31:
== 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, 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: currently, the people with root access are : kclawson,ohanar,vbraun,mderickx,robertwb,wstein,tmonteil,dimpase
  * contact: no real organisation yet, go to sage-devel

== GitHub organization for SageMath ==
  * url: http://github.com/sagemath
  * admin: schilly, vbraun
Line 27: Line 65:
  * admins: ?robertwb?
  * contact: ?robertwb?


== doc.sagemath.org planet.sgaemath.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
  * admins: everyone who is on the github group for sagemath
  * contact: schilly for the website


== 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: ?
  * contact: ?
  * admin: ??
  * contact: ??
Line 52: Line 71:
  * technology used: ubuntu, custom flask code?, see [[buildbot]] for more details
  * resources needed: ?CPU ?RAM ?DISK
  * admins: ?robertwb?
  * contact: ?robertwb?

==
PPA ==
  * pur
pose: easy-to-install Ubuntu .deb packages
  * hosted at: launchpad.net
  * admins: pipedream
  * contact: https://launchpad.net/~aims/+archive/ubuntu/sagemath
  * technology used: centos, custom flask, mongodb, see [[buildbot]] for more details
  * resources needed: Minimal CPU, RAM. ~25GB disk.
  * admin: robertwb, chapoton
  * contact: robertwb, chapoton
Line 72: Line 84:
  * admins: schilly   * admin: schilly
Line 75: Line 87:
== sageb0t ==
  * purpose: turn pull requests on !GitHub into trac tickets
  * contact: robertwb
Line 78: Line 93:
  * 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 (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, http://sagecell.sagemath.org
Line 87: Line 108:
  * state: end of life, still needs some support to provide backup of their worksheets to former users
  * volunteers: dimpase, tmonteil, vdelecroix
  * state: end of life, replaced by [[http://cloud.sagemath.com]]
  * volunteers to provide worksheets back to the users : dimpase, tmonteil, vdelecroix
Line 93: Line 113:
  * hosted at: ?UW?   * hosted at: UW, going to move soon
Line 96: Line 116:
  * admins: ?
  * contact: ?
  * possible issue in migration: it share the same db of users acounts than trac.

== sagemath files ==
  * purpose: main files for rsync and backup of "other" files
  * hosted at: UW and other places ?
  * schilly: this should get its own subdomain files.sagemath.org
  * admin: currently, the people with root access are : kclawson,wstein,ohanar,mmarco,tmonteil,dimpase
  * contact: no real organisation yet, go to sage-devel
  * possible issue in migration: the db of user acounts is synced from trac when this latter is modified (incron)
Line 108: Line 123:
schilly: who wishes this and did define those purposes based on what discussion?   * schilly: who wishes this and did define those purposes based on what discussion?
  * tmonteil: this is a ''whishlist'', not something collectively decided. Note however that almost nothing in the current framework was collectively discussed either.
Line 113: Line 129:
     * 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.
Line 117: Line 135:
    * 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 118: Line 138:
    * 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
Line 122: Line 144:
     * 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 (Niles Johnson's university)
  • technology used: ubuntu, nginx, uwsgi, postgesql, askbot
  • resources needed: database on a separate VM, 2GB RAM, 10GB disk
  • admin: niles, tmonteil, vedlecroix, slelievre, kcrisman, mhansen
  • contact: sage-askbot-admin@googlegroups.com

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

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, 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: currently, the people with root access are : kclawson,ohanar,vbraun,mderickx,robertwb,wstein,tmonteil,dimpase
  • contact: no real organisation yet, go to sage-devel

GitHub 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: ?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

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:
    • Goethe-Universität (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, http://sagecell.sagemath.org

sagenb.org

  • purpose: public notebook,
  • state: end of life, replaced by http://cloud.sagemath.com

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

wiki.sagemath.org

  • purpose: the wiki you are currently reading!
  • hosted at: UW, going to move soon
  • technology used: ubuntu, apache, moinmoin
  • resources needed: ?CPU ?RAM ?DISK
  • admin: currently, the people with root access are : kclawson,wstein,ohanar,mmarco,tmonteil,dimpase
  • contact: no real organisation yet, go to sage-devel
  • possible issue in migration: the db of user acounts is synced from trac when this latter is modified (incron)

Planned services (wishlist)

  • schilly: who wishes this and did define those purposes based on what discussion?
  • tmonteil: this is a whishlist, 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 ?