welcome: please sign in

Diff for "AdminArea"

Differences between revisions 45 and 93 (spanning 48 versions)
⇤ ← Revision 45 as of 2007-03-12 05:32:22 →
Size: 6766
Editor: netblock-68-183-25-2
Comment:
← Revision 93 as of 2007-10-24 22:56:36 → ⇥
Size: 954
Editor: MichaelOlson
Comment: Make this a portal for admins
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from NewServersSetup
Line 5: Line 6:
= Special topic pages about migration and new set-up = = Special topic pages about the new set-up =
Line 8: Line 9:
 * BackupInfo: Information on how to recover deleted files from our off-site backups.
 * ChangingAdminPassword: How admins can change their UNIX passwords.
Line 10: Line 13:
 * IpAddresses: Listing of IPs that we use (nonpublic).
Line 14: Line 18:

The following are outdated:

 * ColocationNextSteps: Listing of things to do after getting the hardware.

= To-do list =

== Before beginning to migrate members ==

=== Per-User Tasks (also need to be included in adduser) ===
 * Add user/cgi@HCOOP.NET principal
    * Generate keytab and put it somewhere where the user can't get it
 * Add user/email@HCOOP.NET principal
    * Generate keytab and put it somewhere where the user can't get it
    * should we call this user/procmail@HCOOP or similar to make it clear that it's only for execution of scripts in response to email arrivals? In particular, this principal is not involved in ''reading'' email.
 * make a maildir at /afs/hcoop.net/common/email/USER
    * doing this for at least one account is blocking Exim delivery testing
 * rename /afs/hcoop.net/usr/username to /afs/hcoop.net/user/u/us/username
 * fs mkm XXX user.username.backup
    * XXX = /afs/hcoop.net/u/us/username/.OldFiles/
        * Advantage: "CMU style"; typical location
    * XXX = /afs/hcoop.net/oldfiles/u/us/username/
        * Advantage: doesn't confuse find(1) and other tools by creating symlink-free cycles in the filesystem

=== Getting Various Daemons to Run with AFS Tokens ===

 * Exim filters
    * (a method has been set up by MichaelOlson, but it needs testing).
 * Courier on deleuze
 * Apache Dynamic Content. Our options are:
       1. Use Apache 1.3 to serve dynamic content (use umbc mod_waklog, which is designed for exactly what we're trying to do)
       1. Support only CGI dynamic content (no PHP, mod_perl, etc) and use a kstart hack to wrap each CGI process.
       1. Serve all dynamic content using a single monolithic AFS identity such as cgi@HCOOP.NET
          * not very useful since this is essentially equivalent to system:authuser@HCOOP.NET
       1. Have each user run their own Apache instance.
       1. Wait for mod_waklog to work properly on Apache 2.0 (may take unbounded amount of time)

=== Other ===
 * 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 Exim on mire to use deleuze as a smarthost. --MichaelOlson
 * 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.

== During migration ==

 * 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 Squirrel``Mail to use imapproxyd, which should give speed improvements once we migrate to deleuze. --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 =

 * DomtoolTwo
 * Vmail tools
 * Web portal		  * OnSiteStuff: Checklist for the next on-site visit to the new machines.
 * OneTimeCosts2007: Costs associated with the new servers through April 2007
 * HcoopAddresses: Physical addresses relevant to us

1. Introduction

TableOfContents

2. Special topic pages about the new set-up

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