welcome: please sign in

Diff for "AdminArea"

Differences between revisions 93 and 162 (spanning 69 versions)
⇤ ← Revision 93 as of 2007-10-24 22:56:36 →
Size: 954
Editor: MichaelOlson
Comment: Make this a portal for admins
← Revision 162 as of 2012-12-10 00:37:45 → ⇥
Size: 4897
Editor: ClintonEbadi
Comment: include DaemonAdmin page inline, since it has useful content and is basically a secret
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from NewServersSetup
= Introduction =		 #pragma section-numbers off
Line 4: Line 3:
[[TableOfContents]] = Admin Area =
Line 6: Line 5:
= Special topic pages about the new set-up = 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.
Line 8: Line 7:
 * AndrewFileSystem: Using our new shared filesystem 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.)

Admins: it is recommended that you watch the changes [[http://wiki.hcoop.net/RecentChanges?action=rss_rc&diffs=1&ddiffs=1|RSS feed]] 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 everyone gets notified about what is going on. Alternatively, you can create a wiki account and subscribe to the page regex `.*` (all pages).

<<TableOfContents>>



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

 * 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...
 * AdminGroup: Listing of people who can delete pages and despam pages on the wiki.
 * AddingNewAdmins: Documented procedures for adding new admin accounts

=== 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
 * [[Code]] - Details of HCoop-specific code kept in git.hcoop.net
 * DaemonDocumentation - Quick links to canonical documentation for our core services

== Planning and Records ==

 * ToDo: Both short term and longer term meta-planning.


=== 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


=== 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
   * OutpostInfo


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

=== General Sysadmin ===
Line 10: Line 83:
 * ChangingAdminPassword: How admins can change their UNIX passwords.
 * DaemonAdmin: Daemon-specific pages aimed at admins
 * DomTool: Administering and using the new domtool
 * IpAddresses: Listing of IPs that we use (nonpublic).
 * NewSystemHardware: Information on the new hardware
 * TaskDistribution: What each sysadmin is responsible for
 * 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.
 * 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.

=== Specific Services ===

<<Include(DaemonAdmin, ,to="^----$")>>
 * 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
 * VersionControlAdmin
 * wiki.hcoop.net
 * JabberAdmin
 * [[BugZilla]]
 * Other
   * CertificateAuthority: How to sign user SSL certificates and the like.


== Historical ==

Pages no longer considered relevant:

 * SoftwareArchitecturePlans: Plans for software installation.
 * SystemArchitecturePlans: Plans regarding our hardware.
 * InstallationLog contains ancient (~2005) records of installation of software and hardware
 * KrunkInfoz (Krunk is out of service)
 * [[Migration2009]] (never happened, staying at Peer1 was a better choice after all)
   * [[Migration2009/SoftwareSetup]]

Admin Area

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.

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.)

Admins: it is recommended that you watch the changes RSS feed 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 everyone gets notified about what is going on. Alternatively, you can create a wiki account and subscribe to the page regex .* (all pages).

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

  • ToDo: Both short term and longer term meta-planning.

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)