3582
Comment:
|
4954
categorize
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
This contains a list of pages that are of interest to the admins. | = 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 [[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 7: | Line 13: |
= Sysadmin work = | |
Line 9: | Line 14: |
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 11: | Line 15: |
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 == |
== To be an admin == Sections you should read if you are interested in being an admin. |
Line 21: | Line 20: |
== Specific Machines == * PowerEdge2850 is about '''deleuze''' * RebootingDeleuze: Steps to take after rebooting deleuze. * RebootingMireSp: How to reboot mire using its SP interface. * HopperServiceProcessor |
=== 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 27: | Line 27: |
== Introductory material == | === Introductory material === |
Line 29: | Line 29: |
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. | 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 38: | Line 38: |
* [[Code]] - Details of HCoop-specific code kept in git.hcoop.net == Planning and Records == * ToDo: Both short term and longer term meta-planning. |
|
Line 40: | Line 45: |
= 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 = |
=== Technical Records === |
Line 54: | Line 52: |
= Sysadmin Stuff = | === Views === |
Line 56: | Line 54: |
== General Sysadmin == | * Fritz.hcoop.net - [[http://fritz.hcoop.net/munin/|Munin reports]] == 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 === |
Line 58: | Line 82: |
* SetupNewMachines: How to put the basic hcoop AFS/Kerberos client config on a newly acquired machine. | |
Line 60: | Line 83: |
* KvmAccess: How to use the remove KVM and avoid going on site. * KvmInfo * UserManagement only talks about adduser/deluser right now. |
|
Line 67: | Line 87: |
* 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. |
|
Line 68: | Line 93: |
== 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 |
=== Specific Services === |
Line 80: | Line 95: |
= Historical = | <<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: |
Line 85: | Line 124: |
* [[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.
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
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)