welcome: please sign in

Diff for "AdminArea"

Differences between revisions 36 and 130 (spanning 94 versions)
⇤ ← Revision 36 as of 2007-03-03 18:50:51 →
Size: 4761
Editor: MichaelOlson
Comment: Move exim4 to done list, since the initial part is done; just need to test
← Revision 130 as of 2010-01-06 01:05:53 → ⇥
Size: 3273
Editor: DavorOcelic
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Introduction = #pragma section-numbers off
Line 3: Line 3:
[[TableOfContents]] This contains a list of pages that are of interest to the admins.
Line 5: Line 5:
= Special topic pages about migration and new set-up = <<TableOfContents>>
Line 7: Line 7:
 * 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		 = Sysadmin work =
Line 15: Line 9:
The following are outdated: Links to detailed policies, procedures and information specific to HCoop. The resources here should allow HCoop admin team members to share information about every part of the complete system, and to allow easier training of future team members.
Line 17: Line 11:
 * ColocationNextSteps: Listing of things to do after getting the hardware. = Keeping track =
Line 19: Line 13:
= To-do list = == On-site visits ==
 * OnSiteVisits: Records of visits by HCoop volunteers to our colocation facilities
Line 21: Line 16:
== Before beginning to migrate members == == Responsibilities ==
 * TaskDistribution: What each sysadmin is responsible for.
 * VolunteerResponsePolicy: Guidelines for responding to requests and email.
 * AdminArea/ListOfVolunteers who can help us do stuff...
 * AdminGroup: Listing of people who can delete pages and despam pages on the wiki.
Line 23: Line 22:
 * 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.
 * Make sure Exim works with AFS.
 * 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 on mire to use deleuze as a smarthost. --MichaelOlson		 == Technical Records ==
 * IpAddresses: Listing of IPs that we use.
 * [[Hardware]]: Information on HCoop hardware.
 * HcoopAddresses: Physical addresses relevant to us.
Line 34: Line 27:
== 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, ....		 == Misc ==
 * RoadMaps: Detailed plans for future events.
Line 42: Line 31:
= Global Notes = = Sysadmin Stuff =
Line 44: Line 33:
 * 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.		 (The information from this point below is mostly current, but the arrangement and text are possible subjects for update).
Line 48: Line 35:
= Tasks done =  * AndrewFileSystem: Using our shared filesystem.
 * AuthenticationScheme: How authentication works on our systems.
 * DomTool: Administering and using domtool.
 * TipsAndTricks
 * DaemonFileSecurity
 * EtcKeeper: Use this to keep track of config changes.
Line 50: Line 42:
== Deleuze == == General Sysadmin ==
 * BackupInfo: Information on how to recover deleted files from our off-site backups.
 * SetupNewMachines: How to put the basic hcoop AFS/Kerberos client config on a newly acquired machine.
 * DebianPackaging: How to make custom HCoop Debian packages.
 * KvmAccess: How to use the remove KVM and avoid going on site.
 * KvmInfo
 * UserManagement only talks about adduser/deluser right now.
 * ResourceLimits
 * InstalledSoftware lists non-debian installed software.
 * SystemAuthentication lists authentication
 * UsingResourceLimits If this is still accurate, we should move it to MemberManual area.
Line 52: Line 54:
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. == Specific Services/Tasks ==
 * DaemonAdmin: How to set up various daemons (subpages for various services, should be linked from here.).
 * MailMan contains no information...
 * SetupNewAfsServer: How to set up a new AFS server.
 * MemberFreezing: How to freeze and unfreeze members who get behind on dues
 * AdminUserSetup lists steps to create (blank), delete, and change passwords of admin users.
 * ChangingAdminPassword: How admins can change their UNIX passwords.
 * CertificateAuthority: How to sign user SSL certificates and the like.
 * ZoneTransfers is also mostly blank.
 * PrincipalsForNonHumans talks about kerberos for automated tasks.
 * SpamAssassinAdmin
Line 54: Line 66:
 * 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		 == Specific Machines ==
 * PowerEdge2850 is about '''deleuze'''
 * RebootingDeleuze: Steps to take after rebooting deleuze.
 * RebootingMireSp: How to reboot mire using its SP interface.
 * HopperServiceProcessor
 * KrunkInfoz
Line 75: Line 73:
= 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		 = Historical =
 * SoftwareArchitecturePlans: Plans for software installation.
 * SystemArchitecturePlans: Plans regarding our hardware.
 * InstallationLog contains ancient (~2005) records of installation of software and hardware

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

Contents

  1. Sysadmin work
  2. Keeping track
    1. On-site visits
    2. Responsibilities
    3. Technical Records
    4. Misc
  3. Sysadmin Stuff
    1. General Sysadmin
    2. Specific Services/Tasks
    3. Specific Machines
  4. Historical

Sysadmin work

Links to detailed policies, procedures and information specific to HCoop. The resources here should allow HCoop admin team members to share information about every part of the complete system, and to allow easier training of future team members.

Keeping track

On-site visits

  • OnSiteVisits: Records of visits by HCoop volunteers to our colocation facilities

Responsibilities

Technical Records

Misc

  • RoadMaps: Detailed plans for future events.

Sysadmin Stuff

(The information from this point below is mostly current, but the arrangement and text are possible subjects for update).

General Sysadmin

Specific Services/Tasks

Specific Machines

Historical

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