welcome: please sign in

Diff for "AdminArea"

Differences between revisions 172 and 173
Revision 172 as of 2013-05-30 18:20:47
Size: 4694
Editor: ClintonEbadi
Comment: overhaul step two: move obsolete links
Revision 173 as of 2013-05-30 18:43:12
Size: 4519
Editor: ClintonEbadi
Comment: step three: remove redundant (and outdated) information better represented on Hardware
Deletions are marked like this. Additions are marked like this.
Line 47: Line 47:
== Specific Machines == == Hardware / On-Site Infrastructure ==
Line 49: Line 49:
This documents machine-specific (hardware) things, or specific configuration necessary for ''that machine''.  * [[Hardware]]: information on the colocation facility and the physical/virtual machines we are using. Tips on using service processors etc. are here.
 * InstallationProcedure: how to install a machine that adheres to our policies
   * KernelVirtualMachine: how we are using libvirt
   * 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
Line 51: Line 55:
 * [[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
== Software ==
Line 67: Line 57:

== Services ==
This documents all software things that are not machine specific.
This documents all software things that are not specific to the on-site infrastructure.

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.

Planning and Records

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

  • 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

Hardware / On-Site Infrastructure

  • Hardware: information on the colocation facility and the physical/virtual machines we are using. Tips on using service processors etc. are here.

  • InstallationProcedure: how to install a machine that adheres to our policies

  • KvmAccess: How to use the remove KVM and avoid going on site

Software

This documents all software things that are not specific to the on-site infrastructure.

General Sysadmin

Specific Services

Historical

Pages no longer considered relevant, but may be of historical interest:


CategorySystemAdministration

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