|
Size: 1155
Comment: Reorg, add VolunteerResponsePolicy and MailmanInstallation
|
Size: 1764
Comment: Move Peer1 migration info to Historical section (should these even be here still?)
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| [[TableOfContents]] | <<TableOfContents>> |
| Line 9: | Line 9: |
| * AndrewFileSystem: Using our new shared filesystem. | * AdminGroup: Listing of people who can delete pages and despam pages on the wiki. * AndrewFileSystem: Using our shared filesystem. * AuthenticationScheme: How authentication works on our systems. * DomTool: Administering and using domtool. * [[Hardware]]: Information on HCoop hardware. * HcoopAddresses: Physical addresses relevant to us. * IpAddresses: Listing of IPs that we use. * OnSiteVisits: Records of visits by HCoop volunteers to our colocation facilities * RoadMaps: Detailed plans for future events. = HOWTO = |
| Line 11: | Line 22: |
| * CertificateAuthority: How to sign user SSL certificates and the like. | |
| Line 12: | Line 24: |
| * DomTool: Administering and using the new domtool. * IpAddresses: Listing of IPs that we use. * NewSystemHardware: Information on the new hardware. * SoftwareArchitecturePlans: Plans for software installation. * SystemArchitecturePlans: Plans regarding our hardware. * OnSiteStuff: Checklist for the next on-site visit to the new machines. * OneTimeCosts2007: Costs associated with the new servers through April 2007. * HcoopAddresses: Physical addresses relevant to us. |
* DebianPackaging: How to make custom HCoop Debian packages. * DaemonAdmin: How to set up various daemons. * KvmAccess: How to use the remove KVM and avoid going on site. * MemberFreezing: How to freeze and unfreeze members who get behind on dues * RebootingDeleuze: Steps to take after rebooting deleuze. * RebootingMireSp: How to reboot mire using its SP interface. * SetupNewAfsServer: How to set up a new AFS server. * SetupNewMachines: How to put the basic hcoop AFS/Kerberos client config on a newly acquired machine. |
| Line 26: | Line 38: |
| = Programs = | = Historical = |
| Line 28: | Line 40: |
| * DaemonAdmin: Daemon-specific pages aimed at admins. * MailmanInstallation: Additional things we must do to keep Mailman happy. |
* SoftwareArchitecturePlans: Plans for software installation. * SystemArchitecturePlans: Plans regarding our hardware. |
This contains a list of pages that are of interest to the admins.
Contents
General
AdminGroup: Listing of people who can delete pages and despam pages on the wiki.
AndrewFileSystem: Using our shared filesystem.
AuthenticationScheme: How authentication works on our systems.
DomTool: Administering and using domtool.
Hardware: Information on HCoop hardware.
HcoopAddresses: Physical addresses relevant to us.
IpAddresses: Listing of IPs that we use.
OnSiteVisits: Records of visits by HCoop volunteers to our colocation facilities
RoadMaps: Detailed plans for future events.
HOWTO
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.
DebianPackaging: How to make custom HCoop Debian packages.
DaemonAdmin: How to set up various daemons.
KvmAccess: How to use the remove KVM and avoid going on site.
MemberFreezing: How to freeze and unfreeze members who get behind on dues
RebootingDeleuze: Steps to take after rebooting deleuze.
RebootingMireSp: How to reboot mire using its SP interface.
SetupNewAfsServer: How to set up a new AFS server.
SetupNewMachines: How to put the basic hcoop AFS/Kerberos client config on a newly acquired machine.
Responsibilities
TaskDistribution: What each sysadmin is responsible for.
VolunteerResponsePolicy: Guidelines for responding to requests and email.
Historical
SoftwareArchitecturePlans: Plans for software installation.
SystemArchitecturePlans: Plans regarding our hardware.