|
Size: 4897
Comment: include DaemonAdmin page inline, since it has useful content and is basically a secret
|
Size: 4519
Comment: step three: remove redundant (and outdated) information better represented on Hardware
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | 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 14: | Line 11: |
| == To be an admin == | |
| Line 15: | Line 13: |
| == To be an admin == | |
| Line 18: | 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 21: | Line 20: |
| Line 25: | Line 25: |
| * AddingNewAdmins: Documented procedures for adding new admin accounts | |
| Line 31: | Line 30: |
| * DaemonFileSecurity | * DaemonDocumentation: manuals for core services with which you should be familiar * SystemArchitecture |
| Line 33: | Line 33: |
| * AuthenticationScheme * [[OpenLDAP]] |
|
| Line 38: | Line 36: |
| * [[Code]] - Details of HCoop-specific code kept in git.hcoop.net * DaemonDocumentation - Quick links to canonical documentation for our core services |
* [[Code]]: Details of HCoop-specific code kept in git.hcoop.net * [[OpenLDAP]] |
| Line 44: | Line 42: |
=== Technical Records === |
|
| Line 52: | Line 47: |
| == Hardware / On-Site Infrastructure == | |
| Line 53: | 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 55: | Line 55: |
| * Fritz.hcoop.net - [[http://fritz.hcoop.net/munin/|Munin reports]] | == Software == |
| Line 57: | 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 82: | Line 61: |
| * AuthenticationScheme | |
| Line 84: | Line 64: |
| * ResourceLimits * InstalledSoftware lists non-debian installed software. |
* DebianArchive: Our local debian mirror for distributing custom packages * ConfigurationManagement: How we manage system wide configuration |
| Line 87: | Line 67: |
| * UsingResourceLimits If this is still accurate, we should move it to MemberManual area. | |
| Line 89: | Line 68: |
| * UserManagement only talks about adduser/deluser right now. | * UserManagement |
| Line 91: | Line 70: |
| * 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 105: | Line 83: |
| * CertificateAuthority: How to sign user SSL certificates and the like. * WebServicesAdmin: How to administer hcoop provided web services |
|
| Line 113: | Line 93: |
| * Other * CertificateAuthority: How to sign user SSL certificates and the like. |
|
| Line 119: | Line 96: |
| Pages no longer considered relevant: | Pages no longer considered relevant, but may be of historical interest: |
| Line 121: | Line 98: |
| * UsingResourceLimits * DaemonFileSecurity * ResourceLimits * TipsAndTricks |
|
| Line 127: | Line 108: |
| * 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
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
- Member Management
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
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.
WebServicesAdmin: How to administer hcoop provided web services
- DNS
ZoneTransfers is also mostly blank.
- Databases
- Backups
- wiki.hcoop.net
Historical
Pages no longer considered relevant, but may be of historical interest:
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)