Cluster - Revision history

Jesselivezey: /* Connect */

2017-01-11T00:45:43Z

Connect

← Older revision		Revision as of 00:37, 11 January 2017
Line 54:		Line 54:

	== Connect ==		== Connect ==

	~~==== Google Authenticator App (get a password) ====~~

	* Open the google Authenticator App
	* Enter your personal pin
	* Enter the one-time pin

	=== ssh to a login node ===		=== ssh to a login node ===
Line 70:		Line 64:

	''' note: please don't use the login nodes for computations (e.g. matlab, python)! '''		''' note: please don't use the login nodes for computations (e.g. matlab, python)! '''

			==== Google Authenticator App (get a password) ====

			* Open the google Authenticator App
			* Enter your personal pin
			* Enter the one-time pin

	=== Setup environment ===		=== Setup environment ===

2017-01-11T00:44:53Z

Pledge App (get a password)

← Older revision		Revision as of 00:36, 11 January 2017
Line 55:		Line 55:
	== Connect ==		== Connect ==

	==== ~~Pledge~~ App (get a password) ====		==== Google Authenticator App (get a password) ====

	* ~~Run~~ the ~~pledge app and click "Generate one-time password"~~		* Open the google Authenticator App
	* Enter your ~~PIN and press "Enter"~~		* Enter your personal pin
	* ~~The application will present your 7 digit~~ one time ~~password~~		* Enter the one-time pin

	=== ssh to a login node ===		=== ssh to a login node ===

2017-01-11T00:43:42Z

Getting an account and one-time password service

← Older revision		Revision as of 00:35, 11 January 2017
Line 28:		Line 28:
	'''OTP (One Time Password) Service'''		'''OTP (One Time Password) Service'''

	Once you have a username, you will need to follow the instructions found [https://~~commons~~.lbl.gov/~~display~~/~~itfaq~~/~~OTP+%28One+Time+Password%29+Service here~~] to set up the ~~Pledge~~ application, which gives you a one-time password for logging into the cluster ~~(see '''Installing and Configuring the OTP Token''')~~.		Once you have a username, you will need to follow the instructions found [https://sites.google.com/a/lbl.gov/high-performance-computing-services-group/authentication/linotp-usage] to set up the Google Authenticator application, which gives you a one-time password for logging into the cluster.

	== Directory setup ==		== Directory setup ==

2016-10-12T18:12:24Z

Data

← Older revision		Revision as of 18:04, 12 October 2016
Line 49:		Line 49:
	For large amounts of data, please create a directory		For large amounts of data, please create a directory

	/clusterfs/cortex/~~scratch~~/username		/clusterfs/cortex/users/username

	and store the data inside that directory. Note that unlike the home directory, scratch space is not backed up and permanence of your data is not guaranteed. There is a total limit of 17 TB for this drive that is shared by everyone at the Redwood Center.		and store the data inside that directory. Note that unlike the home directory, scratch space is not backed up and permanence of your data is not guaranteed. There is a total limit of 17 TB for this drive that is shared by everyone at the Redwood Center.

2016-10-12T18:10:13Z

Data

← Older revision		Revision as of 18:02, 12 October 2016
Line 51:		Line 51:
	/clusterfs/cortex/scratch/username		/clusterfs/cortex/scratch/username

	and store the data inside that directory. Note that unlike the home directory, scratch space is not backed up and permanence of your data is not guaranteed. There is a total limit of 4 TB for this drive that is shared by everyone at the Redwood Center.		and store the data inside that directory. Note that unlike the home directory, scratch space is not backed up and permanence of your data is not guaranteed. There is a total limit of 17 TB for this drive that is shared by everyone at the Redwood Center.

	== Connect ==		== Connect ==

2016-10-12T18:09:39Z

Hardware Overview

← Older revision		Revision as of 18:01, 12 October 2016
Line 13:		Line 13:
	The current hardware and node configuration is listed [https://sites.google.com/a/lbl.gov/high-performance-computing-services-group/ucb-non-supercluster/cortex here].		The current hardware and node configuration is listed [https://sites.google.com/a/lbl.gov/high-performance-computing-services-group/ucb-non-supercluster/cortex here].

	In addition to the compute nodes we ~~own~~ a file server ~~TODO~~		In addition to the compute nodes we ave a 17TB file server at
	~~NetOp 4TB~~		/clusterfs/cortex/users
	which is mounted as scratch space.		which is mounted as scratch space.

2016-10-12T18:01:43Z

Job Management

← Older revision		Revision as of 17:53, 12 October 2016
Line 178:		Line 178:

	In order to coordinate our cluster usage patterns fairly, our cluster uses a job manager known as SLURM. If your are planning to run jobs on the cluster you should be using SLURM! Learn how [http://redwood.berkeley.edu/wiki/Cluster_Job_Management here].		In order to coordinate our cluster usage patterns fairly, our cluster uses a job manager known as SLURM. If your are planning to run jobs on the cluster you should be using SLURM! Learn how [http://redwood.berkeley.edu/wiki/Cluster_Job_Management here].


	= Software =		= Software =

2016-10-12T18:01:23Z

Data

← Older revision		Revision as of 17:53, 12 October 2016
Line 51:		Line 51:
	/clusterfs/cortex/scratch/username		/clusterfs/cortex/scratch/username

	and store the data inside that directory. Note that unlike the home directory, scratch space is not backed up and permanence of your data is not guaranteed. There is a total limit of 4 TB for this drive that is shared by everyone at the Redwood ~~center~~.		and store the data inside that directory. Note that unlike the home directory, scratch space is not backed up and permanence of your data is not guaranteed. There is a total limit of 4 TB for this drive that is shared by everyone at the Redwood Center.

	== Connect ==		== Connect ==

2016-04-06T02:13:58Z

Hardware Overview

← Older revision		Revision as of 02:05, 6 April 2016
Line 11:		Line 11:
	== Hardware Overview ==		== Hardware Overview ==

	The current hardware and node configuration is listed [https://sites.google.com/a/lbl.gov/high-performance-computing-services-group/ucb-supercluster/cortex here].		The current hardware and node configuration is listed [https://sites.google.com/a/lbl.gov/high-performance-computing-services-group/ucb-non-supercluster/cortex here].

	In addition to the compute nodes we own a file server TODO		In addition to the compute nodes we own a file server TODO

2016-02-04T19:47:44Z

General Information

← Older revision		Revision as of 19:39, 4 February 2016
Line 4:		Line 4:

	In order for the cluster to be useful and well-utilized, it works best for everyone to submit jobs TODO (see '''SLURM''' further down on this page for the details) to the queue. A job may not start right away, but will get run once its turn comes. Please do not run extended interactive sessions or ssh directly to worker nodes for performing computation.		In order for the cluster to be useful and well-utilized, it works best for everyone to submit jobs TODO (see '''SLURM''' further down on this page for the details) to the queue. A job may not start right away, but will get run once its turn comes. Please do not run extended interactive sessions or ssh directly to worker nodes for performing computation.

			== Cluster Administration ==

			[[ClusterAdmin]] has information about cluster administration.

	== Hardware Overview ==		== Hardware Overview ==
Line 170:		Line 174:

	* This is useful if you believe someone is abusing the machine and would like to send him/her a friendly reminder.		* This is useful if you believe someone is abusing the machine and would like to send him/her a friendly reminder.

	~~== Cluster Administration ==~~

	~~[[ClusterAdmin]] has information about cluster administration.~~

	= Job Management =		= Job Management =