3552
Comment:
|
← Revision 176 as of 2020-08-23 22:16:03 ⇥
4549
JabberAdmin page moved to DaemonAdmin
|
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: |
== Quick hints == * TipsAndTricks == 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 * OpenLDAP * MitKerberos * AndrewFileSystem * EtcKeeper = Admins and Admin Responsibilities = |
|
Line 41: | 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. * DaemonDocumentation: manuals for core services with which you should be familiar * SystemArchitecture * DomTool * MitKerberos * AndrewFileSystem * EtcKeeper * [[Code]]: Details of HCoop-specific code kept in git.hcoop.net * [[OpenLDAP]] == Planning and Records == * ToDo: Both short term and longer term meta-planning. |
Line 47: | Line 47: |
== Hardware / On-Site Infrastructure == | |
Line 48: | Line 49: |
= Sysadmin Stuff = | * [[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 50: | Line 55: |
== General Sysadmin == | == Software == This documents all software things that are not specific to the on-site infrastructure. === General Sysadmin === Documentation useful for the daily care and feeding of our systems. * AuthenticationScheme |
Line 52: | Line 65: |
* SetupNewMachines: How to put the basic hcoop AFS/Kerberos client config on a newly acquired machine. * DebianPackaging: How to make custom HCoop Debian packages. * KvmAccess: How to use the remove KVM and avoid going on site. * KvmInfo * UserManagement only talks about adduser/deluser right now. |
* DebianPackaging: How to make custom HCoop Debian packages, and details on our debian archive * ConfigurationManagement: How we manage system wide configuration * SystemAuthentication lists authentication * UserManagement * MemberFreezing: How to freeze and unfreeze members who get behind on dues * AdminUserSetup, AddingNewAdmins, ChangingAdminPassword: lists steps to create (blank), delete, and change passwords of admin users. === Specific Services === Documentation of interest to people maintaining particular services. <<Include(DaemonAdmin, ,to="^----$")>> * DomTool * Web * CertificateAuthority: How to sign user SSL certificates and the like. * WebServicesAdmin: How to administer hcoop provided web services * VersionControlAdmin * [[BugZilla]] == Historical == Pages no longer considered relevant, but may be of historical interest or otherwise useful as source material for updated documentation. * AFS / Kerberos * SetupNewAfsServer: How to set up a new AFS server. * PrincipalsForNonHumans talks about kerberos for automated tasks. * MailMan contains no information... * SpamAssassinAdmin * UsingResourceLimits * DaemonFileSecurity |
Line 58: | Line 98: |
* InstalledSoftware lists non-debian installed software. * SystemAuthentication lists authentication * UsingResourceLimits If this is still accurate, we should move it to MemberManual area. == 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 Machines == * PowerEdge2850 is about '''deleuze''' * RebootingDeleuze: Steps to take after rebooting deleuze. * RebootingMireSp: How to reboot mire using its SP interface. * HopperServiceProcessor * KrunkInfoz = Historical = |
* TipsAndTricks |
Line 85: | Line 102: |
* KrunkInfoz (Krunk is out of service) * [[Migration2009]] (never happened, staying at Peer1 was a better choice after all) * [[Migration2009/SoftwareSetup]] * InstalledSoftware ---- 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.
Contents
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
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.
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.
DaemonDocumentation: manuals for core services with which you should be familiar
Code: Details of HCoop-specific code kept in git.hcoop.net
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
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
Software
This documents all software things that are not specific to the on-site infrastructure.
General Sysadmin
Documentation useful for the daily care and feeding of our systems.
BackupInfo: Information on how to recover deleted files from our off-site backups.
DebianPackaging: How to make custom HCoop Debian packages, and details on our debian archive
ConfigurationManagement: How we manage system wide configuration
SystemAuthentication lists authentication
MemberFreezing: How to freeze and unfreeze members who get behind on dues
AdminUserSetup, AddingNewAdmins, ChangingAdminPassword: lists steps to create (blank), delete, and change passwords of admin users.
Specific Services
Documentation of interest to people maintaining particular services.
We've recorded some special instructions, hints, etc., for daemons with non-standard configuration.
- Web
CertificateAuthority: How to sign user SSL certificates and the like.
WebServicesAdmin: How to administer hcoop provided web services
Historical
Pages no longer considered relevant, but may be of historical interest or otherwise useful as source material for updated documentation.
- AFS / Kerberos
SetupNewAfsServer: How to set up a new AFS server.
PrincipalsForNonHumans talks about kerberos for automated tasks.
- Mail
MailMan contains no information...
SoftwareArchitecturePlans: Plans for software installation.
SystemArchitecturePlans: Plans regarding our hardware.
InstallationLog contains ancient (~2005) records of installation of software and hardware
KrunkInfoz (Krunk is out of service)
Migration2009 (never happened, staying at Peer1 was a better choice after all)