welcome: please sign in

Diff for "AdminArea"

Differences between revisions 146 and 166 (spanning 20 versions)
⇤ ← Revision 146 as of 2010-03-10 09:36:22 →
Size: 4758
Editor: RichardDarst
Comment:
← Revision 166 as of 2012-12-20 21:07:21 → ⇥
Size: 5220
Editor: ClintonEbadi
Comment: config management
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
This contains a list of pages that are of interest to the admins.
Line 9: Line 7:
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. 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 11: Line 9:
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.)
 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).
Line 15: Line 12:
Line 26: Line 24:
 * AddingNewAdmins: Documented procedures for adding new admin accounts
Line 29: Line 28:
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. 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.See DaemonDocumentation for links to the official documentation for the softare powering our core infrastructure.
Line 31: Line 30:
 * SystemArchitecture
Line 38: Line 38:
 * [[Code]] - Details of HCoop-specific code kept in git.hcoop.net
Line 42: Line 43:
 * [[Migration2009]]
   * [[Migration2009/SoftwareSetup]]
   * Migration2010Notes: Notes about the new server setup and way to transfer over old data
Line 62: Line 61:
 * SetupNewMachines: How to install a machine that adheres to our policies  * InstallationProcedure: how to install a machine that adheres to our policies
   * SetupNewMachines: The ''old'' guide to installing a machine that adheres to our policies
Line 74: Line 74:
   * OutpostInfo
Line 83: Line 84:
 * DebianArchive: Our local debian mirror for distributing custom packages
 * ConfigurationManagement: How we manage system wide configuration
Line 94: Line 97:
   * 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.).
<<Include(DaemonAdmin, ,to="^----$")>>
Line 104: Line 107:
   * CertificateAuthority: How to sign user SSL certificates and the like.
Line 108: Line 112:
 * Version Control  * VersionControlAdmin
Line 110: Line 114:
 * jabber
 * Other
   * CertificateAuthority: How to sign user SSL certificates and the like.		  * JabberAdmin
 * [[BugZilla]]
   
Line 123: Line 127:
 * [[Migration2009]] (never happened, staying at Peer1 was a better choice after all)
   * [[Migration2009/SoftwareSetup]]
----
CategorySystemAdministration

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.See DaemonDocumentation for links to the official documentation for the softare powering our core infrastructure.

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:

CategorySystemAdministration

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