|
Size: 4825
Comment: Add mire todo section
|
Size: 4971
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]] | = 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: |
| = Global TODO = | |
| Line 21: | Line 14: |
| * Make ca@hcoop.net e-mail address working. It's the address that will be used in the certificate files. * Migrate ejabberd mnesia db just before the dns switchover. |
|
| Line 24: | Line 15: |
| = Global Notes = | == To be an admin == Sections you should read if you are interested in being an admin. |
| Line 26: | Line 18: |
| * 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. |
* TipsAndTricks |
| Line 30: | Line 20: |
| = Deleuze = | === 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 32: | Line 27: |
| 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. | === Introductory material === |
| Line 34: | Line 29: |
| == Tasks done == | 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 36: | Line 31: |
| * 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 |
* DaemonFileSecurity * DomTool * AuthenticationScheme * [[OpenLDAP]] * MitKerberos * AndrewFileSystem * EtcKeeper * [[Code]] - Details of HCoop-specific code kept in git.hcoop.net |
| Line 56: | Line 40: |
| == TODO == | == Planning and Records == |
| Line 58: | Line 42: |
| In order of implementation (soonest first): | * ToDo: Both short term and longer term meta-planning. * [[Migration2009]] * [[Migration2009/SoftwareSetup]] * Migration2010Notes: Notes about the new server setup and way to transfer over old data |
| Line 60: | Line 47: |
| * 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. * 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. * Configure exim4. --MichaelOlson * Configure courier IMAP daemons, reviewing fyodor's config. --MichaelOlson * Configure squirrelmail to use imapproxyd, which should give speed improvements once we migrate to deleuze. --MichaelOlson |
=== 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 67: | Line 53: |
| = Custom software = | |
| Line 69: | Line 54: |
| * 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 |
=== Views === |
| Line 74: | Line 56: |
| These are my responsibility. Right now, I'm waiting for the more traditional stuff to be set up and stable before beginning. --AdamChlipala | * Fritz.hcoop.net - [[http://fritz.hcoop.net/munin/|Munin reports]] |
| Line 76: | Line 58: |
| = 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 |
|
| Line 81: | Line 59: |
| == TODO == * Configure Exim to use deleuze as a smarthost. --MichaelOlson |
== Specific Machines == This documents machine-specific (hardware) things, or specific configuration necessary for ''that machine''. * [[Hardware]] * SetupNewMachines: How to install 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. * 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 === * DaemonAdmin: How to set up various daemons (NOTE: many of the services below are linked from here. We should migrate the contents of this page onto the outline below.). * 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 * DNS * ZoneTransfers is also mostly blank. * Databases * Backups * VersionControlAdmin * wiki.hcoop.net * JabberAdmin * [[BugZilla]] * Other * CertificateAuthority: How to sign user SSL certificates and the like. == 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) |
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.
Code - Details of HCoop-specific code kept in git.hcoop.net
Planning and Records
ToDo: Both short term and longer term meta-planning.
Migration2010Notes: Notes about the new server setup and way to transfer over old data
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.
SetupNewMachines: How to install 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.
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
DaemonAdmin: How to set up various daemons (NOTE: many of the services below are linked from here. We should migrate the contents of this page onto the outline below.).
- AFS / Kerberos
SetupNewAfsServer: How to set up a new AFS server.
PrincipalsForNonHumans talks about kerberos for automated tasks.
- Mail
MailMan contains no information...
- Web
- DNS
ZoneTransfers is also mostly blank.
- Databases
- Backups
- wiki.hcoop.net
- Other
CertificateAuthority: How to sign user SSL certificates and the like.
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)