OPS235 Lab 2 - CentOS7

LAB PREPARATION

Purpose / Objectives of Lab2

The c7host Linux server will run virtualization software to install and run 3 virtual machines (installed in lab2).

In this lab, you will create three virtual machines. This also gives you an opportunity to experiment with different ways of installing CentOS. You will be learning the following elements of Virtualization in this lab:

• Installing Virtualization Software on your c7host machine
• Create 3 separate VMs (virtual machines) using different installation methods:
  • Centos Live DVDInstallation
  • Network Installation without configuration file
  • Network 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.
• Manipulate virtual machines by CLI (virsh)
• Properly backup VMs and VM configuration in virtual manager application onto home directory and to external source (USB Key)
• Observe how Bash Shell Scripting can be used to automate routine tasks involving VM management

What is a Virtual Machine?

A virtual machine is a software simulation of a computer which can be used as though it were actual hardware. It's possible to run multiple virtual machines on one computer, reducing hardware requirements and introducing flexibility. Some common uses of virtualization include:

• Software testing -- Using multiple operating systems simultaneously on a single computer for testing and experimentation.
• Network simulation -- Testing network services, protocols, and security scenarios with a small number of computers.
• Isolation -- Protecting multiple sets of data by storing them on multiple virtual machines. If one of the virtual machines is compromised, the data on other virtual machines is still protected.
• Server consolidation -- Reducing the number of physical servers in a network by moving physical machines to virtual machines. This saves hardware, administration, cooling, and electricity costs, and it can increase the utilization of hardware (by ensuring that the hardware is not under-loaded).
• Load-balancing and disaster recovery -- It is possible to migrate virtual machines between different physical machines, to ensure that a workload is balanced across multiple computers, to allow routine hardware maintenance and upgrading, and to compensate for hardware failure or other disasters.

Minimum Required Materials

CentOS7 LIVE DVD

Removable Hard Disk Pack (SATA)

USB key (for backups)

Lab2 Log Book

My Toolkit (CLI Reference)

Virtualization: virt-manager virsh

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

Installation Guides Installing & Using KVM on CentOS Using KVM (tutorial) virsh command reference CentOS Kickstart Reference

Online Linux Command Review The following links will allow you to practice Linux commands that you learned from ULI101: Online vi Text Editor Tutorial: [ ]>/li> Bash Shell Scripting I: [ ]

INVESTIGATION 1: USING VIRTUALIZATION SOFTWARE TO CREATE VIRTUAL MACHINES

Virtualization Application Setup / Comparison Chart

comparison chart in lab2 logbook.

Record VM Installation in Lab2 (Installation Comparison Chart):

You will be learning to perform several different type of CENTOS Linux installs. Lab2 already has an empty table for comparing various Linux installs. You were required in lab1 to record your observation for your c7host installation.

As you proceed throughout this lab, you will be required to fill in the comparison chart for three of the VMs (virtual machines) that you will be installing.

Complete the following steps to install and run the virtual manager application:

1. Open a web-browser, and open the OPS235 Lab #2 WIKI.
2. Install the virtualization software by issuing the command:
   yum install qemu-kvm qemu-img virt-manager libvirt libvirt-python \
python-virtinst libvirt-client virt-install virt-viewer
   
   

This will install many applications (including):

• kvm/qemu - the hypervisor and other hardware emulation systems.
• A system service named libvirtd that manages the VMs.
• A graphical tool for managing virtual machines (virt-manager) and the virsh command-line tool.
  

3. Start the virtualization service: service libvirtd start
4. The firewall configuration is altered by the addition of the virtualization software. Restart the firewall so that these changes become active: service iptables restart

Run virt-manager as a regular user, not as root Otherwise all your virtual machines will be owned by root and you won't be able to use them as a regular user.

5. Start the graphical tool by selecting the menu options Applications>System Tools>Virtual Machine Manager or by typing the command virt-manager

Part 1: Installing from a Live Disc

VM Details:

Name: centos1

Boot media: CentOS7 Live DVD

Installation source: Live DVD

Memory: 768MB

Disk space: 10GB

CPUs: 1

Performing this Lab off the Seneca network (eg. at home) 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 centos3 virtual machine must be done at Seneca.

1. In the Virtual Machine Manger, click on the icon to Create a Virtual Machine in the upper-left corner:
2. A window will appear with the title New VM. There are five steps to be completed; click Forward after each step:
3. Step 1 of 5: Enter the virtual machine (called centos1) name and select Local install media
4. Step 2 of 5: Insert the DVD containing the Centos Live Disc image. Wait a moment for the disc to be recognized, then select Use CDROM or DVD as the install media. Set the OS type to Linux and the Version to Red Hat Enterprise Linux 7 (the CentOS6 equivalent).
5. Step 3 of 5: Set the memory to 768 MB and the number of CPUs to 1
6. Step 4 of 5: This next step creates a disk file that will be used to simulate the virtual machine's disk drive. Select a size of 10 GB and checkmark the box labeled Allocate entire disk now
7. Step 5 of 5: Review the options that you have selected. Make a note of the storage location. If anything needs to be changed, use the Back button to go back and edit it; otherwise, click Finish

Removing and Recreating VMs If for some reason the user wants to remove a Virtual Machine, they can right-click the VM, and select delete in the Virtual Machine Manager. It is recommended to "delete the image file" in the remove VM dialog box when removing and then recreating a VM. Note: If you fail to properly remove the VM image file, it may affect the hard disk size for the new VM (i.e. use the old smaller size. Make certain to remove that VM image file prior to recreating the VM.

8. The virtual machine will now start. The virtual machine is running from the live disc at this point, and no software has been installed on the hard drive of the virtual machine. The point of a live disk is to allow you to test the distribution to see whether you like it without installing to the harddrive first.

9. Click Install to Hard Drive. The installation program, similar to the one used when installing CentOS in Lab 1, will appear. You will get a warning at one point during the installation process that the disk "May contain data" or "may need to be re-initialized" -- this is simply a warning that the virtual disk is completely blank, and it is safe to proceed with the installation.
10. During the installation process, when prompted for a storage device, first select Specialized Storage Devices, and then select the Virtio Block Device option.
11. When prompted for the hostname, enter centos1, and when prompted for the timezone, select Toronto - Eastern Time Ontario
12. When asked about storage, select Use All Space. Use the default values for all other fields. Notice that the installer does not ask you what software should be installed; compare the installation time to the amount of time it took to do your Lab 2 installation. Record this information in the table contained in Investigation 4.
13. When the installation is complete, click on the reboot button at the bottom right-hand corner of the screen.

13. Start the VM from its disk image. This can be done graphically by selecting the Virual machine name, and then clicking on the Open button, and then click the play button when the next screen appears (or by selecting Virtual Machine>Run from the virtual machine menu). You will get the Firstboot configuration questions during the boot process (asking you to create a user, set the date and time, and ignore the kdump out-of-memory warning). Make certain that the VM has a network interface connection (i.e. look at network applet on the top panel). Create a user with the same name as your Matrix account.
14. Login using the new user account.

Network / Service Considerations 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.

15. Enable SSH access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):
    service sshd start; chkconfig sshd on
16. Find out the IP address of your virtual machine: ifconfig eth0
17. 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
18. Confirm that you can ssh to your virtual machine from the host (your main CentOS installation): ssh c7host_IPaddress (where c7host_IPaddress is the dotted-quad address of your c7host machine).

Virtual Machine Screen Size
The virtual machine screen size will change resolution as it switches from text to graphics mode. Use the VM menu option View>Resize to VM to resize the window to show the entire VM display. If this is larger than your screen size, use View>Scale Display>Always to scale the image so it fits on your screen.

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

Part 2: Installing from the Network

VM Details:

Name: centos2

Boot media: Network installation

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

Memory: 1024MB

Disk space: 20GB

CPUs: 1

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

1. Create the VM (called centos2) as you did with the centos1 virtual machine, except select network installation using the installation source url displayed above.
2. Observe the boot process. How is it different from booting from an optical disc (DVD)?
3. Start the installation process (make certain to use information in the VM Details section above).
4. When you get to the disk partitioning step, select Use All Space and enable the checkbox labelled Review and modify partition layout. If an dialog box displays a permissions problem, then click yes to proceed. On the next screen, change the logical volumes as follows:
   • Reduce the size of the root LV to 8000 MB.
   • Add a logical volume with a size of 2000 MB and a mountpoint of /home (you can name it whatever you want, and use ext4 as the file-system type).
5. On the software selection screen, select Desktop.
6. Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations.Record this information in the table contained in Investigation 4.

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

Part 3: Installing from the Network using Kickstart

VM Details:

Name: centos3

Boot media: Network installation

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

Kickstart location: http://matrix.senecac.on.ca/~andrew.smith/ops235/centos6-kickstart-v01.cfg

Memory: 1024MB

Disk space: 15GB

CPUs: 1

1. Create the VM as you did with the centos2 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 an optical disc?
3. Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations.
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.

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

Part 4: Updating the VMs

Never Shutdown Computer During Upgrade Your computer (host, vms) are at their most vulnerable when you perform an update. Always plan ahead for appropriate time prior to performing an update. Shutting down your computer while performing an update may cause your computer not to boot! You have been warned!!!

1. In each VM, run this command: yum update
2. Record the answers to these questions in your log book:
   • How long did it take to run on each VM? How many packages were updated?
   • Why does it take longer in some VMs than others?

INVESTIGATION 2: MANAGING VIRTUAL MACHINES

Part 1: Managing Virtual Machines from the Command Line

Manage virtual machines from the host The commands used to manage virtual machines must be executed on the host (your disk pack) and not inside a virtual machine.

1. Start the centos1 virtual machine, and stop the centos2 and centos3 virtual machines.
2. Switch to the c7host machine, and open a shell terminal.
3. Enter these commands into your c7host machine and note the result:

virsh list

virsh list --all

virsh list --inactive

Virtual Machine Does not Shutdown from Command If the Virtual machine fails to shutdown from the virsh shutdown command, then you can go to the Virtual Machine manager and halt or shutdown within the VM itself, then you can click the PowerOff button in the VM window. You'll want to avoid a forced shutdown since those are equivalent to yanking the power cord out of the wall on a physical machine!

4. Now, shut-down your centos1 VM normally, and close the centos1 VM window.
5. Switch to your terminal and issue the command: virsh start centos1
6. Using the appropriate command check to see if your centos1 VM is now running.
7. There are other commands that can be used (such as suspend, or shutdown). The "shutdown" command may not always work since it relies on the guest handling a particular ACPI event. Why do you think it is useful to have commands to manipulate VMs?

Answer all observations / questions in your lab log book.

Part 2: Backing Up Virtual Machines

Backing up VMs There are two general processes in order to back up your images: Compressing your images (also recommended to backup up to external storage USB Key) using the gzip command. Backup the VM xml configuration file (preferably to USB key) using virsh shell command to add VM to virtual machine manager list (in the event that the HOST machine is "wiped" and re-installed, but VM images and xml configuration files have been backed up external storage). Taking the time to backup the image of the Operating System's file system allows the user to return to a "restoration point" using the gunzip command in case something bad occurs to the OS during a lab. Failure to take the time to make and confirm backups can result in loss of lab work for the student!

1. Shut down all of the virtual machines.
2. Change to the directory /var/lib/libvirt/images/. Note the size of the files in this directory. What do these files contain?
3. Make a compressed backup of the centos3.img file to your home directory with this command: gzip < centos3.img > ~YourUserId/centos3.img.backup.gz
   (Note: Make certain to use the redirection signs "<" and ">" properly in the command!)
4. Compare the size of the compressed and original files.
5. Start the centos3 VM.
6. Make certain that you are in your VM and not in your main system!
7. >Wreck only your centos3 system! Try this command inside the centos3 virtual machine:rm -rf /*
8. Shut down the VM. If you tried to start the centos3 VM, it would not boot since all system files have been removed!</li>
9. Restore the original image from the backup in your home directory by typing this command: gunzip < ~YourUserId/centos3.img.backup.gz > centos3.img
10. Restart the VM. Is it working normally?
11. Create compressed backups of your other virtual machines.</li>
12. You should make a copy of the xml configuration file in case you "wipe" and re-install the host machine, and want to add a restored VM backups to the virtual machine manager list. We will demonstrate using the centos3 xml configuration file, and prove that a "clone" can be added to your list.Please perform the following step:
13. Execute the following command: virsh dumpxml centos3 >centos3.xml
14. Examine the file centos3.xml. What does it contain? What format is it in?
15. Make a copy of centos3.xml called centos3a.xml.
16. Edit the file centos3a.xml, making the following changes:

• Change the name (in the file, not the file name) to centos3a
• Change at least one of the hexadecimal characters in the UUID. Do not change the length of the UUID. Valid hexadecimal characters are 0-9 and a-f.

Issue this command: virsh define centos3a.xml

Issue the command virsh list --all and record any changes.

Issue the command: virsh undefine centos3a

Shutting Down the Host while Virtual Machines are Running If you shut down your host system while virtual machines are running, they will be suspended, and will resume the next time you boot your host system.

17. List all of the virtual machines again, and note any changes.
18. For the remainder of these labs, it is assumed that you will backup both the images and xml configuration files for all Virtual machines, when asked to backup your virtual machines. It is also highly recommended to backup these files to an external storage device (eg. USB key) in case the host machine gets "wiped" and you need to rebuild your HOST machine and then restore your Virtual Machines...
19. Answer this question in your log book:

• In order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?

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

INVESTIGATION 3: LOOKING AHEAD

Part 1: Automating Routine Tasks (Shell Scripting)

Bash Shell Scripting Tips: She-bang line on first line of shell script: Shell scripts have evolved of the past 40 years. To avoid running a newer shell script on an older shell, it is recommended to force running the shell script in the correct shell. In order to do this, on the first line at the very beginning of the shell script, you add the #! (# as in "shhhh" - a comment, and ! is referred to as "bang" run a commmand: in this case, run the command: /bin/bash). You can issue the Linux command which bash to get the correct location. If there is no bash shell on that machine, the shell script will not run (as a precaution - the Linux admin will know how to make a fix to the shell script if required) . Variables: There are 3 types of variables that can be used in shell scripting: ENVIRONMENT (eg. $USER), user-defined ($varName), and positional parameters (eg. $1, $2... containing arguments after shell script or by using set command (eg. set $(ls) ). Using dollar sign ($) in front of variable expands the value assigned. Command Substitution: A very useful trick to take output from a command to be used as an argument for another command. Examples include: file $(ls) set $(ls);echo $#;echo $* echo "hostname: $(hostname)" Logic Control Flow Statements: The test command can be used to see if a condition is true or false (i.e. test $USER = "root") . The $? special shell variable stores the result (zero if true, non-zero if false). Square brackets [ ] can be used to represent the test command with the condition inside the brackets (spaces separating brackets).Can use if / if-else / if-elif-else statements with brackets. The exit command can be used to terminate the shell script with a false value. Examples if [ $USER = "root" ] then  echo "You must be root" >&2  exit1 fi if [ $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

We continue the discussion of using Bash Shell Scripts to help automate routine tasks for the Linux system administrator. In lab1, you were exposed to downloading and running Bash Shell Scripts for demonstration purposes. Before showing you demos for this lab, you should learn a few more "shell scripting tricks" in case you need to create your own set of tools for task automation.

1. Click on the following link to run an online tutorial showing you some additional shell scripting techniques: [ link ].
2. It is recommended to practice creating Bash Shell Scripts as you proceed throughout this course.
3. Let's look at some demos involving managing VMs with shell scripts. Issue the following command:

   wget https://scs.senecac.on.ca/~elizabeth.kopiec/backupVM.bash

4. Set the appropriate permissions and run this Bash Shell script.
5. Verify that the backup of your virtual machine occurred (hint: issue ls command to verify the date and time of creation).
6. Use the wget command to download, study, and run the following shell scripts on-line:

   https://scs.senecac.on.ca/~murray.saul/vm-start-text.bash
https://scs.senecac.on.ca/~murray.saul/vm-stop-text.bash
https://scs.senecac.on.ca/~murray.saul/vm-start.bash
https://scs.senecac.on.ca/~murray.saul/vm-stop.bash

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

Answer all observations / questions in your lab log book.

LAB 2 SIGN-OFF (SHOW INSTRUCTOR)

Students should be prepared with all required commands (system information) displayed in a terminal (or multiple terminals) prior to calling the instructor for signoff.

Arrange evidence for each of these items on your screen, then ask your instructor to review them and sign off on the lab's completion:

✓ Three working virtual machines created.

✓ Disk layout and size correct on all virtual machines

✓ Use virsh to list the status of all vms.

✓ All virtual machines fully updated.

✓ All virtual machines backed up to a usb stick.

✓ Installation comparison table filled in.

✓ Lab Logbook (lab2) notes filled-in.

Preparing for Quizzes

1. What is the name of the CentOS installation program?
2. Which factors recorded in your table (above) were due to the type of installation performed, and which factors were due to the amount of software installed?
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. What factors affect installation time?
6. How can you reduce the number of software updates required immediately after installation?
7. Why would you enable additional repositories during installation?
8. What does the file /root/anaconda-ks.cfg contain, and how is it created?
9. How do you start and stop virtual machines?
10. How do you SSH into your virtual machines?
11. What is the purpose of and relationship between these pieces of software?
    • libvirt
    • libvirtd
    • virsh
    • virt-manager
    • virt-install
    • kvm
12. The kickstart installation (centos3) was a network installation. Can a kickstart file be used with a DVD installation?
13. The kickstart installation (centos3) was fairly fast. Why? Under what circumstances would it take a long time, even on a fast network?
14. What other types of installation sources are possible (besides Live Disc, Installation Disc, and Network?)