Category:Sysadmin - Revision history

Khtang at 20:57, 27 December 2018

2018-12-27T20:57:44Z

2014-05-23T13:06:03Z

Pro-active maintenance

← Older revision		Revision as of 13:06, 23 May 2014
Line 18:		Line 18:
	* [[Periodic system maintenance]]		* [[Periodic system maintenance]]
	* manage public DNS https://www.cgl.ucsf.edu/dns_dhcp/		* manage public DNS https://www.cgl.ucsf.edu/dns_dhcp/
			* edit host alias file to define private address machine names. Use alpha:/opt/bks/bin/add-host-alias. This script freezes and unfreezes the dynamic zones using rndc freeze <zone> and rndc thaw <zone> e.g. zone is cluster.ucsf.bkslab.org
			* NB CNAMES must be terminated with a dot .
			* NB bkslab.org is managed by aaa1 but uoft.bkslab.org is delegated to spinaltap and ucsf.bkslab.org to alpha
			* use joker.com to manage top level bkslab.org domain

			= Conventions =
			* When we create a desktop, we create the user account l_<USER> (l as in lion or local). This allows the user to use the desktop if ldap or network are down.

	= Reactive maintenance =		= Reactive maintenance =

2014-05-01T17:26:29Z

← Older revision		Revision as of 17:26, 1 May 2014
Line 1:		Line 1:
			To contact the systadmins, look [[sysadmin\|here]].

	These are pages for docking.org sysadmins, also useful for anyone who wants to install, run and manage a docking.org site.		These are pages for docking.org sysadmins, also useful for anyone who wants to install, run and manage a docking.org site.
	Sysadmin pages are only relevant if you have sudo on a docking.org type cluster. For other roles, see [[:Category:Roles\|here]].		Sysadmin pages are only relevant if you have sudo on a docking.org type cluster. For other roles, see [[:Category:Roles\|here]].

2014-04-23T14:26:38Z

← Older revision		Revision as of 14:26, 23 April 2014
Line 15:		Line 15:
	Pro-active maintenance is classified temporally, reactive is always in the present.		Pro-active maintenance is classified temporally, reactive is always in the present.
	* [[Periodic system maintenance]]		* [[Periodic system maintenance]]
			* manage public DNS https://www.cgl.ucsf.edu/dns_dhcp/

	= Reactive maintenance =		= Reactive maintenance =

2014-04-07T15:32:33Z

Policies

← Older revision		Revision as of 15:32, 7 April 2014
Line 25:		Line 25:

	= Policies =		= Policies =
	* we have an elaborate private ~~address scheme~~ that is possibly more trouble than it is worth		* we have an elaborate scheme for [[private addresses]] that is possibly more trouble than it is worth
	* if a machine does not have to be on the public network, is should not be on the public network		* if a machine does not have to be on the public network, is should not be on the public network
	* use iptables aggressively to suppress nearly all public services outside the lab		* use iptables aggressively to suppress nearly all public services outside the lab
			* use VMs
			* document all machines in the google docs
			* document everything that is not security related on the wiki

	= System down/hung/crashed/offline =		= System down/hung/crashed/offline =

2014-04-07T15:28:39Z

← Older revision		Revision as of 15:28, 7 April 2014
Line 11:		Line 11:
	3) Sysadmin security secrets		3) Sysadmin security secrets

	= Pro-active =		= Pro-active maintenance =
	There are two kinds of maintenance, reactive and pro-active.		There are two kinds of maintenance, reactive and pro-active.
	Pro-active maintenance is classified temporally, reactive is always in the present.		Pro-active maintenance is classified temporally, reactive is always in the present.
	* [[Periodic system maintenance]]		* [[Periodic system maintenance]]

	= Reactive =		= Reactive maintenance =

	* Create a new user		* Create a new user
Line 23:		Line 23:
	* disk full		* disk full
	* security breach		* security breach

			= Policies =
			* we have an elaborate private address scheme that is possibly more trouble than it is worth
			* if a machine does not have to be on the public network, is should not be on the public network
			* use iptables aggressively to suppress nearly all public services outside the lab



	= System down/hung/crashed/offline =		= System down/hung/crashed/offline =

2014-03-31T16:58:24Z

Pro-active

← Older revision		Revision as of 16:58, 31 March 2014
Line 15:		Line 15:
	Pro-active maintenance is classified temporally, reactive is always in the present.		Pro-active maintenance is classified temporally, reactive is always in the present.
	* [[Periodic system maintenance]]		* [[Periodic system maintenance]]
	* [[Backups]]
	* [[Security review]]
	* [[Software upgrades]]

	= Reactive =		= Reactive =

2014-03-31T16:57:59Z

Reactive

← Older revision		Revision as of 16:57, 31 March 2014
Line 24:		Line 24:
	* Retire a user		* Retire a user
	* RAID disk failure		* RAID disk failure
			* disk full
			* security breach

	= System down/hung/crashed/offline =		= System down/hung/crashed/offline =

2014-03-31T16:38:13Z

← Older revision		Revision as of 16:38, 31 March 2014
Line 6:		Line 6:
	{{TOCright}}		{{TOCright}}

	~~'''~~For security reasons, documents pertaining to ~~authentication and access~~ are kept in google docs~~'''~~		For security reasons, documents pertaining to security are kept in google docs. For access, contact the [[sysadmin]]s. This includes
	~~= Google Docs docs =~~		1) Software Licenses
	~~Some documents do not belong on the wiki~~. For access, contact the [[sysadmin]]s.		2) Our Computers
	* Lab Software ~~Status~~		3) Sysadmin security secrets
	* Lab IP addresses
	* Sysadmin ~~Secrets~~


	~~There are two kinds of maintenance, reactive and pro-active. Pro-active maintenance is classified temporally, reactive is always in the present.~~

	= Pro-active =		= Pro-active =
			There are two kinds of maintenance, reactive and pro-active.
			Pro-active maintenance is classified temporally, reactive is always in the present.
	* [[Periodic system maintenance]]		* [[Periodic system maintenance]]
	* [[Backups]]		* [[Backups]]
Line 59:		Line 55:

	* Add new hardware to the cluster		* Add new hardware to the cluster





	[[Category:Sysadmin]]		[[Category:Sysadmin]]
	[[Category:Tutorials]]		[[Category:Tutorials]]








	== Procedures ==		== Procedures ==

2014-03-31T16:35:34Z

← Older revision		Revision as of 16:35, 31 March 2014
Line 1:		Line 1:
	These are pages for docking.org sysadmins, also useful for anyone who wants to install, run and manage a docking.org site.		These are pages for docking.org sysadmins, also useful for anyone who wants to install, run and manage a docking.org site.
	Sysadmin pages are only relevant if you have sudo on a docking.org type cluster. For other roles, see [[:Category:Roles\|here]].		Sysadmin pages are only relevant if you have sudo on a docking.org type cluster. For other roles, see [[:Category:Roles\|here]].
	Once the docking lab has been [[So you want to set up a lab \| set up ]], it must be maintained.		Once the docking lab has been [[So you want to set up a lab \| set up ]], it must be [[Periodic_system_maintenance \|maintained]].
	This guide covers ~~the events we could think of that may occur after you have~~ a ~~computational pharmacology lab up and running~~.		This guide covers everything it takes to be a docking.org [[sysadmin]].

	{{TOCright}}		{{TOCright}}