1950
Comment:
|
3552
|
Deletions are marked like this. | Additions are marked like this. |
Line 7: | Line 7: |
= Planning = | = Sysadmin work = |
Line 9: | Line 9: |
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. The linked pages are sorted based on relevance in day to day operations. That means the current admins will most often consult pages from the top of the list, while new admins or people wishing to get familiar with the setup will start from the end and move upwards. == Plans == * RoadMaps: Announcements of future plans and events. == Quick hints == * TipsAndTricks == 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. * DaemonFileSecurity * DomTool * AuthenticationScheme * OpenLDAP * MitKerberos * AndrewFileSystem * EtcKeeper = 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. = Technical Records = * IpAddresses: Listing of IPs that we use. * [[Hardware]]: Information on HCoop hardware. * HcoopAddresses: Physical addresses relevant to us. |
|
Line 10: | Line 46: |
* 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. |
|
Line 22: | Line 50: |
* AndrewFileSystem: Using our shared filesystem. * AuthenticationScheme: How authentication works on our systems. * DomTool: Administering and using domtool. |
|
Line 27: | Line 51: |
Line 29: | Line 52: |
* CertificateAuthority: How to sign user SSL certificates and the like. * ChangingAdminPassword: How admins can change their UNIX passwords. |
|
Line 34: | Line 55: |
* KvmInfo * UserManagement only talks about adduser/deluser right now. * ResourceLimits * InstalledSoftware lists non-debian installed software. * SystemAuthentication lists authentication * UsingResourceLimits If this is still accurate, we should move it to MemberManual area. |
|
Line 37: | Line 64: |
* MailMan contains no information... | |
Line 39: | Line 67: |
* 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. * SpamAssassinAdmin |
|
Line 41: | Line 75: |
* PowerEdge2850 is about '''deleuze''' | |
Line 43: | Line 78: |
* HopperServiceProcessor * KrunkInfoz |
|
Line 47: | Line 84: |
* InstallationLog contains ancient (~2005) records of installation of software and hardware |
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 members to share information about every part of the complete system, and to allow easier training of future team members.
The linked pages are sorted based on relevance in day to day operations. That means the current admins will most often consult pages from the top of the list, while new admins or people wishing to get familiar with the setup will start from the end and move upwards.
Plans
RoadMaps: Announcements of future plans and events.
Quick hints
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.
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.
Technical Records
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
Sysadmin Stuff
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