changes to Tutorial1&2

Author: ZamaZethu

.gitignore

@@ -1 +1,2 @@
-*~
+*~
+.DS_Store

tutorial1/README.md

@@ -523,7 +523,7 @@ If your workstation or laptop is running Windows, then you may proceed using eit
 
 ### Username and Password
 
-Once you've successfully logged into your head node VM, you are encouraged to change your password so that you may access your head node through the OpenStack VNC console interface.
+Once you've successfully logged into your head node VM, you are encouraged to setup your password login as a fail safe incase your ssh keys are giving issue, you may also access your head node through the OpenStack VNC console interface.
 
 ```bash
    sudo passwd <username>
@@ -539,10 +539,75 @@ Once logged into your head node, you can now make use of the [previously discuss
 
 <p align="center"><img alt="Verifying head node basic networking configuration." src="./resources/head_node_basic_networking_commands.png" width=900 /></p>
 
-## Manual Pages `man`, Reading Documents `cat` and the `-h` Switch
-## Piping `|` Through `grep`, `more` or `less`
-## Redirecting `>>` Console Output to a File
+## Manual Pages `man`
+In linux every information about all linux commands is found in a linux built in manual page document. This doncument is accessible via a command called `man` short term for manual page. Run the ff commands to understand what each command mean, scroll up and down then press `q` to exit the page, these are some of the commands you will use throught the week. 
+
+```bash
+   man sudo
+   man ping 
+   man tracepath
+   man ls 
+   man cat 
+   
+```
+<p align="center"><img alt="manual page for `sudo` command" src="./resources/man_sudo_feedback.png" width=900 /></p>
+
+
+## the `-h` Switch
+If you don't want to use the `man` command to learn about each command and related options, you can use the `--help or -h` flag to see which options are available for a specific command. run the ff command to learn about available options each command has.
+
+```bash
+
+   sudo -h 
+   ifconfig -h 
+   ping -h 
+   ssh-keygen --help 
+   grep --help 
+   
+```
+
+<p align="center"><img alt="manual page for `sudo` command" src="./resources/sudo_with-h_flag.png" width=900 /></p>
+
+
+## Reading Documents
+you will be reading a lof of files throughout the week and the ff commands can be used to read files with ease, use `man` to learn about each command. All the following command are used to read the content of a file `staff_list.txt`
+
+```bash
+less staff_list.txt
+more staff_list.txt
+cat staff_list.txt
+vi staff_list.txt
+nana staff_list.txt
+
+   
+```
+
+<p align="center"><img alt="cat prints the content of file on screen" src="./resources/cat_command.png" width=900 /></p>
+
+<p align="center"><img alt="read the content of the file with `less` command " src="./resources/less_command.png" width=900 /></p>
+
+## Piping 
+
+`|` Through `grep` is used when searching the content of the file, if it exist it will be printed on the screen, if the search does not exist nothing will show on the screen.
+
+<p align="center"><img alt="search the file with `grep` command " src="./resources/search_commands_grep.png" width=400 /></p>
+
+## Console Output to a File
+
+`>`  replaces the content of an output file with all input content
+`>>` appends the input content to the end of the output file.
+
+<p align="center"><img alt="appends james at the endo of staff_list.txt file" src="./resources/append.png" width=900 /></p>
+
+<p align="center"><img alt="replaces the content of staff_list.txt file with james"  src="./resources/replaces.png" width=900 /></p>
+
 ## GNU `history` Library
+`history` command shows all commands you have executed so far, the feedback is numbered, use `!14` to rerun the 20th command  
+ 
+ <p align="center"><img alt="history command "  src="./resources/history_command.png" width=900 /></p>
+ 
+ <p align="center"><img alt="rerun commands from history "  src="./resources/rerun_command_from_history.png" width=900 /></p>
+
 ## Brief Introduction to Text Editors (Vi vs Vim vs Nano)
 ### Your First Chat GPT Query
 

tutorial1/resources/append.png

@@ -93,9 +93,12 @@ This tutorial will demonstrate how to access web services that are on your virtu
 
 # Spinning Up a Compute Node in OpenStack
 
-play around
 
-scripting and automation to test out differnet configurations
+# Manually from openstack dashboard 
+To launch your compute node vm, go to `Compute-> Instances` click `launch instance` and follow the headnode vm launch process on Tutorial 1. **remember** to use `compute` flavors and `local_team_keys`  used when launching the headnode on Tutorial 1.
+
+
+# scripting and automation to test out differnet configurations
 
 As previously discussed in [Tutorial 1: OpenStack Flavors](../tutorial1/README.md#openstack-instance-flavors), an important aspect of system administration is resource monitoring, management and utilization. Once you have successfully stood up your head node, your team will need to plan and manage the resources remaining which will be available for your compute node(s).
 
@@ -112,7 +115,7 @@ Sensible default instance flavors have already been identified and configured fo
 
 One important distinction between your head node and compute node(s), is that the compute nodes will **not** have a floating IP associated to them. Your head node will act as a ***Gateway*** for your Compute Node(s), and ***Route*** traffic between the internet and your cluster, using a method referred to as ***Network Address Translation (NAT)***, which was discussed in the [WiFi Hotspot Example](../tutorial1/README.md#wifi-hotspot-example).
 
-The final important consideration that must be made for your compute node is that you must not forget to configure an SSH key, so that you may access it after it has successfully launched. For ease of access and to simplify your configuration, you are *strongly* advised to use the same SSH key that you'd [previously generated](../tutorial1/README.md#generating-ssh-keys).
+The final important consideration that must be made for your compute node is that you must not forget to configure an SSH key, so that you may access it after it has successfully launched. For ease of access and to simplify your configuration, you are *strongly* advised to use the same SSH key that you'd [previously generated](../tutorial1/README.md#generating-ssh-keys) on your local machine/laptop.
 
 # Accessing Your Compute Node
 
@@ -128,7 +131,7 @@ TODO: High level explanation of OpenStack's automatic network configuration and
 
 TODO: Maybe remove the default routing table on compute node and route through headnode?
 
-## Command Line Proxy Jump Directive
+## Command Line Proxy Jump Directive 
 
 From you workstation, using either MobaXTerm or Windows Powershell, you can `ssh` directly into your compute node by first making an **ssh** connection too your head node and then establishing a TCP forwarding connection to your compute node. Using this method, the SSH keys for both your head node and compute node must reside on your local workstation:
 
@@ -207,8 +210,11 @@ Just as you did so in the previous tutorial when you generated SSH keys [on your
 
 # Understanding the Roles of the Head Node and Compute Node
 Networking Diagram and client server model
+headnode (hd) and compute node (cn) relationship follow a server (hd) - client (cn) relations, the headnode carries the systems services and compute node does all the computations
 System software need to be installed on both head node and compute nodes
-Do not ssh endlessly between head and compute nodes, one terminal example or multiplexing
+Do not ssh endlessly between head and compute nodes, one terminal example or multiplexing (screen sessions via `tmux`)
+
+
 ## Terminal Multiplexers
 
 Discuss GNU Screen and [tmux](https://github.com/tmux/tmux/wiki)
@@ -256,7 +262,7 @@ sudo apt-get install tmux
 To start a new `tmux` session on your **head node**:
 
 ```bash
-tmux
+tmux new -s session_name 
 ```
 
 ### Working on your Head Node and Compute Node in Two Adjacent Panes
@@ -333,18 +339,169 @@ Should your terminal application close, or if you relocate from the laboratores.
 To connect to an existing `tmux` session on your **head node**:
 
 ```bash
-tmux attach
+tmux a -t session_name 
+```
+
+
+## Basic Linux commands   
+
+# Basic System Monitoring  
+`top` `htop` are system built commands used to monitor server resource suage. for `htop` first install epel source repository then install htop 
+https://docs.rockylinux.org/gemstones/htop/ 
+
+```bash
+sudo dnf -y install epel-release
+sudo dnf makecache
+sudo dnf -y install htop
+htop 
+
+```
+
+<p align="center"><img alt="htop output" src="./resources/htopcommand.png" width=900 /></p>
+
+
+
+# Print current working space 
+If you are lost and don't know where you currently working use `pwd` (print working directory), it will show you your current woring space 
+
+```bash
+pwd 
+```
+
+
+## Manipulating Files and Directories
+
+# Make a New Directory 
+
+`mkdir` command is used to create folders or directories, the `-p` flag means create the directory path `mnu/2024` if it does not exits before creating `SCC` directory. 
+
+```bash
+mkdir SCC
+mkdir -p mnu/2024/SCC
+```
+
+
+
+# creating new Files 
+The following commands are used to create and edit files 
+`touch` create a new file(s) 
+
+`vi, vim, nano ` file editor commands and are used to edit existing files, but if a file does not exist it will create the file and open it for editing. 
+
+
+```bash
+touch file
+
+vi file1
+```
+
+
+
+# List Directory 
+`ls` (list) command used to list the content of directory/folder.
+
+```bash
+ls 
+
+ls mnu/2024/SCC
+```
+
+`ls` list or prints the content of the current directory 
+`ls mnu/2024/SCC`  list or print the content of the last `SCC` directory 
+
+
+
+# Change Directory 
+
+`cd` commad allow you move from directory to directory 
+
+```bash
+
+cd mnu/2024/SCC
+
+```
+
+`cd mnu/2024/SCC` means moving to `SCC`  directory, you can verify your current working directory by `pwd` command 
+
+ <p align="center"><img alt="change from current to SCC directory" src="./resources/cdexample.png" width=700 /></p>
+
+
+
+
+# Copy File or Directory 
+
+`cp` copy files/directories from source to destinations, it works like windows `copy and paste`. 
+
+```bash
+mkdir -p mnu/2024/team
+cp -r mnu/2024/SCC mnu/2024/team/
+
+```
+
+`mkdir -p mnu/2024/team` creates a team directory/folder under mnu/2024 directoy path
+`cp -r mnu/2024/SCC mnu/2024/team/` will recursilvely copy the `SCC` directory and it content to `mnu/2024/team/` directory. 
+
+ <p align="center"><img alt="creating the SCC directory" src="./resources/cpexamble.png" width=700 /></p>
+
+
+
+
+# Move File or Directory 
+
+`mv` command literally moves files/directories from source to destinations, it work like windows `cut and paste`. 
+
+
+```bash
+mv staff_list.txt mnu/2024/team/SCC
+
+```
+
+`staff_list.txt` file is being moved to SCC directory 
+
+ <p align="center"><img alt="moving staff list file to SCC directory" src="./resources/mvcommandexample.png" width=700 /></p>
+
+
+
+
+# Remove File or Directory 
+
+`rm` remove command used to delete files, directory with `-r` flag
+
+```bash
+rm  mnu/2024/team/SCC/staff_list.txt
+rm -r mnu/2024/team/SCC
+
+```
+
+<p align="center"><img alt="moving staff list file to SCC directory" src="./resources/rmcommand.png" width=700 /></p>
+<p align="center"><img alt="moving staff list file to SCC directory" src="./resources/rmcommandexample.png" width=700 /></p>
+
+
+
+
+# The history Command
+
+`history` command shows all commands you have executed so far, the feedback is numbered, use `!14` to rerun the 20th command  
+ 
+ <p align="center"><img alt="history command "  src="./resources/history_command.png" width=900 /></p>
+ <p align="center"><img alt="rerun commands from history "  src="./resources/rerun_command_from_history.png" width=900 /></p>
+
+
+
+
+# The virtual environment Command 
+
+`virtualenv` command helps you run multiple services with conflicting packages without any problems. each virtual enviroment is treated as an independant entity. 
+Below is how you create and source or access a virtual enviroment then deactivate to exit, ensure to use sensible names.
+https://www.digitalocean.com/community/tutorials/how-to-install-python-3-and-set-up-a-programming-environment-on-rocky-linux-9 
+
+```bash
+python -m venv env
+source env/bin/activate
+deactivate 
+
 ```
 
-## Basic System Monitoring 
-# Manipulating Files and Directories
-## List Directory `ls`
-## Change Directory `cd`
-## Copy File or Directory `cp`
-## Move File or Directory `mv`
-## Make a New Directory `mkdir`
-## Remove File or Directory `rm`
-## The `history` Command
 ## Recommended Project Folder Structure
 # Verifying Networking Setup