welcome: please sign in

Diff for "AdminArea"

Differences between revisions 134 and 165 (spanning 31 versions)
Revision 134 as of 2010-01-06 02:56:22
Size: 3539
Editor: DavorOcelic
Comment:
Revision 165 as of 2012-12-20 20:41:49
Size: 5151
Editor: ClintonEbadi
Comment: link to new pages created from FritzVirtualization
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.

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 7: Line 13:
= Sysadmin work =
Line 9: Line 14:
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.

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.

== Plans ==

 * RoadMaps: Announcements of future plans and events.

== Quick hints ==
== To be an admin ==
Sections you should read if you are interested in being an admin.
Line 21: Line 19:
== 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
 * MitKerberos
 * AndrewFileSystem
 * EtcKeeper



= Admins and Admin Responsibilities =
=== Admins and Admin Responsibilities ===
Line 39: Line 24:
 * AddingNewAdmins: Documented procedures for adding new admin accounts
Line 40: Line 26:
= Technical Records = === 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.

 * SystemArchitecture
 * DaemonFileSecurity
 * DomTool
 * AuthenticationScheme
 * [[OpenLDAP]]
 * MitKerberos
 * AndrewFileSystem
 * EtcKeeper
 * [[Code]] - Details of HCoop-specific code kept in git.hcoop.net

== Planning and Records ==

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


=== Technical Records ===
Line 47: Line 52:
= Sysadmin Stuff = === Views ===
Line 49: Line 54:
== General Sysadmin ==  * 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]]
 * 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


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

=== General Sysadmin ===
Line 51: Line 83:
 * SetupNewMachines: How to put the basic hcoop AFS/Kerberos client config on a newly acquired machine.
Line 53: Line 84:
 * 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
Line 60: Line 89:
 * 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 61: Line 95:
== 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 73: Line 97:
== Specific Machines ==
 * PowerEdge2850 is about '''deleuze'''
 * RebootingDeleuze: Steps to take after rebooting deleuze.
 * RebootingMireSp: How to reboot mire using its SP interface.
 * HopperServiceProcessor
 * KrunkInfoz
<<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.
 * DNS
   * ZoneTransfers is also mostly blank.
 * Databases
 * Backups
 * VersionControlAdmin
 * wiki.hcoop.net
 * JabberAdmin
 * [[BugZilla]]
   
Line 80: Line 117:
= Historical =
== Historical ==

Pages no longer considered relevant:
Line 84: Line 125:
 * KrunkInfoz (Krunk is out of service)
 * [[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).

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)