|
Size: 7030
Comment:
|
Size: 3624
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. | The linked pages are sorted based on relevance in day to day operations. That means the current admins will most often consult pages from the top of the list, while new admins or people wishing to get familiar with the setup will start from the end and move upwards. |
| Line 19: | Line 13: |
| = To-do list = | == Plans == |
| Line 21: | Line 15: |
| == Before beginning to migrate members == | * RoadMaps: Announcements of future plans and events. |
| Line 23: | Line 17: |
| === Per-User Tasks (also need to be included in adduser) === Assuming username "fred", |
== Quick hints == |
| Line 26: | Line 19: |
| * Add fred/cgi@HCOOP.NET principal * Generate keytab and put it somewhere where the user can't get it * Add fred/mailfilter@HCOOP.NET principal * Generate keytab and put it somewhere where the user can't get it * make a user volume * vos create user.fred * fs mkm /afs/hcoop.net/user/f/fr/fred/ * make a maildir * vos create mail.fred * create a delivery mountpoint * fs mkm /afs/hcoop.net/common/mail/f/fr/fred/ mail.fred * create the user's ~/Maildir mount point * fs mkm /afs/hcoop.net/user/f/fr/fred/Maildir mail.fred * doing this for at least one account is blocking Exim delivery testing * make a mount point for the user' oldfiles * 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 * should we provide snapshots for mail.fred? * where should we mount these volumes? |
* TipsAndTricks |
| Line 49: | Line 21: |
| === Getting Various Daemons to Run with AFS Tokens === | == Specific Machines == * PowerEdge2850 is about '''deleuze''' * RebootingDeleuze: Steps to take after rebooting deleuze. * RebootingMireSp: How to reboot mire using its SP interface. * HopperServiceProcessor |
| Line 51: | Line 27: |
| * 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) |
== Introductory material == |
| Line 62: | Line 29: |
| === 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. |
Refer to documentation of each of the listed components. The information in our Wiki pages covers only the most basic principles, and quickly focuses on HCoop-specific setup, assuming skillset with the technology. |
| Line 70: | Line 31: |
| == During migration == | * DaemonFileSecurity * DomTool * AuthenticationScheme * [[OpenLDAP]] * MitKerberos * AndrewFileSystem * EtcKeeper |
| Line 72: | Line 39: |
| * 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, .... * put 'vos backupsys -localauth' in deleuze:/etc/cron.d/cron.daily/ |
|
| Line 78: | Line 40: |
| = Global Notes = | |
| Line 80: | Line 41: |
| * 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. |
= Admins and Admin 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 84: | Line 47: |
| = Tasks done = | = Technical Records = * IpAddresses: Listing of IPs that we use. * [[Hardware]]: Information on HCoop hardware. * HcoopAddresses: Physical addresses relevant to us. * OnSiteVisits: Records of visits by HCoop volunteers to our colocation facilities |
| Line 86: | Line 53: |
| == Deleuze == | |
| Line 88: | 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. | = Sysadmin Stuff = |
| Line 90: | Line 56: |
| * 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 |
== 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 114: | Line 68: |
| = Mire = | == 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 116: | Line 80: |
| * 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 |
= Historical = |
| Line 119: | Line 82: |
| = Custom software = | Pages no longer considered relevant: |
| Line 121: | Line 84: |
| * DomtoolTwo * Vmail tools * Web portal |
* SoftwareArchitecturePlans: Plans for software installation. * SystemArchitecturePlans: Plans regarding our hardware. * InstallationLog contains ancient (~2005) records of installation of software and hardware * KrunkInfoz (Krunk is out of service) |
This contains a list of pages that are of interest to the admins.
Contents
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.
The linked pages are sorted based on relevance in day to day operations. That means the current admins will most often consult pages from the top of the list, while new admins or people wishing to get familiar with the setup will start from the end and move upwards.
Plans
RoadMaps: Announcements of future plans and events.
Quick hints
Specific Machines
PowerEdge2850 is about deleuze
RebootingDeleuze: Steps to take after rebooting deleuze.
RebootingMireSp: How to reboot mire using its SP interface.
Introductory material
Refer to documentation of each of the listed components. The information in our Wiki pages covers only the most basic principles, and quickly focuses on HCoop-specific setup, assuming skillset with the technology.
Admins and Admin 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.
Technical Records
IpAddresses: Listing of IPs that we use.
Hardware: Information on HCoop hardware.
HcoopAddresses: Physical addresses relevant to us.
OnSiteVisits: Records of visits by HCoop volunteers to our colocation facilities
Sysadmin Stuff
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.
UserManagement only talks about adduser/deluser right now.
InstalledSoftware lists non-debian installed software.
SystemAuthentication lists authentication
UsingResourceLimits If this is still accurate, we should move it to MemberManual area.
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.
Historical
Pages no longer considered relevant:
SoftwareArchitecturePlans: Plans for software installation.
SystemArchitecturePlans: Plans regarding our hardware.
InstallationLog contains ancient (~2005) records of installation of software and hardware
KrunkInfoz (Krunk is out of service)