Differences between revisions 44 and 45
Revision 44 as of 2009-05-07 15:32:56
Size: 3241
Editor: RonnyAasen
Comment:
Revision 45 as of 2009-08-18 07:14:47
Size: 3732
Editor: RonnyAasen
Comment: made web sites into links to ease testing when going to apache2
Deletions are marked like this. Additions are marked like this.
Line 32: Line 32:
    * (www.)skolelinux.{com,net,no}
    * popcon.skolelinux.org
    * bugs.skolelinux.(no,org)
    * friprogramvare.no
    * friprogramvareiskolen.no
    * i18n.skolelinux.no
    * www.linuxiskolen.no
    * www.skolelinux.org
    * www.spist.no
    * skoleknoppix.skolelinux.org
    * snofrix.skolelinux.org
    * nordiskknoppix.skolelinux.org
    * knoppix.skolelinux.org
    * cvs.cinelerra.org
    * www.cinelerra.org
    * bugs.cinelerra.org
    * planet.skolelinux.org
    * [[http://www.skolelinux.org|(www.)skolelinux.{com,net,org,no}]]
    * [[http://popcon.skolelinux.org|popcon.skolelinux.org]]
    * [[http://bugs.skolelinux.org|bugs.skolelinux.(no,org)]]
    * [[http://friprogramvare.no|friprogramvare.no]]
    * [[http://friprogramvareiskolen.no|friprogramvareiskolen.no]]
    * [[http://i18n.skolelinux.no|i18n.skolelinux.no]]
    * [[http://www.linuxiskolen.no|www.linuxiskolen.no]]
    * [[http://www.spist.no|www.spist.no]]
    * [[http://skoleknoppix.skolelinux.org|skoleknoppix.skolelinux.org]]
    * [[http://snofrix.skolelinux.org|snofrix.skolelinux.org]]
    * [[http://nordiskknoppix.skolelinux.org|nordiskknoppix.skolelinux.org]]
    * [[http://knoppix.skolelinux.org|knoppix.skolelinux.org]]
    * [[http://cvs.cinelerra.org|cvs.cinelerra.org]]
    * [[http://www.cinelerra.org|www.cinelerra.org]]
    * [[http://bugs.cinelerra.org|bugs.cinelerra.org]]
    * [[http://planet.skolelinux.org|planet.skolelinux.org]]

Overview about Debian-Edu/Skolelinux Infrastructure

Web Servers and Services:

Current situation

developer.skolelinux.org

  • {login problems}
  • Old package archives
  • Checkbot linkrot checker
  • Websites (developer.s.n) -> moved to maintainer

    • developer.skolelinux.no
  • powered down /!\

user.skolelinux.org

  • Login server for developers
  • Login server for lots of users (IRC, etc)
  • Subversion repository frontend (svn.skolelinux.org)
  • Old CVS repository frontend (cvs.skolelinux.no)
  • Selected web sites
    • svn.skolelinux.org
  • Recent svn client (working)
  • Nagios server

maintainer.skolelinux.org

administrator.skolelinux.no aka ftp.skolelinux.org

  • (restricted host)
  • DAK (archive server)
  • Upload queue for developer
  • rsync, ftp and http download for images and pools
  • building of CD images
  • Webserver (ftp.skolelinux.{org,no})
  • File server for the other machines (NFS):
    • Home directories for users
    • Subversion repository storage
    • Archive for old CVS repository

tester.skolelinux.org

  • Xen server for virtual hosts

ldap.skolelinux.org

  • Xen host on tester.skolelinux.org
  • LDAP server for nss/pam on the other machines

ghost.skolelinux.org

  • Xen host on tester.skolelinux.org
  • Available server for all developers and general use

security.skolelinux.org

  • (restricted host)
  • Xen host on tester.skolelinux.org
  • Build and test services for the security team


rt.debian.org

The Debian-Edu/Skolelinux Sysadmin Team (aka drift) is now using the debian ticket system on rt.debian.org. This means all bugreports and feature requests regarding the Debian-Edu/Skolelinux infrastructure should be directed to this ticket system. General information about how to use the ticket system can be found at http://wiki.debian.org/rt.debian.org.

The team uses three queues:

DESA - Incoming: Place for all new tickets, which will then be moved to one of the other queues. DESA: Public DESA queue DESA - private: Private DESA queue

If you are curious and want to check the status of your ticket, you can login to the ticket system on rt.debian.org by using "guest" as a user and "readonly" as the password. This user has access to the public DESA queue. Of course it is still possible to email drift@skolelinux.org for any queries, but we do prefer that you create a ticket for each request.