How to access the public servers: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
== Server Types and Management== | |||
You can ssh into our public computer server via SSH: | |||
'''courtyard.gi.ucsc.edu''': 1TB RAM, 64 cores, 672GBTB local scratch space | |||
This server is running CentOS 7.5 Linux. It is managed by the Genomics Institute Cluster Admin group. If you need software installed on it, please make your request by emailing cluster-admin@soe.ucsc.edu. | |||
== Storage == | |||
These servers mount two types of storage; home directories and group storage directories. Your home directory will be located as "/public/home/username" and has a 30GB quota. The group storage directories are created per PI, and each group directory has a 15TB quota. For example, if David Haussler is the PI that you report to directly, then the directory would exist as /public/groups/hausslerlab. Request access to that group directory and you will then be able to write to it. Each of those group directories are shared by the lab it belongs to, so you must be wary of everyone's data usage and share the 15TB available per group accordingly. | |||
== Actually Doing Work and Computing == | |||
When doing research, running jobs and the like, please be careful of your resource consumption on the server you are on. Don't run too many threads or cores at once if such a thing overruns the RAM available or the disk IO available. If you are not sure of your potential RAM, CPU or disk impact, start small with one or two processes and work your way up from there. Also, before running your stuff, check what else is already happening on the server by using the 'top' command to see who else and what else is running and what kind of resources are already being consumed. If, after starting a process, you realize that the server slows down considerably or becomes unusable, kill your processes and re-evaluate what you need to make things work. These servers are shared resources - be a good neighbor! | |||
== Serving Files to the Public via the Web == | |||
If you want to setup a web page on courtyard, or serve files over HTTP from there, do this: | |||
mkdir /public/home/''your_username''/public_html | mkdir /public/home/''your_username''/public_html | ||
chmod 755 /public/home/''your_username''/public_html | chmod 755 /public/home/''your_username''/public_html | ||
Put data in the public_html directory. The URL will be: | |||
http://public.gi.ucsc.edu/''~username''/ | http://public.gi.ucsc.edu/''~username''/ |
Revision as of 01:25, 13 July 2018
Server Types and Management
You can ssh into our public computer server via SSH:
courtyard.gi.ucsc.edu: 1TB RAM, 64 cores, 672GBTB local scratch space
This server is running CentOS 7.5 Linux. It is managed by the Genomics Institute Cluster Admin group. If you need software installed on it, please make your request by emailing cluster-admin@soe.ucsc.edu.
Storage
These servers mount two types of storage; home directories and group storage directories. Your home directory will be located as "/public/home/username" and has a 30GB quota. The group storage directories are created per PI, and each group directory has a 15TB quota. For example, if David Haussler is the PI that you report to directly, then the directory would exist as /public/groups/hausslerlab. Request access to that group directory and you will then be able to write to it. Each of those group directories are shared by the lab it belongs to, so you must be wary of everyone's data usage and share the 15TB available per group accordingly.
Actually Doing Work and Computing
When doing research, running jobs and the like, please be careful of your resource consumption on the server you are on. Don't run too many threads or cores at once if such a thing overruns the RAM available or the disk IO available. If you are not sure of your potential RAM, CPU or disk impact, start small with one or two processes and work your way up from there. Also, before running your stuff, check what else is already happening on the server by using the 'top' command to see who else and what else is running and what kind of resources are already being consumed. If, after starting a process, you realize that the server slows down considerably or becomes unusable, kill your processes and re-evaluate what you need to make things work. These servers are shared resources - be a good neighbor!
Serving Files to the Public via the Web
If you want to setup a web page on courtyard, or serve files over HTTP from there, do this:
mkdir /public/home/your_username/public_html chmod 755 /public/home/your_username/public_html
Put data in the public_html directory. The URL will be:
http://public.gi.ucsc.edu/~username/