Skip to content
Snippets Groups Projects
Commit f5e00b56 authored by Caughlin Bohn's avatar Caughlin Bohn
Browse files

Added newer screenshots to duo

parent 07328947
Branches
No related tags found
3 merge requests!78Added Office Hours Page,!77Added DUO Screenshot Update and SandStone Docs,!76Sandstone Doc Page And DUO Screenshots
...@@ -3,18 +3,8 @@ title = "How to Connect" ...@@ -3,18 +3,8 @@ title = "How to Connect"
description = "What is a cluster and what is HPC" description = "What is a cluster and what is HPC"
weight = "9" weight = "9"
+++ +++
High-Performance Computing is the use of groups of computers to solve computations a user or group would not be able to solve in a reasonable time-frame on their own desktop or laptop. This is often achieved by splitting one large job amongst numerous cores or 'workers'. This is similar to how a skyscraper is built by numerous individuals rather than a single person. Many fields take advantage of HPC including bioinformatics, chemistry, materials engineering, and newer fields such as educational psychology and philosophy. Connecting to one of our clusters is very simple. In a terminal or command prompt, type `ssh <username>@crane.unl.edu` and the corresponding password to get access to the HCC cluster **Crane**.
{{< figure src="/images/cluster.png" height="450" >}} {{< highlight bash >}}
HPC clusters consist of four primary parts, the login node, management node, workers, and a central storage array. All of these parts are bound together with a scheduler such as HTCondor or SLURM. $ ssh <username>@crane.unl.edu
</br></br> $ <password>
#### Login Node: {{< /highlight >}}
Users will automatically land on the login node when they log in to the clusters. You will [submit jobs] ({{< ref "/guides/submitting_jobs" >}}) using one of the schedulers and pull the results of your jobs. Running jobs on the login node directly will be stopped so others can use the login node to submit jobs.
</br></br>
#### Management Node:
The management node does as it sounds, it manages the cluster and provides a central point to manage the rest of the systems.
</br></br>
#### Worker Nodes:
The worker nodes are what run and process your jobs that are submitted from the schedulers. Through the use of the schedulers, more work can be efficiently done by squeezing in all jobs possible for the resources requested throughout the nodes. They also allow for fair use computing by making sure one user or group is not using the entire cluster at once and allowing others to use the clusters.
</br></br>
#### Central Storage Array:
The central storage array allows all of the nodes within the cluster to have access to the same files without needing to transfer them around. HCC has three arrays mounted on the clusters with more details [here]({{< ref "/guides/handling_data" >}}).
+++
title = "Introduction to HPC"
description = "What is a cluster and what is HPC"
weight = "1"
+++
High-Performance Computing is the use of groups of computers to solve computations that a user or group would not be able to solve in a reasonable time-frame on their own desktop or laptop. This is often achieved by splitting one large job amongst numerous cores or 'workers'. This is similar to how a skyscraper is built by numerous individuals rather than a single person. Many fields take advantage of HPC including bioinformatics, chemistry, materials engineering, and newer fields such as educational psychology and philosophy.
HPC clusters consist of four primary parts, the login node, management node, workers, and a central storage array. The cullmination of these parts create a high performance cluster that can recieve work from the schedulers.
{{< figure src="/images/cluster.png" height="450" >}}
##### [Source](https://training.h3abionet.org/technical_workshop_2015/?page_id=403)
#### Login Node:
Users will automatically land on the login node when they log in to the clusters. You will [submit jobs] ({{< ref "/quickstarts/submitting_jobs" >}}) using one of the schedulers and pull the results of your jobs. Running jobs on the login node directly will be stopped so others can use the login node to submit jobs.
</br></br>
#### Management Node:
The management node contains and runs the schedulers and other utilities for managing the cluster.
</br></br>
#### Worker Nodes:
The worker nodes are what run and process your jobs that are submitted from the schedulers. Through the use of the schedulers, more work can be efficiently done by squeezing in all jobs possible for the resources requested throughout the nodes. They also allow for fair use computing by making sure one user or group is not using the entire cluster at once and allowing others to use the clusters.
</br></br>
#### Central Storage Array:
The central storage array allows all of the nodes within the cluster to have access to the same files without needing to transfer them around. HCC has three arrays mounted on the clusters with more details [here]({{< ref "/guides/handling_data" >}}).
\ No newline at end of file
...@@ -75,11 +75,11 @@ this example, the choices are Duo Push notification, SMS message, or ...@@ -75,11 +75,11 @@ this example, the choices are Duo Push notification, SMS message, or
phone call. Choosing option 1 for Duo Push, a request to verify the phone call. Choosing option 1 for Duo Push, a request to verify the
login will be sent to the user's smartphone. login will be sent to the user's smartphone.
{{< figure src="/images/5832716.png" height="350" >}} {{< figure src="/images/DUORequest.jpg" height="350" >}}
Simply tap `Approve` to verify the login. Simply tap `Approve` to verify the login.
{{< figure src="/images/5832717.png" height="350" >}} {{< figure src="/images/DUOApprove.jpg" height="350" >}}
{{% notice warning%}}**If you receive a verification request you didn't initiate, deny the {{% notice warning%}}**If you receive a verification request you didn't initiate, deny the
request and contact HCC immediately via email at request and contact HCC immediately via email at
......
static/images/5832716.png

29 KiB

static/images/5832717.png

32.1 KiB

static/images/DUOApprove.jpg

208 KiB

static/images/DUORequest.jpg

255 KiB

0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment