welcome: please sign in

Diff for "AdminArea"

Differences between revisions 119 and 145 (spanning 26 versions)
⇤ ← Revision 119 as of 2009-08-22 19:55:18 →
Size: 1764
Editor: ClintonEbadi
Comment: Move Peer1 migration info to Historical section (should these even be here still?)
← Revision 145 as of 2010-03-10 08:55:50 → ⇥
Size: 4757
Editor: RichardDarst
Comment: update the intro to the page and stuff
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Admin Area =
Line 4: Line 5:


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.

Admins: it is recommended that you create a wiki account and subscribe to the page regex `.*` (all pages) 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 get emailed when it is done.

will let you know all the relevant subpages. From my experience, I would recommend longer pages, instead of dividing a topic into lots of subpages. When there are too many subpages, I've found that some will be updated, and some will fall out of date. (Of course, use your judgment here.)
Line 7: Line 16:
= General = == To be an admin ==
Sections you should read if you are interested in being an admin.
Line 9: Line 19:
 * TipsAndTricks

=== 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 10: Line 26:
 * AndrewFileSystem: Using our shared filesystem.
 * AuthenticationScheme: How authentication works on our systems.
 * DomTool: Administering and using domtool.
=== 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

== Planning and Records ==

 * RoadMaps: Announcements of future plans and events.
 * [[Migration2009]]
   * [[Migration2009/SoftwareSetup]]
   * Migration2010Notes: Notes about the new server setup and way to transfer over old data

=== Technical Records ===
 * IpAddresses: Listing of IPs that we use.
Line 15: Line 50:
 * IpAddresses: Listing of IPs that we use.
Line 17: Line 51:
 * RoadMaps: Detailed plans for future events.
Line 19: Line 52:
= HOWTO =
=== Views ===

 * Fritz.hcoop.net - [[http://fritz.hcoop.net/munin/|Munin reports]]


== Specific Machines ==
This documents machine-specific (hardware) things, or specific configuration necessary for ''that machine''.

 * [[Hardware]]
 * SetupNewMachines: How to install a machine that adheres to our policies
 * KvmAccess: How to use the remove KVM and avoid going on site.
 * deleuze
   * PowerEdge2850 is about '''deleuze'''
   * RebootingDeleuze: Steps to take after rebooting deleuze.
 * mire
   * RebootingMireSp: How to reboot mire using its SP interface.
 * hopper
   * HopperServiceProcessor
 * fritz
   * FritzInfo
 * outpost


== Services ==
This documents all software things that are not machine specific.

=== General Sysadmin ===
Line 22: Line 82:
 * CertificateAuthority: How to sign user SSL certificates and the like.
 * ChangingAdminPassword: How admins can change their UNIX passwords.
Line 25: Line 83:
 * 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.		  * ResourceLimits
 * InstalledSoftware lists non-debian installed software.
 * SystemAuthentication lists authentication
 * UsingResourceLimits If this is still accurate, we should move it to MemberManual area.
 * Member Management
   * UserManagement only talks about adduser/deluser right now.
   * 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.
Line 33: Line 93:
= Responsibilities = === Specific Services ===
 
 * DaemonAdmin: How to set up various daemons (NOTE: many of the services below are linked from here. We should migrate the contents of this page onto the outline below.).
 * AFS / Kerberos
   * SetupNewAfsServer: How to set up a new AFS server.
   * PrincipalsForNonHumans talks about kerberos for automated tasks.
 * Mail
   * MailMan contains no information...
   * SpamAssassinAdmin
 * DomTool
 * Web
 * DNS
   * ZoneTransfers is also mostly blank.
 * Databases
 * Backups
 * Version Control
 * wiki.hcoop.net
 * jabber
 * Other
   * CertificateAuthority: How to sign user SSL certificates and the like.
Line 35: Line 114:
 * TaskDistribution: What each sysadmin is responsible for.
 * VolunteerResponsePolicy: Guidelines for responding to requests and email.
Line 38: Line 115:
= Historical = == Historical ==

Pages no longer considered relevant:
Line 42: Line 121:
 * InstallationLog contains ancient (~2005) records of installation of software and hardware
 * KrunkInfoz (Krunk is out of service)

Admin Area

This contains a list of pages that are of interest to the admins.

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.

Admins: it is recommended that you create a wiki account and subscribe to the page regex .* (all pages) 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 get emailed when it is done.

will let you know all the relevant subpages. From my experience, I would recommend longer pages, instead of dividing a topic into lots of subpages. When there are too many subpages, I've found that some will be updated, and some will fall out of date. (Of course, use your judgment here.)

Contents

  1. Admin Area
    1. To be an admin
      1. Admins and Admin Responsibilities
      2. Introductory material
    2. Planning and Records
      1. Technical Records
      2. Views
    3. Specific Machines
    4. Services
      1. General Sysadmin
      2. Specific Services
    5. Historical

To be an admin

Sections you should read if you are interested in being an admin.

Admins and Admin Responsibilities

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.

Planning and Records

Technical Records

Views

Specific Machines

This documents machine-specific (hardware) things, or specific configuration necessary for that machine.

Services

This documents all software things that are not machine specific.

General Sysadmin

Specific Services

Historical

Pages no longer considered relevant:

AdminArea (last edited 2020-08-23 22:16:03 by ClintonEbadi)