Differences between revisions 6 and 33 (spanning 27 versions)
Revision 6 as of 2015-05-18 14:06:44
Size: 1667
Editor: tmonteil
Comment:
Revision 33 as of 2016-01-21 18:10:50
Size: 5876
Editor: slelievre
Comment: Add more info about Linux packaging: arch-linux, Fedora, RPM
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.

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 wher 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

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

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

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

=== 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
  * admins: pipedream
  * contact: https://launchpad.net/~aims/+archive/ubuntu/sagemath

== 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)
  * admins: schilly
  * contact: schilly

== 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: dimpase, tmonteil, vdelecroix

== wiki.sagemath.org ==
  * purpose: the wiki you are currently reading!
  * hosted at: ?UW?
  * technology used: ubuntu, apache, moinmoin
  * resources needed: ?CPU ?RAM ?DISK
  * admin: ?
  * contact: ?
  * possible issue in migration: it share the same db of users acounts than trac.
Line 4: Line 131:
== ask.sagemath.org ==
  * purpose : webserver wher users can get support
  * hosted at : Ohio State University (Niles Johnson's university)
  * technology used : ubuntu, nginx, uwsgi, postgesql, askbot
  * admins : niles, tmonteil, vedlecroix, slelievre, kcrisman, mhansen
  * contact : sage-askbot-admin@googlegroups.com
= Planned services (wishlist) =
Line 11: Line 133:
schilly: who wishes this and did define those purposes based on what discussion?
Line 12: Line 135:
== 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
  * admins : ?robertwb?
  * contact : ?robertwb?
== backup ==
  * purpose: backup between remote hosts, local backups can be destroyed
     * schilly: backup of what?
Line 19: Line 139:
== 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
  * 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
Line 20: Line 145:
== git.sagemath.org and trac.sagemath.org ==
  * purpose : development tools, they share the same host
  * hosted at : ?UW?
  * technology used : ubuntu, apache, git, trac
  * admins : ?schilly?
  * contact : ?schilly?


== patchbot.sagemath.org ==
  * purpose : distribute and gathers automatic ticket testing on volunteer's machines
  * hosted at : ?UW?
  * technology used : ubuntu, custom flask code?, see [[buildbot]] for more details
  * admins : ?robertwb?
  * contact : ?robertwb?


== rsync.sagemath.org ==
  * purpose : the seed for mirrors, see MirrorNetwork for more details
  * hosted at : ?UW?
  * technology used : ?
  * admins : ?schilly?
  * contact : ?schilly?


== www.sagemath.org ==
  * purpose : web homepage
  * hosted at : github.io via fastly.net ?
  * technology used : proprietary?
  * admins : ?schilly?
  * contact : ?schilly?
== 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?

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 wher 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

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

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 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
  • 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

Packaging for Linux

arch-linux package

Fedora package

RPM package

Ubuntu PPA

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)
  • admins: schilly
  • contact: schilly

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: dimpase, tmonteil, vdelecroix

wiki.sagemath.org

  • purpose: the wiki you are currently reading!
  • hosted at: ?UW?
  • technology used: ubuntu, apache, moinmoin
  • resources needed: ?CPU ?RAM ?DISK
  • admin: ?
  • contact: ?
  • possible issue in migration: it share the same db of users acounts than trac.

Planned services (wishlist)

schilly: who wishes this and did define those purposes based on what discussion?

backup

  • purpose: backup between remote hosts, local backups can be destroyed
    • schilly: backup of what?

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
  • 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

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?