welcome: please sign in

Diff for "AdminArea"

Differences between revisions 35 and 73 (spanning 38 versions)
Revision 35 as of 2007-03-03 17:48:14
Size: 4718
Editor: AdamChlipala
Comment: All the to-do items I can think of
Revision 73 as of 2007-05-03 13:32:49
Size: 6196
Editor: MichaelOlson
Comment: locase my handle
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:

= Final preparations =

See page NewServersSetup/FinalPreparations.
Line 14: Line 18:
 * OneTimeCosts2007: Costs associated with the new servers through April 2007
Line 23: Line 28:
 * Get Apache dynamic content execution on mire working with AFS.
 * Get Exim filter execution on deleuze working with AFS.
 * Mailman?
 * Make ca@hcoop.net e-mail address working. It's the address that will be used in the certificate files.
 * Fix resolv.conf on both servers to have multiple good DNS servers for now, set it to use localhost once BIND is running and configured.
 * Figure out how to use Dell OMSA or other tools to monitor RAID and other hardware.
 * Configure exim4. --MichaelOlson
 * Configure Courier IMAP daemons, reviewing fyodor's config. --MichaelOlson
 * Configure Squirrel``Mail to use imapproxyd, which should give speed improvements once we migrate to deleuze. --MichaelOlson
 * Configure Exim to use deleuze as a smarthost. --MichaelOlson
 * Megacz
    * Make /afs/hcoop.net/common/etc/scripts/apache-sync-logs work
 * mwolson
    * Perform testing on procmail and exim filter on deleuze.
    * Migrate site-specific (read: non-AFS) changes to apache 1.X on mire (read: check to see if this has already been done).


=== Misc ===
 * Unclaimed
   * Make ca@hcoop.net e-mail address working. It's the address that will be used in the certificate files.
   * Make sure somebody is reading mail sent to abuse@hcoop.net so we don't wind up on lame DNSBLs
   * Fix resolv.conf on both servers to have multiple good DNS servers for now, set it to use localhost once BIND is running and configured.
   * Figure out how to use Dell OMSA or other tools to monitor RAID and other hardware.
   * Do performance testing on the new configuration, by having admins or other users monitor performance on mire (using vmstat, top, mytop, etc) and having one or more (perhaps multi-threaded) scripts requesting web pages from somewhere off of the Peer 1 network.
 * mwolson
    * Run simple tests on cron to see if it works.
    * Mailman
      * The exim side of things has been mostly set up.
      * I think I migrated the non-exim stuff as well, but will need to double-check.
      * Need to think of a way to test this, perhaps with help from a migrated user.
Line 36: Line 51:
 * Watchdog process to kill resource hogs
 * Migrate ejabberd mnesia db just before the dns switchover.
 * Set up back-up regime, possibly using [http://rsync.net/ rsync.net].
 * Get miscellaneous web stuff ported, like membership application, vmail password change, publicly-viewable statistics on membership, bandwidth usage stats, ....
 * Unclaimed
  
* Watchdog process to kill resource hogs
   * Migrate ejabberd mnesia db just before the dns switchover.
   * Set up back-up regime, possibly using [http://rsync.net/ rsync.net].
   * Get miscellaneous web stuff ported, like membership application, vmail password change, publicly-viewable statistics on membership, bandwidth usage stats, ....
Line 73: Line 88:
 * Configure exim4. --MichaelOlson
 * Configure Courier IMAP daemons, reviewing fyodor's config. --MichaelOlson
 * Migrate squirrelmail configuration settings from fyodor.
 * Configure Squirrel``Mail to use imapproxyd, which should give speed improvements once we migrate to deleuze. --MichaelOlson
 * Exim filters
    * (a method has been set up by MichaelOlson, but it needs testing).
 * DNS server
    * Works on deleuze, although I will test once more domains have been migrated for reasonable domain defaults --JustinLeitgeb
 * nscd process for name caching
    * Currently this processes is set to do hostname caching on deleuze, so bind will not be set up as a caching name server --JustinLeitgeb
 * Get exim working on mire --MichaelOlson

Introduction

TableOfContents

Final preparations

See page NewServersSetup/FinalPreparations.

Special topic pages about migration and new set-up

The following are outdated:

To-do list

Before beginning to migrate members

  • Megacz
    • Make /afs/hcoop.net/common/etc/scripts/apache-sync-logs work
  • mwolson
    • Perform testing on procmail and exim filter on deleuze.
    • Migrate site-specific (read: non-AFS) changes to apache 1.X on mire (read: check to see if this has already been done).

Misc

  • Unclaimed
    • Make ca@hcoop.net e-mail address working. It's the address that will be used in the certificate files.

    • Make sure somebody is reading mail sent to abuse@hcoop.net so we don't wind up on lame DNSBLs

    • Fix resolv.conf on both servers to have multiple good DNS servers for now, set it to use localhost once BIND is running and configured.
    • Figure out how to use Dell OMSA or other tools to monitor RAID and other hardware.
    • Do performance testing on the new configuration, by having admins or other users monitor performance on mire (using vmstat, top, mytop, etc) and having one or more (perhaps multi-threaded) scripts requesting web pages from somewhere off of the Peer 1 network.
  • mwolson
    • Run simple tests on cron to see if it works.
    • Mailman
      • The exim side of things has been mostly set up.
      • I think I migrated the non-exim stuff as well, but will need to double-check.
      • Need to think of a way to test this, perhaps with help from a migrated user.

During migration

  • Unclaimed
    • Watchdog process to kill resource hogs
    • Migrate ejabberd mnesia db just before the dns switchover.
    • Set up back-up regime, possibly using [http://rsync.net/ rsync.net].

    • Get miscellaneous web stuff ported, like membership application, vmail password change, publicly-viewable statistics on membership, bandwidth usage stats, ....

Global Notes

  • To edit LDAP database from a GUI tool, use gq program

  • To connect to hcoop's ldap server using gq, create a SSH tunnel: ssh -p 2222 -f -N -L 389:localhost:389 USERNAME@69.90.123.67, and then connect to localhost:389 in gq.

  • For the description of the actual authentication scheme, see AuthenticationScheme.

Tasks done

Deleuze

This machine donated by Justin Leitgeb seems real nice. Buffered disk throughput is about 1.5 GB/s. Raw disk reads are 60 MB/s for the two 36 GB disks and 120 MB/s for the 4-disk array. Not bad at all.

  • Removed excessive packages, cleaned up the system
  • Installed changetrack to monitor all config file changes. The program uses rcs and automatically keeps previous revisions. It is ran from cron on a daily basis.

  • Installed debsums to monitor file md5sums

  • Installed Courier IMAP and IMAP-SSL
  • Installed LDAP for user authentication. The system is currently configured to use LDAP and fallback to the usual /etc/ files. Admin users will be added locally on all machines and will be able to log in even when LDAP is not operational.

  • Installed MIT Kerberos 5
  • Fixed date/time on the system. Installed ntpd

  • Installed TLS support for LDAP. Certificate file is /etc/ldap/server.pem, and ldap/ldaps ports are 389/636.

  • Installed Linux 2.6.18.3-grsec with 2.6.18-mm3 patches (2) for megaraid.
    • The patches and source tree installed, along with the .deb generated, is under /usr/src/ntk2. I set up sockets groups as on fyodor (7070-7072). SMP, with hyperthreading enhancements, is enabled. I also installed a bunch of packages that someone were uninstalled while I was gone (e.g., gcc). I also fixed the sudoers, wheel group, and admin home directories. --NathanKennedy

  • Kerberos + LDAP works.
  • Compiled requisite kernel modules, compiled and installed new OpenIPMI package, and installed dellomsa. Dell OMSA is now working. --NathanKennedy

  • Install SSH.
  • Permit new admins to log in by copying their SSH keys to their newly-created (empty) home directories.
  • Install AFS (need to repeat the reading on AFS and how it really works. Also it will influence the decision how to format /dev/sdb in the system) -- DavorOcelic

  • Install MySQL and PostgreSQL (input from AFS step and admin discussion needed to see how to exactly configure this).
  • Install BIND.
  • Install and configure Apache, to serve static web content only. --MichaelOlson

  • Review kernel configuration and install testnet. -- DavorOcelic

  • Configure exim4. --MichaelOlson

  • Configure Courier IMAP daemons, reviewing fyodor's config. --MichaelOlson

  • Migrate squirrelmail configuration settings from fyodor.
  • Configure SquirrelMail to use imapproxyd, which should give speed improvements once we migrate to deleuze. --MichaelOlson

  • Exim filters
    • (a method has been set up by MichaelOlson, but it needs testing).

  • DNS server
    • Works on deleuze, although I will test once more domains have been migrated for reasonable domain defaults --JustinLeitgeb

  • nscd process for name caching
    • Currently this processes is set to do hostname caching on deleuze, so bind will not be set up as a caching name server --JustinLeitgeb

  • Get exim working on mire --MichaelOlson

Mire

  • Installed new second SCSI hard drive, reinstalled debian, and configured the drives with software RAID-1. --NathanKennedy

  • Configured Mire to work as a proper krb/ldap/afs client machine. --DavorOcelic

Custom software

AdminArea (last edited 2020-08-23 22:16:03 by ClintonEbadi)