|
Size: 5603
Comment:
|
Size: 5151
Comment: link to new pages created from FritzVirtualization
|
| 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: |
| = Special topic pages about migration and new set-up = | 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 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 |
From my experience, I would recommend longer pages, instead of dividing a topic into lots of subpages. When there are too many subpages, I've found that some will be updated, and some will fall out of date. (Of course, use your judgment here.) |
| Line 15: | Line 9: |
| The following are outdated: | 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 17: | Line 11: |
| * ColocationNextSteps: Listing of things to do after getting the hardware. | <<TableOfContents>> |
| Line 19: | Line 13: |
| = To-do list = | |
| Line 21: | Line 14: |
| == Before beginning to migrate members == | == To be an admin == Sections you should read if you are interested in being an admin. |
| Line 23: | Line 17: |
| * Mailman * DNS server daemon * Apache Dynamic Content. Our ''viable'' options are: 1. Have domtool support Apache13; use mod_waklog * less than 40 lines of code need to be changed in domtool's Apache20 module to do this 1. Support only CGI (no PHP, suexec) and use kstart to wrap each CGI process 1. Write our own versions of suexec and the suexecified-php (whatever it's called) * reliability/security/maintainability concerns |
* TipsAndTricks |
| Line 32: | Line 19: |
| === Misc === * Make ca@hcoop.net e-mail address working. It's the address that will be used in the certificate files. * Make sure somebody is reading mail sent to abuse@hcoop.net so we don't wind up on lame DNSBLs * 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. |
=== 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. * AddingNewAdmins: Documented procedures for adding new admin accounts |
| Line 40: | Line 26: |
| == During migration == | === Introductory material === |
| Line 42: | Line 28: |
| * 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, .... |
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.See DaemonDocumentation for links to the official documentation for the softare powering our core infrastructure. |
| Line 47: | Line 30: |
| = Global Notes = | * SystemArchitecture * DaemonFileSecurity * DomTool * AuthenticationScheme * [[OpenLDAP]] * MitKerberos * AndrewFileSystem * EtcKeeper * [[Code]] - Details of HCoop-specific code kept in git.hcoop.net |
| Line 49: | Line 40: |
| * 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. |
== Planning and Records == |
| Line 53: | Line 42: |
| = Tasks done = | * ToDo: Both short term and longer term meta-planning. |
| Line 55: | Line 44: |
| == Deleuze == | |
| Line 57: | Line 45: |
| 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. | === 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 59: | Line 51: |
| * 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). |
|
| Line 85: | Line 52: |
| = Mire = | === Views === |
| Line 87: | Line 54: |
| * 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 |
* Fritz.hcoop.net - [[http://fritz.hcoop.net/munin/|Munin reports]] |
| Line 90: | Line 56: |
| = Custom software = | |
| Line 92: | Line 57: |
| * DomtoolTwo * Vmail tools * Web portal |
== Specific Machines == This documents machine-specific (hardware) things, or specific configuration necessary for ''that machine''. * [[Hardware]] * InstallationProcedure: how to install a machine that adheres to our policies * 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. * deleuze * PowerEdge2850 is about '''deleuze''' * RebootingDeleuze: Steps to take after rebooting deleuze. * mire * RebootingMireSp: How to reboot mire using its SP interface. * hopper * HopperServiceProcessor * fritz * FritzInfo * outpost * OutpostInfo == Services == This documents all software things that are not machine specific. === General Sysadmin === * BackupInfo: Information on how to recover deleted files from our off-site backups. * DebianPackaging: How to make custom HCoop Debian packages. * DebianArchive: Our local debian mirror for distributing custom packages * ResourceLimits * InstalledSoftware lists non-debian installed software. * SystemAuthentication lists authentication * UsingResourceLimits If this is still accurate, we should move it to MemberManual area. * Member Management * UserManagement only talks about adduser/deluser right now. * 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. === Specific Services === <<Include(DaemonAdmin, ,to="^----$")>> * AFS / Kerberos * SetupNewAfsServer: How to set up a new AFS server. * PrincipalsForNonHumans talks about kerberos for automated tasks. * MailMan contains no information... * SpamAssassinAdmin * DomTool * Web * CertificateAuthority: How to sign user SSL certificates and the like. * DNS * ZoneTransfers is also mostly blank. * Databases * Backups * VersionControlAdmin * wiki.hcoop.net * JabberAdmin * [[BugZilla]] == 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) * [[Migration2009]] (never happened, staying at Peer1 was a better choice after all) * [[Migration2009/SoftwareSetup]] ---- 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.
From my experience, I would recommend longer pages, instead of dividing a topic into lots of subpages. When there are too many subpages, I've found that some will be updated, and some will fall out of date. (Of course, use your judgment here.)
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).
Contents
To be an admin
Sections you should read if you are interested in being an admin.
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.
AddingNewAdmins: Documented procedures for adding new admin accounts
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.See DaemonDocumentation for links to the official documentation for the softare powering our core infrastructure.
Code - Details of HCoop-specific code kept in git.hcoop.net
Planning and Records
ToDo: Both short term and longer term meta-planning.
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
Views
Fritz.hcoop.net - Munin reports
Specific Machines
This documents machine-specific (hardware) things, or specific configuration necessary for that machine.
InstallationProcedure: how to install a machine that adheres to our policies
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.
- deleuze
PowerEdge2850 is about deleuze
RebootingDeleuze: Steps to take after rebooting deleuze.
- mire
RebootingMireSp: How to reboot mire using its SP interface.
- hopper
- fritz
- outpost
Services
This documents all software things that are not machine specific.
General Sysadmin
BackupInfo: Information on how to recover deleted files from our off-site backups.
DebianPackaging: How to make custom HCoop Debian packages.
DebianArchive: Our local debian mirror for distributing custom packages
InstalledSoftware lists non-debian installed software.
SystemAuthentication lists authentication
UsingResourceLimits If this is still accurate, we should move it to MemberManual area.
- Member Management
UserManagement only talks about adduser/deluser right now.
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.
Specific Services
We've recorded some special instructions, hints, etc., for daemons with non-standard configuration.
- AFS / Kerberos
SetupNewAfsServer: How to set up a new AFS server.
PrincipalsForNonHumans talks about kerberos for automated tasks.
- Mail
MailMan contains no information...
- Web
CertificateAuthority: How to sign user SSL certificates and the like.
- DNS
ZoneTransfers is also mostly blank.
- Databases
- Backups
- wiki.hcoop.net
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)
Migration2009 (never happened, staying at Peer1 was a better choice after all)