|
Size: 1389
Comment: Repurpose AdminGroup
|
Size: 1950
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| [[TableOfContents]] | <<TableOfContents>> |
| Line 7: | Line 7: |
| = General = | = Planning = |
| Line 9: | Line 9: |
| * 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. |
|
| Line 10: | Line 19: |
| * AndrewFileSystem: Using our new shared filesystem. | = Sysadmin Stuff = * AndrewFileSystem: Using our shared filesystem. |
| Line 12: | Line 24: |
| * DomTool: Administering and using the new domtool. * HcoopAddresses: Physical addresses relevant to us. * IpAddresses: Listing of IPs that we use. * NewSystemHardware: Information on the new hardware. * OnSiteStuff: Checklist for the next on-site visit to the new machines. * RoadMaps: Detailed plans for future events. * SoftwareArchitecturePlans: Plans for software installation. * SystemArchitecturePlans: Plans regarding our hardware. |
* DomTool: Administering and using domtool. |
| Line 21: | Line 26: |
| = HOWTO = | == General Sysadmin == |
| Line 26: | Line 31: |
| * SetupNewMachines: How to put the basic hcoop AFS/Kerberos client config on a newly acquired machine. | |
| Line 27: | Line 33: |
| * DaemonAdmin: How to set up various daemons. * KvmAccess: How to use the remove KVM and avoid going on site |
* KvmAccess: How to use the remove KVM and avoid going on site. |
| Line 30: | Line 35: |
| = Responsibilities = | == 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 |
| Line 32: | Line 40: |
| * TaskDistribution: What each sysadmin is responsible for. * VolunteerResponsePolicy: Guidelines for responding to requests and email. |
== Specific Machines == * RebootingDeleuze: Steps to take after rebooting deleuze. * RebootingMireSp: How to reboot mire using its SP interface. = Historical = * SoftwareArchitecturePlans: Plans for software installation. * SystemArchitecturePlans: Plans regarding our hardware. |
This contains a list of pages that are of interest to the admins.
Contents
Planning
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.
AdminGroup: Listing of people who can delete pages and despam pages on the wiki.
Sysadmin Stuff
AndrewFileSystem: Using our shared filesystem.
AuthenticationScheme: How authentication works on our systems.
DomTool: Administering and using domtool.
General Sysadmin
BackupInfo: Information on how to recover deleted files from our off-site backups.
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.
DebianPackaging: How to make custom HCoop Debian packages.
KvmAccess: How to use the remove KVM and avoid going on site.
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 Machines
RebootingDeleuze: Steps to take after rebooting deleuze.
RebootingMireSp: How to reboot mire using its SP interface.
Historical
SoftwareArchitecturePlans: Plans for software installation.
SystemArchitecturePlans: Plans regarding our hardware.