welcome: please sign in

Diff for "AdminArea"

Differences between revisions 148 and 171 (spanning 23 versions)
Revision 148 as of 2010-03-29 12:06:32
Size: 4854
Editor: DavorOcelic
Comment:
Revision 171 as of 2013-05-30 18:00:01
Size: 4972
Editor: ClintonEbadi
Comment: first stab at an overhaul: delete really obsolete content
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
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 14: Line 11:
== To be an admin ==
Line 15: Line 13:
== To be an admin ==
Line 18: Line 15:
 * TipsAndTricks {{{#!wiki tip
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 21: Line 20:
Line 28: 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 30: Line 30:
 * SystemArchitecture
Line 42: Line 43:
 * [[Migration2009]]
   * [[Migration2009/SoftwareSetup]]
   * Migration2010Notes: Notes about the new server setup and way to transfer over old data
Line 52: Line 51:

=== Views ===

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

Line 62: Line 55:
 * 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 68:
   * OutpostInfo
Line 83: Line 78:
 * DebianArchive: Our local debian mirror for distributing custom packages
 * ConfigurationManagement: How we manage system wide configuration
Line 91: Line 88:
   * AddingNewAdmins: Documented procedures for adding new admin accounts
Line 94: Line 92:
   * 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 102:
   * CertificateAuthority: How to sign user SSL certificates and the like.
   * WebServicesAdmin: How to administer hcoop provided web services
Line 108: Line 108:
 * Version Control  * VersionControlAdmin
Line 110: Line 110:
 * jabber
 * Other
   * CertificateAuthority: How to sign user SSL certificates and the like.

 * JabberAdmin
 * [[BugZilla]]
   
Line 119: Line 117:
 * TipsAndTricks
Line 123: Line 122:
 * [[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.

To be an admin

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

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

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

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)