|
Size: 4934
Comment: remove redundant h1
|
Size: 4607
Comment: and try to clean up the reference section now
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
= Admin Area = |
|
| Line 5: | Line 7: |
| 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 13: | Line 12: |
| Line 15: | Line 15: |
| * TipsAndTricks | {{{#!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 18: | Line 20: |
| Line 22: | Line 25: |
| * AddingNewAdmins: Documented procedures for adding new admin accounts | |
| Line 26: | Line 28: |
| 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. | 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 28: | Line 30: |
| * DaemonFileSecurity | * DaemonDocumentation: manuals for core services with which you should be familiar * SystemArchitecture |
| Line 30: | Line 33: |
| * AuthenticationScheme * [[OpenLDAP]] |
|
| Line 35: | Line 36: |
| * [[Code]] - Details of HCoop-specific code kept in git.hcoop.net | * [[Code]]: Details of HCoop-specific code kept in git.hcoop.net * [[OpenLDAP]] |
| Line 40: | Line 42: |
=== Technical Records === |
|
| Line 48: | Line 47: |
| == Hardware / On-Site Infrastructure == | |
| Line 49: | Line 49: |
| === Views === | * [[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 |
| Line 51: | Line 55: |
| * Fritz.hcoop.net - [[http://fritz.hcoop.net/munin/|Munin reports]] | == Software == |
| Line 53: | Line 57: |
== 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. |
This documents all software things that are not specific to the on-site infrastructure. |
| Line 78: | Line 61: |
| Documentation useful for the daily care and feeding of our systems. * AuthenticationScheme |
|
| Line 80: | Line 66: |
| * ResourceLimits * InstalledSoftware lists non-debian installed software. |
* DebianArchive: Our local debian mirror for distributing custom packages * ConfigurationManagement: How we manage system wide configuration |
| Line 83: | Line 69: |
| * UsingResourceLimits If this is still accurate, we should move it to MemberManual area. * Member Management * UserManagement only talks about adduser/deluser right now. |
* UserManagement |
| Line 87: | Line 71: |
| * AdminUserSetup lists steps to create (blank), delete, and change passwords of admin users. * ChangingAdminPassword: How admins can change their UNIX passwords. |
* AdminUserSetup, AddingNewAdmins, ChangingAdminPassword: lists steps to create (blank), delete, and change passwords of admin users. |
| Line 92: | Line 75: |
| Documentation of interest to people maintaining particular services. |
|
| Line 93: | Line 78: |
* 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. |
|
| Line 99: | Line 97: |
| * 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: |
* UsingResourceLimits * DaemonFileSecurity * ResourceLimits * TipsAndTricks |
| Line 123: | Line 107: |
| * InstalledSoftware |
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.
DebianArchive: Our local debian mirror for distributing custom packages
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)