OPS235 Lab 2 - CentOS7 - VMware

LAB PREPARATION

Purpose / Objectives of Lab2

At the end of lab2, your VMware Workstation application will contain 4 virtual machines. You will now have the option to run one virtual machine at a time, or run all machines simultaneously to learn about networking (covered in later labs)

In this lab, you will create another three virtual machines to learn how to install Centos Linux in different ways including network installs.

Main Objectives

• Create 3 separate VMs (virtual machines) using different installation methods:

• Centos Live DVD (with Install to Harddisk program)
• Network Centos Installation without configuration file
• Network Centos Installation with configuration file (Kickstart)

• Understand the advantages and disadvantages of each type of installation, and be able to select the best installation method for a particular situation.
• Create and run Bash Shell scripts to automatically create a post-install report for an installed VM.

Minimum Required Materials

USB key (for backups)

Lab2 Log Book

My Toolkit (CLI Reference)

Package Management rpm yum

System Information hostname uname ps lsblk

Networking ifconfig netstat route nslookup

Misc Commands gzip, gunzip grep wc pwd ls more file wget chmod vi

Online Linux Command Review The following tutorial will allow you to learn essential shell scripting skills. Login to your Matrix account, and issue the pathname to run the online tutorial in Matrix: Shell Scripting - Part I (Scripting Basics): /home/murray.saul/scripting-1 Shell Scripting - Part 2 (Logic & Math Expressions): /home/murray.saul/scripting-2 Shell Scripting - Part 3 (Loops) /home/murray.saul/scripting-3

INVESTIGATION 1:CREATE OTHER VIRTUAL MACHINES (INSTALL COMPARISON)

Virtualization Application Setup / Comparison Chart

Record VM Installation in Lab2 (Installation Comparison Chart):

You will be learning to perform several different type of CENTOS Linux installs. Lab2 has a comparison chart for comparing various Linux installs. You were required in lab1 to record your observation for your centos1 installation.

As you proceed throughout this lab, you will be required to fill in the comparison chart for the remaining 3 virtual machines that you will be installing.

Part 1: Installing from a Downloaded Image (Centos7 LIVE CD)

Perform Downloads and Network installs at Seneca It is recommended to perform this lab in one of Seneca College's labs. This lab uses servers which are on the Seneca network and which are not available from other locations (such as your home). If you attempt this lab from another location, adjust the belmont.senecac.on.ca URLs to point to another mirror server -- note that you may need to change the directory name as well as the server name. The installation of the centos4 virtual machine must be done at Seneca.

VM Details:

VM Name (and hostname): centos2

Boot media: LIVE CD Image (downloaded iso file)

Installation source: Downloaded Centos7 LIVE CD image (http://belmont.senecac.on.ca/centos/7/isos/x86_64/CentOS-7-x86_64-LiveGNOME-1511.iso)

VM Image Pathname: /var/lib/libvirt/images/centos2.img

Memory: 2GB

Disk space: 10GB

File System (root partition): ext4

CPUs: 1

You do not need to burn a DVD for the Centos7 install image. You can simply download an image file (.iso), and refer to this downloaded image in order to install the Linux OS. This is the second method of installation that we will now investigate.

1. Open a web-browser, click on the link below to save on your Windows machine in your Seneca Lab (Downloads section).
   
   http://belmont.senecac.on.ca/centos/7/isos/x86_64/CentOS-7-x86_64-LiveGNOME-1511.iso
   
   
2. Launch the VMWare Workstation application.
3. Click on the icon to Create a New Virtual Machine and select Custom (Advanced).

When your centos2 LIVE machine boots-up, immediately double-click on the Install to Hard Disk icon to run the installation program.

4. The virtual machine will now start.
5. Immediately double-click on the icon called Install to Hard Disk.
6. Start timing your installation and making notes for centos2 virtual machine in the installation comparison chart in lab2 logbook.
7. Select your downloaded iso Centos7 Gnome LIVE image (under Downloads folder) and click Next. Basically, you perform the same steps is in lab1 (i.e. select Custom (Advanced) with 2 GB of RAM, the VM name will be called centos2 and the Hard Disk size will be 10 GB (not 20GB).
8. When your VM boots-up, Double-click Install to Hard Drive. The installation program, similar to the one used when installing CentOS in Lab 1, will appear. You basically perform the same installation operations for this VM including for Date & Time, Network & Hostname, and Installation Destination. Make certain to use the hostname: centos1 as opposed to c7host) for this installation. (with a few slight differences).
9. For Installation Destination, select the destination option: I will configure partitioning and then click Done. Make certain that the Partition Scheme is set to LVM and then click on the link: Click to Create Automatically. Done. Check to make certain that the root partition has file system type: ext4.
10. Accept the changes and then click Begin Installation.
    1. You will be required to make selections very similar to what you did in lab1.
    2. While the system is installing, take a few minutes to record your observations (including slight differences with centos1 install as opposed to c7host install).
    3. When the installation process is complete, note the time required to install this system and record in the installation comparison chart of your lab2 logbook.
       
       
11. Power-off your Centos7 LIVE system.
12. Restart your centos2 VM, and enter 1, 2, c, c, like you did in lab1.
13. Finish the final steps in the setup process (like you did in lab1).
14. It is recommended that you turn off the screen-saver (like you did in Lab1: Turn-off Screen Saver Lock).

Important Network Service Tasks Please perform the tasks below in order allow these CentOS systems to be able to communicate with each other. Failure to properly perform these operations can cause problems in future labs.

20. Make certain to disable SELinux for centos2 (refer to lab1)
21. Start and enable the SSH server to allow access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):
    systemctl start sshd; systemctl enable sshd
22. Find out the IP address of your virtual machine and the name of your Ethernet network adaptor: ifconfig
23. Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine:
    iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT
24. If you are logged in as root, logout to your regular user account.
25. Confirm that you can ssh to your virtual machine from the host (your main CentOS installation): ssh regularuserid@IPaddress (where regularuserid is your regular user login id, and IPaddress is the IP_ADDRESS of your centos2 VM!).

Remember to Backup your VM to USB Key!
Remember that you need to backup your centos2 VM to your USB key before you leave your Seneca lab, or you will lose your work!

Part 2: Installing from a Network

Authenticate to the network The rest of this lab uses network access. Be sure to authenticate to the network using your browser before proceeding.

VM Details:

VM Name (and hostname): centos3

Boot media: Network installation

Installation source URL: http://belmont.senecac.on.ca/centos/7/os/x86_64/

VM Image Pathname: /var/lib/libvirt/images/centos3.img

Memory: 2048MB

Disk space: 20GB

CPUs: 1

1. Create the VM (called centos3) as you did with the centos1 machine, except for the following differences:
   
   
   1. Select Network Installation using the installation source URL displayed above.
   2. When customizing your partitions, do the same operation that you did in centos2, but after automatically creating the partitions, reduce the size of the root LVM partition to 8000 MB and add an LVM partition with a size of 2000 MB (mount point: /home, name: home, and make certain root and /home partitions have ext4 file system).
   3. Don't forget to install the GNOME desktop here as you will need a GUI for Centos3
      
      
2. Complete the installation. Login to your regular user account, and perform a yum update for the centos3 VM (reboot if required). Make certain to adjust your screen-saver settings if desired.
3. Repeat the steps as you did to start the SSH service, set iptables to accept connections via ssh, test connections between centos3 and centos1, and disable SELinux (refer to lab1).
4. Record the time taken to install, and compare this to the time taken by the previous installations. Record your findings in the Installation Comparison chart in lab2 logbook.

Remember to Backup your VM to USB Key!
Remember that you need to backup your centos3 VM to your USB key before you leave your Seneca lab, or you will lose your work!

Part 3: Installing from a Network using a Kickstart File

VM Details:

VM Name (and hostname): centos4

Boot media: Network installation

Installation source URL: http://belmont.senecac.on.ca/centos/7/os/x86_64/

Kickstart File URL: http://matrix.senecac.on.ca/~andrew.smith/ops235/centos7-kickstart-v01.cfg

VM Image Pathname: /var/lib/libvirt/images/centos4.img

Memory: 2048MB

Disk space: 15GB

CPUs: 1

1. Create the VM as you did with the centos3 virtual machine, specifying a network install as before, but specify the kickstart location under the "options section" for network install. What do you think is the purpose of this kickstart file?
2. Observe the installation. How is it different from booting from a downloaded image?
3. Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations.
   
   If the during the installation, you see the message at the bottom Pane is Dead, click the Virtual Machine menu at the top, select Shut Down -> Force Off, right-click on centos4 in the virtual manager window and select Delete. Redo the VM setup for a new instance of the centos4 VM.
4. What happens when the installation is finished?
5. Take a look at the kickstart file (eg. view url in a webj-browser) to determine the root password as well as the name and password for the first user account!
6. Boot the virtual machine and log in (use the user ID and password information from the previous step). Compare the experience to the first time you booted the other virtual machines. Record this information in the table contained in Investigation 4.
7. Repeat the steps as you did to start the SSH service, set iptables to accept connections via ssh, test connections between centos4 and centos1, and disable SELinux (refer to lab1).
8. Remember that centos4 is text-based interface only (no graphics). To recover from a blank screen, press a key (like the SPACE key) to return to the screen display.
9. Record the time taken to install, and compare this to the time taken by the previous installations. Record your findings in the Installation Comparison chart in lab2 logbook.

Answer the Investigation 1 observations / questions in your lab log book.

Remember to Backup your VM to USB Key!
Remember that you need to backup your centos3 VM to your USB key before you leave your Seneca lab, or you will lose your work!

INVESTIGATION 2: COMMON POST-INSTALL TASKS

Part 1: Perform Software Updates

Allow Time to Perform Yum Updates Allow sufficient time in order to perform updates prior to the end of the lab. Since you will be updating ALL of your VMs, allow 15-20 "lead-time" to start your updates and to backup your VMs prior to the end of the lab. NEVER force a shut-down of your VM while updates are running, since this will ruin your VM, and you will have to restore from a backup, or redo your labs for that VM!

It is important as a Linux System Administrator to update software on your Linux system periodically. Performing periodic updates will fix software bugs and inefficiencies as well as apply security patches in order to better secure your Linux server.

You are required to perform the following command for ALL of your 4 VMs:

yum update

This will download and install all of the packages that have been updated since the installation DVD image was created. If you complete this command at Seneca, it should run quite fast as Seneca College hosts a CentOS Repository mirror (a copy of all of the current CentOS packages, on a local web server). You will be reminded at the end of each of the remaining labs to perform software updates on ALL of your VMs.

Part 2: Accessing Administrative Priviledges

Accessing the Administration Account (root) Many administrative tasks require the root administrative account. There are many ways to access this administration account: Login: root (enter root password) Switch User to root (without login): su: Remains in regular user's directory, does not run root's startup script(s). su - : Changes to root's home directory (/root) and runs root's start script(s).

Navigate through your Graphical CentOS system, locate and run a terminal program (in order to issue Linux commands).

Issue and record the commands used and the output generated in each of the following steps:

1. With older (ancient) versions of Linux, a user once may have been allowed to login to their graphical Linux system using root as their user-name and their root password. This has been determined to be a security risk and that option has been removed with many or all Linux operating systems.
2. Therefore, from this point onwards, you will be logging into your regular user account instead and issuing a command to login as the root user.
3. Refer to the Information box regarding how to access the admin account from the command line.
4. Issue the command su Issue the pwd and whoami commands to confirm your directory pathname. When finished logout of this account.
5. Issue the command su - Issue the pwd and whoami commands to confirm your directory pathname. What do you notice are the main differences between using su versus using su - ?
6. An installation log file called /var/log/anaconda/packaging.log has been created to record the installation of your centos1 machine. This file is an ASCII file which can be viewed with the more command.
7. You can make use of this file to determine how many packages have been installed: complete the following command to count the number of packages that are labelled "Installing" in the installation log file:

grep -i packaging /var/log/anaconda/packaging.log | wc -l

Part 3: Common Post-Install Commands & Shell Scripting

Bash Shell Scripting Reference Guide: She-bang Line Forces shell script to run in a specific Shell Some shell syntax not backward compatible #! must be at beginning of first line of shell script Example: #!/bin/bash Variables Environment System-wide or "global" variable Usually appear in UPPERCASE letters Can view with command: set | more $ in front to expand variable to value Examples: USER, PATH, HOME, SHELL User-defined Variable created by user (command line, scripting) Examples: myVar="my value"; readonly myVar; export myVar read -p "enter value: " myVar Positional parameters Assign values with set command or shell script arguments These variables are numbered (eg. $1, $2 ... $10} Special parameters: $*, $@, $#, $$, $? Command Substitution Useful method to expand output from a command to be used as an argument for another command. Examples: file $(ls) set $(ls);echo $#;echo $* echo "hostname: $(hostname)" Logic Control Flow Statements $? variable true (0) if command runs; otherwise is false (non-zero) Example: if echo $myVar | grep "match" then echo "Match" fi The test command is used to test conditions. Square brackets [ ] is short-cut for test command (args contained inside with spaces). The exit command can be used to terminate the shell script with a false value. Example: if [ $USER = "root" ] then  echo "You must be root"  exit1 fi For numberic comparison, use the following test options: -gt,-ge, -lt, -le, -eq, -ne Examples: if test $age -gt 65 then  echo "retire" else  echo "don't retire" fi if [ $grade -gt 79 ] then  echo "You get Good Mark" elif [ $grade -gt 49 ] then  echo "You pass" else  echo "You fail" fi For testing for file information, you can use -d to test if directory pathname exists, and -f if the file pathname exists. You can use ! for negation. Examples: if [ -d directory-pathname ] then echo "directory exists" fi if [ ! - f file-pathname ] then echo "File does not exist" fi Loops (iteration): Loops and logic are a very important elements of shell scripting (not to mention programming as well). Determinant loops (such as for loops) usually repeat for a preset number of times (eg. counts, positional parameters stored). In-determinant loops (such as while or until loops) may repeat based on unknown conditions (like waiting for user to enter correct data). Test conditions can be used with in-determinant loops, or even commands! If a command runs successfully (eg ls, cd, grep matching a pattern), zero (true) value is returned, otherwise a non-zero (false) value is returned. Command options or redirection to /dev/null can be used to just test if command runs, but not display stdout or stderr. Conditional statements "and" (&&) / "or" (||) can also be used when testing multiple conditions. Examples (try in a shell script) set ops235 is fun for x do  echo "argument is $x" done for x in $(ls) do  echo "Filename: $x" done read -p "enter a whole number: " num until echo $num | grep -q "^[0-9][0-9]*$" do  read -p "Incorrect. Please enter WHOLE NUMBER: " num done read -p "pick a number between 1 and 10: " num while [ $num -lt 1 ] || [ $num -gt 10 ] do  read -p "Incorrect. Please pick number between 1 and 10: " num done

It is very common for System Administrators to keep records regarding their installed computer systems. For example, it is necessary to have a record of all the hardware information for each machine in order to help fix computer hardware problems, and to assist when purchasing additional consistent computer hardware.

Therefore, it makes sense to also have a record of the installed computer software as well. This can contain information regarding the Linux operating system, installed software, and network connectivity information.

Perform the Following Steps:

1. Study the Linux commands and their purpose to note computer software information for your installed centos1 VM. You should take time to issue each of these commands to view the output, and record this chart in your lab1 logbook.
   
   
2. Login to your centos1 VM, open a Bash Shell terminal, and login as root by issuing the command:
   su -
   
   
3. Make certain to record output from these commands (except for the ps -ef output) in your lab1 logbook.

Command(s)	Purpose
uname -rv hostname ps -ef	Basic Linux OS information such as kernel version, host-name of Linux server, and all processes that are running on the system after installation.
rpm -q -a | wc -l rpm -q -a -l | wc -l rpm -q -l gedit | wc -l	Obtain number of installed packages in the rpm database. Option -q is to "query" informationo, option -a means for all installed packages, option -l means all files installed as opposed to just the application.
ifconfig route -n nslookup	Obtain network connectivity confirmation including: IP ADDRESS, Netmask, routing (default gateway), and the default Domain Name Server.

You may have learned about creating and running Bash Shell Scripts in your ULI101 course. Shell scripts help Linux users and system administrators to automate repetitive tasks to become more efficient and to help them save time. You will be reviewing and building a basic Bash Shell script to generate information reports for your newly-installed Linux host machine.

4. Refer to the Bash Shell Scripting Guide prior to proceeding with this section. As you continue, you are required to make Bash Shell scripting notes in your lab1 logbook.
5. Create a directory called bin in your root home directory to store your shell scripts by issuing the command:
   mkdir ~/bin
6. Change to that newly-created bin directory

NOTE: Although it is possible to copy and paste, is it highly recommended to manually enter the following Bash Shell scripting content to become familiar with writing Bash Shell scripting code. Remember: you will be required to create a Bash Shell script on your final exam, so you need the practice!

7. Launch a text editor (such as vi or nano) to create a Bash Shell script called: myreport.bash in your current directory.
8. Copy and paste the text below into your vi editing session for your file report.bash
   (how do you copy and paste efficiently in Linux?)
   


#!/bin/bash

# Author: *** INSERT YOUR NAME ***
# Date: *** CURRENT DATE ***
#
# Purpose: Creates system info report
#
# USAGE: ./myreport.bash

if [ $USER != "root" ] # only runs if logged in as root
then
 echo "You must be logged in as root." >&2
 exit 1
fi


9. Save your editing session, assign the myreport.bash file read and execute permissions (at least for the owner) and run by typing:
   ./myreport.bash
10. Did it run? If not what do you think you need to do in order to run the Bash Shell Script?
11. Issue the command su - and run the script from the regular user's home directory (not root's home directory):
    ~regularuserid/myreport.bash
12. Did it work?
13. Reopen your text-editing session for ~regularuserid/myreport.bash and add the following lines of code to the bottom of the shell script file:

# Create report title

echo "SYSTEM REPORT" > /root/report.txt
echo "Date: $(date +'%A %B %d, %Y (%H:%M:%p)')" >> /root/report.txt
echo >> /root/report.txt


8. Save and run the bash shell script. View the contents of the file called report.txt that was generated (I hope you are using the up arrow key to issue previously issued commands in order to save time!). Notice how the redirection symbol > is used at the beginning of the report, and then the other redirection symbol >> is used to help "grow" the report with the other content.
9. The only remaining content of the report would be the system information. We can use a shell scripting trick called "command substitution" $( .. ) in order place results from an command to be used by another command (like echo). Re-edit the shell script and add the following code at the bottom of the shell script file:

echo >> /root/report.txt
echo "Hostname: $(hostname)" >> /root/report.txt
echo >> /root/report.txt
echo "Kernel Version: $(uname -rv)" >> /root/report.txt
echo >> /root/report.txt


10. Save, run the script, and view the report.txt contents (are you using tip that was given to save time?).
11. Edit the shell script and include output from the ps aux and ifconfig commands (with appropriate titles). Remember to redirect that output to add to the bottom of the file!
12. Save, run and confirm that the shell script is working correctly.
13. What would be the use of keeping this shell script as a Linux system administrator?

14. Here are some more "complex" Bash Shell scripts, that perform the same task. Although you are not require to understand some of these other tricks, it is recommended that you view the contents of the scripts and save them for future consideration or exmaples.
15. The wget command can be used to quickly download files from the Internet. Issue the following command:
    wget https://scs.senecac.on.ca/~murray.saul/text-report.bash
16. Verify that the file text-report.bash was downloaded to your current directory.
17. Assign read and execute permissions for this file by issuing the command: chmod u+rx text-report.bash
18. Run this Bash Shell script by issuing the command: ./text-report.bash
19. Check to see if it created a report in your current directory. What is the purpose of the report?
20. Use the vi text editor to view the contents of the file text-report.bash. Can you understand how this script works?
    
    
21. Use the wget command to download, study, and run the following shell scripts on-line:

    https://scs.senecac.on.ca/~murray.saul/report.bash
https://scs.senecac.on.ca/~murray.saul/report3.bash

22. Try to understand what these Bash Shell scripts do.
23. You have completed lab1. Proceed to Completing The Lab, and follow the instructions for "lab sign-off".

Part 4: Manipulating VMWare Virtual Machines with vmrun Command

Regardless of your host operating system, you can use the vmrun command to manipulate your VMs.

Perform the following Steps:

1. Determine which operating system is the host for your VMware Workstation application. Use the chart below to setup your OS's environment to run the vmrun command:

Operating System	Set-up Steps
Linux	Edit the file /etc/ld.so.conffile and add the following line: /usr/lib/vmware-vix and then run the command: ldconfig.
Windows	Right-click on Computer, then select Properties , AdvancedSystemSettings , EnvironmentVariables, SystemVariables, Path, Edit and select the path below based on architecture: 32-bit: C:\Program Files\VMware\VMware VIX 64-bit: C:\Program Files (x86)\VMware\VMware VIX.
Mac OS/X	In a Terminal window, issue the following command to add the directory pathname to your system path: export PATH="$PATH:/Applications/VMware\ Fusion.app/Contents/

2. The vmrun command is run with various arguments. The most common are: stop, start, reset, suspend, pause, list, and clone. This command is run with basically the same syntax regardless of the operating system that you are running.
   
   
3. Shut-down all of your VMs.
4. Issue the following command:
   vmrun start path-to-centos1.vmx. What happens?
5. Use the vmrun command to start the other VMs.
6. Issue the following command:
   vmrun start path-to-centos4.vmx. What happens?
7. Issue the following command:vmrun list path-to-centos1.vmx. What happens? Why would you use this command?
8. Depending of your Operating system platform (Linux Bash Shell script, Windows Powershell script), download the following scripts in the table below to your current directory and run to see what happens. Notice how the for loop is used to in order to start and stop multiple VMs.

Operating System	Various Start / Stop Scripts
Linux	start-vm-cli.bash | start-vm-gui.bash | stop-vm-cli.bash | stop-vm-gui.bash
Windows	start-vms-cli | start-vms-gui | stop-vms-cli | stop-vms-gui
Mac OS/X	start-vms-cli | start-vms-gui | stop-vms-cli | stop-vms-gui

9. Notice that regardless of the operating system, that scripting is an essential tool for system administrators to control a computer system!

Answer Investigation 2 observations (all parts and questions) in your lab log book.

LAB 2 SIGN-OFF (SHOW INSTRUCTOR)

Backup ALL of your VMs!
If you have successfully completed this lab, make a new backup of all of your virtual machines onto your UBS Key.

Download and Run Lab2 Checking Script & Show Lab2 Work

Perform the Following Steps:

1. Make certain ALL of your VMs are running.
2. Switch to your centos2 VM, open a terminal, login as root, and change directory to /root/bin.
3. Issue the Linux command: wget http://matrix.senecac.on.ca/~murray.saul/ops235/lab2-check.bash
4. Give the lab2-check.bash file execute permissions (for the file owner).
5. Run the shell script and if any warnings, make fixes and re-run shell script until you receive "congratulations" message.
6. Arrange proof of the following on the screen:

✓ All VMs:

• All 4 VMs created and running
• Disk layout and size correct on ALL virtual machines
• Proof of yum updates on ALL VMs

✓centos2 VM:

• Creation of your bash shell script called myreport.bash
• A list of your iptables rules (command: iptables -L)
• Output from running the lab2-check.bash script with all OK messages

✓ Lab2 logbook notes and Installation Comparison chart completed.

Practice For Quizzes, Tests, Midterm & Final Exam

1. What is the name of the CentOS installation program?
2. What is the name of the file created by the CentOS installation program?
3. Which type of installation works best for confirming compatibility with hardware before installation? Why?
4. Which type of installation works best for installing large numbers of computers? Why?
5. How can you reduce the number of software updates required immediately after installation?
6. How do you start and stop virtual machines?
7. How do you SSH into your virtual machines?
8. List 2 ways that you can access your root account
9. What is the difference between the commands su and su -  ?
10. What is the home directory for the user "root"?
11. How do you determine the host name of your GNU/Linux workstation?
12. What command can display the NIC's MAC address?
13. What command is used to get a list of running processes on your newly-installed system?
14. How create in a shell script to force the user to run shell script as root?
15. How to store each file-name in your current directory as separate positional parameters? How to list all of the positional parameters? How to display the number of positional parameters?