welcome: please sign in

Diff for "AdminArea"

Differences between revisions 141 and 171 (spanning 30 versions)
Revision 141 as of 2010-01-07 23:00:15
Size: 3696
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 3: Line 3:
This contains a list of pages that are of interest to the admins. = 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.
Line 7: Line 10:
= Sysadmin work =
Line 9: Line 11:
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 ==
Line 11: Line 13:
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. Sections you should read if you are interested in being an admin.
Line 13: Line 15:
== Plans == {{{#!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 15: Line 19:
 * RoadMaps: Announcements of future plans and events. === Admins and Admin Responsibilities ===
Line 17: Line 21:
== Views ==  * 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.
Line 19: Line 26:
 * Fritz.hcoop.net - [[http://fritz.hcoop.net/munin/|Munin reports]] === Introductory material ===
Line 21: Line 28:
== Quick hints == 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 23: Line 30:
 * TipsAndTricks

== Specific Machines ==
 * PowerEdge2850 is about '''deleuze'''
 * RebootingDeleuze: Steps to take after rebooting deleuze.
 * RebootingMireSp: How to reboot mire using its SP interface.
 * HopperServiceProcessor

== Guides ==

 * SetupNewMachines: How to install a machine that adheres to our policies

== 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.
 * SystemArchitecture
Line 46: Line 38:
 * [[Code]] - Details of HCoop-specific code kept in git.hcoop.net
Line 47: Line 40:
= 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.
== Planning and Records ==
Line 53: Line 42:
= Technical Records =  * ToDo: Both short term and longer term meta-planning.


=== Technical Records ===
Line 59: Line 51:
== Specific Machines ==
This documents machine-specific (hardware) things, or specific configuration necessary for ''that machine''.
Line 60: Line 54:
= Sysadmin Stuff =  * [[Hardware]]
 * InstallationProcedure: how to install a machine that adheres to our policies
   * SetupNewMachines: The ''old'' guide to installing 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
Line 62: Line 70:
== General Sysadmin ==
== Services ==
This documents all software things that are not machine specific.

=== General Sysadmin ===
Line 65: Line 78:
 * KvmAccess: How to use the remove KVM and avoid going on site.
 * KvmInfo
 * UserManagement only talks about adduser/deluser right now.
 * DebianArchive: Our local debian mirror for distributing custom packages
 * ConfigurationManagement: How we manage system wide configuration
Line 72: Line 84:
 * 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.
   * AddingNewAdmins: Documented procedures for adding new admin accounts
   * ChangingAdminPassword: How admins can change their UNIX passwords.
Line 73: Line 91:
== 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.
 * SpamAssassinAdmin
=== Specific Services ===
Line 85: Line 93:
= Historical = <<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
   * CertificateAuthority: How to sign user SSL certificates and the like.
   * WebServicesAdmin: How to administer hcoop provided web services
 * DNS
   * ZoneTransfers is also mostly blank.
 * Databases
 * Backups
 * VersionControlAdmin
 * wiki.hcoop.net
 * JabberAdmin
 * [[BugZilla]]
   
== Historical ==
Line 89: Line 117:
 * TipsAndTricks
Line 93: 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)