|
Size: 1950
Comment:
|
Size: 4607
Comment: and try to clean up the reference section now
|
| 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. |
| Line 7: | Line 10: |
| = Planning = | |
| Line 9: | Line 11: |
| * OnSiteVisits: Records of visits by HCoop volunteers to our colocation facilities * RoadMaps: Detailed plans for future events. * '''Responsibilities''' * TaskDistribution: What each sysadmin is responsible for. * VolunteerResponsePolicy: Guidelines for responding to requests and email. * '''Records''' * IpAddresses: Listing of IPs that we use. * [[Hardware]]: Information on HCoop hardware. * HcoopAddresses: Physical addresses relevant to us. |
== To be an admin == Sections you should read if you are interested in being an admin. {{{#!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). }}} === 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... |
| Line 20: | Line 26: |
| = Sysadmin Stuff = | === Introductory material === |
| Line 22: | Line 28: |
| * AndrewFileSystem: Using our shared filesystem. * AuthenticationScheme: How authentication works on our systems. * DomTool: Administering and using domtool. |
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 26: | Line 30: |
| == General Sysadmin == | * DaemonDocumentation: manuals for core services with which you should be familiar * SystemArchitecture * DomTool * MitKerberos * AndrewFileSystem * EtcKeeper * [[Code]]: Details of HCoop-specific code kept in git.hcoop.net * [[OpenLDAP]] |
| Line 28: | Line 39: |
| == 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. * AuthenticationScheme |
|
| Line 29: | Line 65: |
| * CertificateAuthority: How to sign user SSL certificates and the like. * ChangingAdminPassword: How admins can change their UNIX passwords. * SetupNewMachines: How to put the basic hcoop AFS/Kerberos client config on a newly acquired machine. |
|
| Line 33: | Line 66: |
| * KvmAccess: How to use the remove KVM and avoid going on site. | * DebianArchive: Our local debian mirror for distributing custom packages * ConfigurationManagement: How we manage system wide configuration * SystemAuthentication lists authentication * UserManagement * 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. |
| Line 35: | Line 73: |
| == Specific Services/Tasks == * DaemonAdmin: How to set up various daemons (subpages for various services, should be linked from here.). * SetupNewAfsServer: How to set up a new AFS server. * MemberFreezing: How to freeze and unfreeze members who get behind on dues |
=== Specific Services === |
| Line 40: | Line 75: |
| == Specific Machines == * RebootingDeleuze: Steps to take after rebooting deleuze. * RebootingMireSp: How to reboot mire using its SP interface. |
Documentation of interest to people maintaining particular services. |
| Line 44: | Line 77: |
| = Historical = | <<Include(DaemonAdmin, ,to="^----$")>> * 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. * AFS / Kerberos * SetupNewAfsServer: How to set up a new AFS server. * PrincipalsForNonHumans talks about kerberos for automated tasks. * MailMan contains no information... * SpamAssassinAdmin * UsingResourceLimits * DaemonFileSecurity * ResourceLimits * TipsAndTricks |
| Line 47: | Line 103: |
| * 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]] * 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
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)