OPS335 Installation Lab

Objectives

• Install your host machine (Centos 7)
• Install 3 virtual machines (VMs) (Fedora 22 - Server)
• Prepare for Lab Exercises / Exploration Questions

Required materials

• Centos 7 Installation DVD
• One SATA hard disk in a removable drive tray (minimum 250GB) - It is strongly advised you dedicate a drive for this course only.
• Recommended - USB drive (8 GB+) for creating and storing backups (Virtual Machines, configuration files)

Part A: Host Installation

Installation instructions for Centos 7

1. Download a copy of the Centos 7 installation DVD (64 bit edition) from the Centos web site or belmont. Note: we'll be using the 64 bit version of Centos because all of our lab computers are equiped with Intel 64 bit mainboards and CPUs. We'll also be using a Fedora iso for installing the virtual machines, but you will not need to burn that to a disc. It is faster to download the ISO and install directly from it.
   • Seneca's mirror of Centos: http://belmont.senecacollege.ca/pub/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1511.iso
     (This is very fast, but is only accessible from within Seneca's network - you can't access this from home. You can burn this disc on the machines in the Open Lab.)
     
   • Centos mirror list (available from any Internet connection): https://www.centos.org/download/mirrors/ (version: 7.2.1511)
     
2. Insert your HDD into the docking bay of a PC in the lab and boot the computer using your installation DVD. If possible try to use the same PC for this course for the rest of the semester. Some PCs may be configured with slight hardware variations from others which may cause problems when moving your HDD from one system to another.
3. Most modification is now perform through a single summary screen. Use it to customize your installation following these guidelines:
   • Set Date & Time
   • Turn on networking and use your Seneca ID as the hostname.
   • Under software selection, choose Server with gui, and ensure you enable the software package KDE (located on the right-hand-side).
   • For installation destination, select your drive (not the one internal to the PC), and select the option to manually configure partitioning.
     • Delete any old partitions.
     • Click the link to create partitions automatically (this will give a typical layout with /, /boot, /boot/efi, /home, etc).
     • Free up space by shrinking the /home partition. Since your machine will have far fewer users and more virtual machines than a typical installation, we will need that space elsewhere.
     • Create a new logical volume for /var/lib/libvirt/images and give it the space made available by shrinking /home (You will need enough space for 6 virtual machines at 8GB each). You may wish to keep some extra space left unassigned in case you need some space later, but the majority of the space you will need will be for /var/lib/libvirt/images.
     • Make certain that the existing partitions have the file system type ext4 (not xfs).
4. During the installation process you will also have the opportunity to create users.
   • set the root password
   • create a user account named with your Seneca ID
5. After completing the installation, remove the DVD and reboot from your HDD.

Booting your system

1. Login as the user you created and open a terminal window. Then use 'su' to become root and run the 'yum update' command. Reboot after all updates have completed. Now that your system is up to date, again login using your learnid and do the following:
   • Verify that your system date and time are correct. If not then set the correct system date and time.
   • Verify that your network is functioning.
     • If you do not have an ip address, edit the line in either the file /etc/sysconfig/network-scripts/ifcfg-eno1 or /etc/sysconfig/network-scripts/ifcfg-eth0 (note this file name may differ between machines).

 onboot=no

should be:

 onboot=yes

2. If you had to change that, reboot your machine before continuing.
3. Run and record the purpose and output after issuing the following commands:

df -hT
cat /etc/fstab
cat /etc/issue
uname -a

Using iptables

The most recent variants of Centos and Fedora are using a service called firewalld that is intended to replace iptables, however the iptables service is still in relatively common usage. In this course we will keep running iptables on the host machine, and gain experience with the new service (firewalld) on the virtual machines.

1. install and enable iptables

yum install iptables-services
systemctl enable iptables

2. disable firewalld by issuing the command:
   

systemctl disable firewalld

3. Note that the machine will not switch over to using iptables until you reboot, but you will be doing that shortly, so there is no need to do so right now.

Configuring a Linux Gateway

At this point you have a basic Centos system installed and updated. This will serve as a host for the virtual machines where you will do the majority of the work in this course. All the rest of our labs will assume you have this basic system running. If, for any reason, your system becomes corrupted during the semester, you'll have to redo this lab to be able to continue with the remaining uncompleted labs. You are responsible for YOUR system. If you do not perform back-ups you have taken this risk on yourself. Poor planning on your part does not constitute an emergency for anyone else.

1. You will need to install some software to allow your machine to act as a host for virtual machines. Issue the following command:

yum install virt-manager libvirt

2. Start and enable the virtualization service:

systemctl start libvirtd
systemctl enable libvirtd

3. Reboot your machine. If you do not, you will not be able to install any virtual machines.
4. Start the graphical virtual machine manager (virt-manager)
   • You will need to enter your root password.
5. We will be creating our own virtual network. A default virtual network has been created for you, but you will be using a custom one in this course.
   • Right click localhost (QEMU) and select Details. Click on the Virtual Networks tab.
   • Stop and delete the default network.
   • Run, and record the output of the following command:

iptables -t nat -L

6. Use the plus sign to add a new virtual network using the following options.
   1. Name your virtual network ops335
   2. Use the last two digits of your student number for the third octet of network IP address (for example, if your student number is 000-000-090, the network address would be 192.168.90.0/24.
   3. Ensure the DHCP range will allow you to assign at least 3 static IP addresses outside it.
   4. Choose Forwarding to physical network radio button, Destination: Any physical device and Mode: NAT
   5. Ensure the network is started at boot.
7. Once completed changing these settings, open a terminal and observe and record the output of the following command (noting the difference from the last time you ran it. We will discuss it in a few weeks):

iptables -t nat -L

Record steps, commands, and your observations in Part A in your OPS335 lab log-book

Part B: Virtual Machine Installation

With the virtualization software installed and your personal network created, you are now ready to create your first virtual machine. If you have an installation DVD for Fedora you can use that, but it will be much faster to download the iso from belmont and install directly from it.

wget http://belmont.senecacollege.ca/pub/fedora/releases/21/Server/x86_64/iso/Fedora-Server-DVD-x86_64-21.iso

If it has not been made available use the publicly available link:
wget --no-check-certificate https://download.fedoraproject.org/pub/fedora/linux/releases/22/Server/x86_64/iso/Fedora-Server-DVD-x86_64-22.iso

Installation

1. Click on the icon Create a new virtual machine to begin.
2. Name your machine f22-vm1 and choose your installation method: Local install media. Choose the desired option to install from either the CD or iso.
3. Use the default memory and CPU options for use with lab computers (Depending on available hardware these settings can be adjusted). Then click on the Forward button to proceed.
4. Leave the disk image size set at 8GB and click on the Forward button.

5. At the Ready to begin installation window click on Advanced options arrow to review available options.
   • Select the Virtual Network named ops335. Make note of any other available options (you will need them again in the assignments).

6. Select Install to Hard Drive to begin your Fedora installation. Select the appropriate default options (You may wish to review your OPS235 notes to remind yourself what these are).
7. During installation you will be prompted to set the root password and an initial user account. For the initial user, enter the same information you entered on your host machine.
8. Set your hostname to vm1.localdomain.

Firstboot - First user created
For successful completion of the labs, please ensure the first user created is named using your Seneca username.

First Boot

1. You will notice that the server installation defaults to a command-line interface. This is normal, and we will only be using this interface during this course.
2. Ensure your machine has a network connection by running the command

host cbc.ca

3. If that did not work, edit the line in the file /etc/sysconfig/network-scripts/ifcfg-eno1 or /etc/sysconfig/network-scripts/ifcfg-eth0

 onboot=no

should be

 onboot=yes

4. If you had to change that, reboot your machine.
5. Once you have a working connection update your machine (this may take a while).

 yum update

6. Reboot the virtual machine once it is updated.
7. If your virtual machine hangs on boot, you will need to change a graphics option:
   • While the VM is off, click on View (from the menu at the top of the VM window), and select Details.
   • From the menu on the left side, select Display.
   • Change the drop-down list for Type from VNC to Spice, and click apply.
   • Switch the view back to Console and start the machine again.
   • Now run the following commands and note the output.
   • Issue the commands below and note in your lab logbook how they differ from the Centos installation on your host.

 df -hT
 cat /etc/fstab
 cat /etc/issue
 uname -a

Cloning a Virtual Machine

1. Now that you have one virtual machine working, you will create two more. If you struggled with the previous steps, repeat them to create two more virtual machines (naming them f22-vm2 and f22-vm3, with hostnames vm2.localdomain and vm3.localdomain respectively).

2. If you are confident with what you have done so far, you may clone your existing machine to create the others by following there steps:
   • To quickly create additional VM's shutdown f22-vm1, right click and select Clone....
   • Set the Name to be: f22-vm2
   • Once successfully created, boot the new VM and correct the host name. This can be done using the hostnamectl command-line tool.
   • Record in your notes how each is done.
   • Use the host command to check for connectivity
   • After creating f22-vm2 repeat the above steps to create f22-vm3 and correct the host name.

Record steps, commands, and your observations in Part B in your OPS335 lab log-book

Completing the Lab

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 (command output) for each of these items on your screen, then ask your instructor to review them and sign off on the lab's completion:

✓ Host Machine installed

✓ 3 virtual machines installed (running Fedora 22 Server)

✓ Each machine (host and VM) has access to the network

✓ Lab logbook completed

✓ Run a shell script to submit your lab:

  Steps:

• Issue the following command to download the bash shell script:
  wget http://matrix.senecac.on.ca/~peter.callaghan/files/OPS335/labcheck0.bash
• Run the command:
  

labcheck0.bash > lab0host.txt

• Follow the instructions and press SEND for marking (only 1 submission permitted)

Exploration questions

1. What is the code name of your installed Fedora Linux system? How did you determine this?
2. What kernel release is your host system running?
3. What kernel release are your virtual machines running?
4. What is the UUID (Universally Unique Identifier) of your root file system? What command was used to obtain this information?
5. What is the size and type of the /boot file system on your host?
6. What file was edited to change the host name on your VM's?
7. Explain the iptables rules displayed when you ran the command 'iptables -t nat -L'. How did they change after creating your personal network.