welcome: please sign in

Diff for "AdminArea"

Differences between revisions 21 and 97 (spanning 76 versions)
⇤ ← Revision 21 as of 2006-12-09 21:45:56 →
Size: 4379
Editor: ri02-226
Comment:
← Revision 97 as of 2007-11-12 19:31:28 → ⇥
Size: 1198
Editor: MichaelOlson
Comment: Move OneTimeCosts2007 link
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Introduction = #pragma section-numbers off
Line 3: Line 3:
To get the whole picture, also see pages ColocationNextSteps, SystemArchitecturePlans and NewSystemHardware. This contains a list of pages that are of interest to the admins.
Line 7: Line 7:
= Special topic pages about migration and new set-up = = General =
Line 9: Line 9:
 * AndrewFileSystem: Using our new shared filesystem
 * DomTool: Administering and using the new domtool		  * AdminGroup: Listing of HCoop system administrators.
 * AndrewFileSystem: Using our new shared filesystem.
 * AuthenticationScheme: How authentication works on our systems.
 * BackupInfo: Information on how to recover deleted files from our off-site backups.
 * ChangingAdminPassword: How admins can change their UNIX passwords.
 * DomTool: Administering and using the new domtool.
 * IpAddresses: Listing of IPs that we use.
 * NewSystemHardware: Information on the new hardware.
 * SoftwareArchitecturePlans: Plans for software installation.
 * SystemArchitecturePlans: Plans regarding our hardware.
 * OnSiteStuff: Checklist for the next on-site visit to the new machines.
 * HcoopAddresses: Physical addresses relevant to us.
Line 12: Line 22:
= Global TODO = = Responsibilities =
Line 14: Line 24:
 * Make ca@hcoop.net e-mail address working. It's the address that will be used in the certificate files.  * TaskDistribution: What each sysadmin is responsible for.
 * VolunteerResponsePolicy: Guidelines for responding to requests and email.
Line 16: Line 27:
= Global Notes = = Programs =
Line 18: Line 29:
 * 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.

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

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

== 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.
 * Install MySQL and PostgreSQL (input from AFS step and admin discussion needed to see how to exactly configure this) -- DavorOcelic
 * Install BIND -- DavorOcelic
 * Review kernel configuration and install testnet. -- DavorOcelic
 * Install and configure Apache, to serve static web content only. --MichaelOlson
 * 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.

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

= 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

= 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		  * DaemonAdmin: Daemon-specific pages aimed at admins.
 * MailmanInstallation: Additional things we must do to keep Mailman happy.

This contains a list of pages that are of interest to the admins.

TableOfContents

General

Responsibilities

Programs

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