|
Size: 2778
Comment: fix link to ListOfVolunteers
|
Size: 3127
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| = Planning = | = Sysadmin work = Links to detailed policies, procedures and information specific to HCoop. The resources here should allow HCoop admin team to all have a clue about every part of the system, and to allow easier training of future team members. = Keeping track = == On-site visits == |
| Line 9: | Line 15: |
== 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. == Technical Records == * IpAddresses: Listing of IPs that we use. * [[Hardware]]: Information on HCoop hardware. * HcoopAddresses: Physical addresses relevant to us. == Misc == |
|
| Line 10: | Line 29: |
| * '''Responsibilities''' * TaskDistribution: What each sysadmin is responsible for. * VolunteerResponsePolicy: Guidelines for responding to requests and email. * AdminArea/ListOfVolunteers who can help us do stuff... * '''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. |
|
| Line 26: | Line 37: |
| * EtcKeeper: Use this to keep track of config changes. |
This contains a list of pages that are of interest to the admins.
Contents
Sysadmin work
Links to detailed policies, procedures and information specific to HCoop. The resources here should allow HCoop admin team to all have a clue about every part of the system, and to allow easier training of future team members.
Keeping track
On-site visits
OnSiteVisits: Records of visits by HCoop volunteers to our colocation facilities
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.
Technical Records
IpAddresses: Listing of IPs that we use.
Hardware: Information on HCoop hardware.
HcoopAddresses: Physical addresses relevant to us.
Misc
RoadMaps: Detailed plans for future events.
Sysadmin Stuff
AndrewFileSystem: Using our shared filesystem.
AuthenticationScheme: How authentication works on our systems.
DomTool: Administering and using domtool.
EtcKeeper: Use this to keep track of config changes.
General Sysadmin
BackupInfo: Information on how to recover deleted files from our off-site backups.
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.
UserManagement only talks about adduser/deluser right now.
InstalledSoftware lists non-debian installed software.
SystemAuthentication lists authentication
UsingResourceLimits If this is still accurate, we should move it to MemberManual area.
Specific Services/Tasks
DaemonAdmin: How to set up various daemons (subpages for various services, should be linked from here.).
MailMan contains no information...
SetupNewAfsServer: How to set up a new AFS server.
MemberFreezing: How to freeze and unfreeze members who get behind on dues
AdminUserSetup lists steps to create (blank), delete, and change passwords of admin users.
ChangingAdminPassword: How admins can change their UNIX passwords.
CertificateAuthority: How to sign user SSL certificates and the like.
ZoneTransfers is also mostly blank.
PrincipalsForNonHumans talks about kerberos for automated tasks.
Specific Machines
PowerEdge2850 is about deleuze
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.
InstallationLog contains ancient (~2005) records of installation of software and hardware