|
Size: 6462
Comment: Add OnSiteStuff
|
Size: 4565
Comment: debian archive info has been on debian packaging page for a while
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Introduction = | #pragma section-numbers off |
| Line 3: | Line 3: |
| [[TableOfContents]] | = Admin Area = |
| Line 5: | Line 5: |
| = Final preparations = See page NewServersSetup/FinalPreparations. = 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 * 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 The following are outdated: * ColocationNextSteps: Listing of things to do after getting the hardware. = To-do list = == During migration == * Unclaimed * Watchdog process to kill resource hogs * 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. * 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, .... * 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. * ntk * Mailman * (Status) The exim side of things has been mostly set up. I think I migrated the non-exim stuff as well, but will need to double-check. --MichaelOlson * Migrate lists. * Reboot mire while on-site to watch for slow boot issues that should be resolved with recent changes * mwolson * Run simple tests on cron to see if it works. |
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 47: | Line 8: |
| = Global Notes = | <<TableOfContents>> |
| Line 49: | Line 10: |
| * 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 -f -N -L 389:localhost:389 USERNAME@deleuze.hcoop.net''', and then connect to ''localhost:389'' in ''gq''. * For the description of the actual authentication scheme, see AuthenticationScheme. |
|
| Line 53: | Line 11: |
| = Tasks done = | == To be an admin == |
| Line 55: | Line 13: |
| == Deleuze == | Sections you should read if you are interested in being an admin. |
| Line 57: | Line 15: |
| 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. | {{{#!wiki tip Admins: it is recommended that you watch the changes [[http://wiki.hcoop.net/RecentChanges?action=rss_rc&diffs=1&ddiffs=1|RSS feed]] to keep informed of what everyone is up to. Then, please document all of your work on here somewhere - that way we will not only have a record, but everyone gets notified about what is going on. Alternatively, you can create a wiki account and subscribe to the page regex `.*` (all pages). }}} |
| Line 59: | Line 19: |
| * 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 * Exim filters * (a method has been set up by MichaelOlson, but it needs testing). * DNS server * Works on deleuze, although I will test once more domains have been migrated for reasonable domain defaults --JustinLeitgeb * nscd process for name caching * Currently this processes is set to do hostname caching on deleuze, so bind will not be set up as a caching name server --JustinLeitgeb * Get exim working on mire --MichaelOlson * Upgrade deleuze to debian etch --MichaelOlson * Install denyhosts on both deleuze and mire, needs debian etch --MichaelOlson * Switch ssh on deleuze to listen to port 22, needs denyhosts --MichaelOlson * Perform testing on procmail and exim filter on deleuze. --MichaelOlson * Make ca@hcoop.net e-mail address working. It's the address that will be used in the certificate files. --MichaelOlson * Make sure somebody is reading mail sent to abuse@hcoop.net so we don't wind up on lame DNSBLs. * Review apache configuration on mire. --MichaelOlson * Make /afs/hcoop.net/common/etc/scripts/apache-sync-logs work. --Megacz |
=== Admins and Admin Responsibilities === |
| Line 98: | Line 21: |
| = Mire = | * 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 100: | Line 26: |
| * 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 |
=== Introductory material === |
| Line 103: | Line 28: |
| = Custom software = | 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 105: | Line 30: |
| * DomtoolTwo * Vmail tools * Web portal |
* DaemonDocumentation: manuals for core services with which you should be familiar * SystemArchitecture * DomTool * MitKerberos * AndrewFileSystem * EtcKeeper * [[Code]]: Details of HCoop-specific code kept in git.hcoop.net * [[OpenLDAP]] == Planning and Records == * ToDo: Both short term and longer term meta-planning. * 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 == Hardware / On-Site Infrastructure == * [[Hardware]]: information on the colocation facility and the physical/virtual machines we are using. Tips on using service processors etc. are here. * InstallationProcedure: how to install a machine that adheres to our policies * KernelVirtualMachine: how we are using libvirt * SetupNewMachines: The ''old'' guide to installing a machine that adheres to our policies * KvmAccess: How to use the remove KVM and avoid going on site == Software == This documents all software things that are not specific to the on-site infrastructure. === General Sysadmin === Documentation useful for the daily care and feeding of our systems. * AuthenticationScheme * BackupInfo: Information on how to recover deleted files from our off-site backups. * DebianPackaging: How to make custom HCoop Debian packages, and details on our debian archive * ConfigurationManagement: How we manage system wide configuration * SystemAuthentication lists authentication * UserManagement * MemberFreezing: How to freeze and unfreeze members who get behind on dues * AdminUserSetup, AddingNewAdmins, ChangingAdminPassword: lists steps to create (blank), delete, and change passwords of admin users. === Specific Services === Documentation of interest to people maintaining particular services. <<Include(DaemonAdmin, ,to="^----$")>> * DomTool * Web * CertificateAuthority: How to sign user SSL certificates and the like. * WebServicesAdmin: How to administer hcoop provided web services * VersionControlAdmin * JabberAdmin * [[BugZilla]] == Historical == Pages no longer considered relevant, but may be of historical interest or otherwise useful as source material for updated documentation. * AFS / Kerberos * SetupNewAfsServer: How to set up a new AFS server. * PrincipalsForNonHumans talks about kerberos for automated tasks. * MailMan contains no information... * SpamAssassinAdmin * UsingResourceLimits * DaemonFileSecurity * ResourceLimits * TipsAndTricks * 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) * [[Migration2009]] (never happened, staying at Peer1 was a better choice after all) * [[Migration2009/SoftwareSetup]] * InstalledSoftware ---- CategorySystemAdministration |
Admin Area
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.
Contents
To be an admin
Sections you should read if you are interested in being an admin.
Admins: it is recommended that you watch the changes RSS feed to keep informed of what everyone is up to. Then, please document all of your work on here somewhere - that way we will not only have a record, but everyone gets notified about what is going on. Alternatively, you can create a wiki account and subscribe to the page regex .* (all pages).
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.
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.
DaemonDocumentation: manuals for core services with which you should be familiar
Code: Details of HCoop-specific code kept in git.hcoop.net
Planning and Records
ToDo: Both short term and longer term meta-planning.
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
Hardware / On-Site Infrastructure
Hardware: information on the colocation facility and the physical/virtual machines we are using. Tips on using service processors etc. are here.
InstallationProcedure: how to install a machine that adheres to our policies
KernelVirtualMachine: how we are using libvirt
SetupNewMachines: The old guide to installing a machine that adheres to our policies
KvmAccess: How to use the remove KVM and avoid going on site
Software
This documents all software things that are not specific to the on-site infrastructure.
General Sysadmin
Documentation useful for the daily care and feeding of our systems.
BackupInfo: Information on how to recover deleted files from our off-site backups.
DebianPackaging: How to make custom HCoop Debian packages, and details on our debian archive
ConfigurationManagement: How we manage system wide configuration
SystemAuthentication lists authentication
MemberFreezing: How to freeze and unfreeze members who get behind on dues
AdminUserSetup, AddingNewAdmins, ChangingAdminPassword: lists steps to create (blank), delete, and change passwords of admin users.
Specific Services
Documentation of interest to people maintaining particular services.
We've recorded some special instructions, hints, etc., for daemons with non-standard configuration.
- Web
CertificateAuthority: How to sign user SSL certificates and the like.
WebServicesAdmin: How to administer hcoop provided web services
Historical
Pages no longer considered relevant, but may be of historical interest or otherwise useful as source material for updated documentation.
- AFS / Kerberos
SetupNewAfsServer: How to set up a new AFS server.
PrincipalsForNonHumans talks about kerberos for automated tasks.
- Mail
MailMan contains no information...
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)
Migration2009 (never happened, staying at Peer1 was a better choice after all)