welcome: please sign in

Diff for "AdminArea"

Differences between revisions 2 and 30 (spanning 28 versions)
Revision 2 as of 2006-11-21 21:56:06
Size: 4330
Editor: ri02-128
Comment:
Revision 30 as of 2007-01-17 02:20:09
Size: 4946
Editor: MichaelOlson
Comment: Remove PAM todo item
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Introduction =

[[TableOfContents]]

= Special topic pages about migration and new set-up =

 * AndrewFileSystem: Using our new shared filesystem
 * DaemonAdmin: Daemon-specific pages aimed at admins
 * DomTool: Administering and using the new domtool
 * NewSystemHardware: Information on the new hardware
 * TaskDistribution: What each sysadmin is responsible for
 * SoftwareArchitecturePlans: Plans for software installation
 * SystemArchitecturePlans: Plans regarding our hardware

The following are outdated:

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

= Global TODO =

 * Make ca@hcoop.net e-mail address working. It's the address that will be used in the certificate files.
 * Migrate ejabberd mnesia db just before the dns switchover.

= 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.
Line 17: Line 46:
 * Kerberos works.  * 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
Line 23: Line 59:
 * LDAP working with kerberos. Documentation on this is lacking. -- DavorOcelic
Line 25: Line 60:
 * 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) -- DavorOcelic
 * Install BIND -- DavorOcelic
Line 29: Line 61:
 * See why db4.2 recover takes a long time on LDAP restart if anything is modified in the directory -- DavorOcelic
 * Install and configure Apache, to serve static web content only.
Line 32: Line 62:
 * 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 squirrelmail to use imapproxyd, which should give speed improvements once we migrate to deleuze. --MichaelOlson
Line 35: Line 69:
 * When executing '''kinit; ldapsearch -H ldaps:/// -I -b "" -s base -LLL supportedSASLMechanisms''', instead of the correct answer, LDAP server dumps "Cannot open /etc/sasldb2" in error logs. This is a Berkeley DB file used when SASL assumes plain text identification, but here this is not the case (we want Kerberos authentication). I think the problem is in the lack of "{KERBEROS}" password type in userPassword LDAP field. I need to see if the problem simply consists of adding this option in the schema, or its unavailability suggests that LDAP can't do that. -- DavorOcelic
Line 37: Line 70:
 * The logical volume for /dev/sdb is supposed to be a 4-drive raid array, each drive ~73GB. Right now it seems to be configured as RAID1 mirroring the two drives, for a capacity of ~146G (see dmesg, for instance). This would be faster and the volume would be 73G bigger if it was set up as RAID5. I might need to do this from console, and I need to talk to Justin about it, since he set up the logical volumes and I thought he said that sdb was RAID5. --NathanKennedy
Line 41: Line 73:
 * DomtoolTwo  * DomtoolTwo (Adam, will it be possible to change/modify support requests from the command line? Also, it would be so "candy" if the messages regarding ticket status were sent as followups to the original request email, not as completely separate mails). -- DavorOcelic
Line 48: Line 80:

= Global TODO =

 * Make ca@hcoop.net e-mail address working. It's the address used in the certificate files.

= 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.51''', and then connect to ''localhost:389'' in ''gq''.
= Mire =
== Tasks done ==
 * 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

1. Introduction

TableOfContents

2. Special topic pages about migration and new set-up

The following are outdated:

3. Global TODO

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

  • Migrate ejabberd mnesia db just before the dns switchover.

4. 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.

5. 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.

5.1. Tasks done

  • 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

5.2. TODO

In order of implementation (soonest first):

  • 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.
  • Review kernel configuration and install testnet. -- DavorOcelic

  • Get domtool2 working (this to be done concurrent with mire).
  • 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 squirrelmail to use imapproxyd, which should give speed improvements once we migrate to deleuze. --MichaelOlson

5.3. Problems

  • With debsums, once you break md5sum of a config file, the file keeps being reported as mismatching even if you completely regenerate md5sums for a package!! -- DavorOcelic

6. Custom software

  • DomtoolTwo (Adam, will it be possible to change/modify support requests from the command line? Also, it would be so "candy" if the messages regarding ticket status were sent as followups to the original request email, not as completely separate mails). -- DavorOcelic

  • Vmail tools
  • Web portal
  • Watchdog process to kill resource hogs

These are my responsibility. Right now, I'm waiting for the more traditional stuff to be set up and stable before beginning. --AdamChlipala

7. Mire

7.1. Tasks done

  • 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

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