Merge pull request #19 from chpc-tech-eval/tut3/intel

Tut3/intel

Author: nyameko

README.md

@@ -16,8 +16,6 @@ This tutorial will conclude with you downloading, installing and running the Hig
 
 <!-- markdown-toc start - Don't edit this section. Run M-x markdown-toc-refresh-toc -->
 
-1. [Tutorial 1: Standing Up Your Head Node and Running HPL](#tutorial-1-standing-up-your-head-node-and-running-hpl)
-1. [Table of Contents](#table-of-contents)
 1. [Checklist](#checklist)
 1. [Network Primer](#network-primer)
     1. [Basic Networking Example (WhatIsMyIp.com)](#basic-networking-example-whatismyipcom)

resources/github_profile_settings_highlight.png

@@ -503,13 +503,13 @@ If your NAT is working correctly and your compute node's DNS was set correctly w
 > **! >>> Without access to a working DNS server you won't be able to install packages on your compute node (or head node for that matter), even if the internet is otherwise working.**
 
 <div style="page-break-after: always;"></div>
-
+## Routing your Compute Nodes Exclusively Through Your Head Node
 
 # Network Time Protocol
 
 **NTP** or **network time protocol** enables you to synchronise the time across all the computers in your network. This is important for HPC clusters as some applications require that system time be accurate between different nodes (imagine receiving a message 'before' it was sent).
 
-It is also important that your timezones are also consistent across your machines. Time actions on **CentOS 8** can be controlled by a tool called `timedatectl`. For example, if you wanted to change the timezone that your system is in, you could use `timedatectl list-timezones`, find the one you want and then set it by using `timedatectl set-timezone <timezone>`. `timedatectl` can also set the current time on a local machine and more. 
+It is also important that your timezones are also consistent across your machines. Time actions on **CentOS 8** can be controlled by a tool called `timedatectl`. For example, if you wanted to change the timezone that your system is in, you could use `timedatectl list-timezones`, find the one you want and then set it by using `timedatectl set-timezone <timezone>`. `timedatectl` can also set the current time on a local machine and more.
 
 You will now **setup the NTP service** (through the `chronyd` implementation) on your head node and then connect your compute nodes to it.
 

tutorial1/README.md

@@ -3,34 +3,32 @@
 ## Table of Contents
 <!-- markdown-toc start - Don't edit this section. Run M-x markdown-toc-refresh-toc -->
 
-- [Student Cluster Compeititon - Tutorial 4](#student-cluster-compeititon---tutorial-4)
-  - [Table of Contents](#table-of-contents)
-- [Checklist](#checklist)
-  - [(Delete) - Remote Web Service Access](#delete---remote-web-service-access)
-- [Prometheus](#prometheus)
-  - [Edit YML Configuration File](#edit-yml-configuration-file)
-  - [Configuring Prometheus as a Service](#configuring-prometheus-as-a-service)
-  - [SSH Port Forwarding](#ssh-port-forwarding)
-  - [Dynamic SSH Forwarding (SOCKS Proxy)](#dynamic-ssh-forwarding-socks-proxy)
-    - [Configuring Your Browser](#configuring-your-browser)
-  - [X11 Forwarding](#x11-forwarding)
-- [Grafana](#grafana)
-  - [Configuring Grafana Dashboards](#configuring-grafana-dashboards)
-- [Node Exporter](#node-exporter)
-  - [Configuring Node Exporter as a Service](#configuring-node-exporter-as-a-service)
-- [Slurm Scheduler and Workload Manager](#slurm-scheduler-and-workload-manager)
-  - [Prerequisites](#prerequisites)
-  - [Head Node Configuration (Server)](#head-node-configuration-server)
-  - [Compute Node Configuration (Clients)](#compute-node-configuration-clients)
-  - [Configure Grafana Dashboard for Slurm](#configure-grafana-dashboard-for-slurm)
-- [Using Terraform to Automate the Deployment of your OpenStack Instances](#using-terraform-to-automate-the-deployment-of-your-openstack-instances)
-- [Using Ansisble to Automate the Configuration of your VMs](#using-ansisble-to-automate-the-configuration-of-your-vms)
-- [Introduction to Continuous Integration](#introduction-to-continuous-integration)
-  - [GitHub](#github)
-  - [TravisCI](#travisci)
-  - [CircleCI](#circleci)
-- [GROMACS Protein Visualisation](#gromacs-protein-visualisation)
-- [Running Qiskit from a Remote Jupyter Notebook Server](#running-qiskit-from-a-remote-jupyter-notebook-server)
+1. [Checklist](#checklist)
+    1. [(Delete) - Remote Web Service Access](#delete---remote-web-service-access)
+1. [Prometheus](#prometheus)
+    1. [Edit YML Configuration File](#edit-yml-configuration-file)
+    1. [Configuring Prometheus as a Service](#configuring-prometheus-as-a-service)
+    1. [SSH Port Forwarding](#ssh-port-forwarding)
+    1. [Dynamic SSH Forwarding (SOCKS Proxy)](#dynamic-ssh-forwarding-socks-proxy)
+        1. [Configuring Your Browser](#configuring-your-browser)
+    1. [X11 Forwarding](#x11-forwarding)
+1. [Grafana](#grafana)
+    1. [Configuring Grafana Dashboards](#configuring-grafana-dashboards)
+1. [Node Exporter](#node-exporter)
+    1. [Configuring Node Exporter as a Service](#configuring-node-exporter-as-a-service)
+1. [Slurm Scheduler and Workload Manager](#slurm-scheduler-and-workload-manager)
+    1. [Prerequisites](#prerequisites)
+    1. [Head Node Configuration (Server)](#head-node-configuration-server)
+    1. [Compute Node Configuration (Clients)](#compute-node-configuration-clients)
+    1. [Configure Grafana Dashboard for Slurm](#configure-grafana-dashboard-for-slurm)
+1. [GROMACS Protein Visualisation](#gromacs-protein-visualisation)
+1. [Running Qiskit from a Remote Jupyter Notebook Server](#running-qiskit-from-a-remote-jupyter-notebook-server)
+1. [Automating the Deployment of your OpenStack Instances Using Terraform](#automating-the-deployment-of-your-openstack-instances-using-terraform)
+1. [Automating the Configuration of your VMs Using Ansisble](#automating-the-configuration-of-your-vms-using-ansible)
+1. [Introduction to Continuous Integration](#introduction-to-continuous-integration)
+    1. [GitHub](#github)
+    1. [TravisCI](#travisci)
+    1. [CircleCI](#circleci)
 
 <!-- markdown-toc end -->
 
@@ -378,15 +376,6 @@ To confirm that your node configuration is correct, you can run the following co
 The `S:C:T` column means "sockets, cores, threads" and your numbers for your compute node should match the settings that you made in the `slurm.conf` file.
 ## Configure Grafana Dashboard for Slurm
 
-# Using Terraform to Automate the Deployment of your OpenStack Instances
-
-# Using Ansisble to Automate the Configuration of your VMs
-
-# Introduction to Continuous Integration
-## GitHub
-## TravisCI
-## CircleCI
-
 # GROMACS Protein Visualisation
 
 > **! >>> You will need to work on your personal computer (or laptop) to complete this section.**
@@ -424,3 +413,15 @@ Simulations like this are used to to develop and prototype experimental pharmace
 </span>
 
 # Running Qiskit from a Remote Jupyter Notebook Server
+
+
+# Automating the Deployment of your OpenStack Instances Using Terraform
+
+## 
+
+# Automating the Configuration of your VMs Using Ansible
+
+# Introduction to Continuous Integration
+## GitHub
+## TravisCI
+## CircleCI