Latest revision as of 11:29, 24 September 2018

THIS IS AN OLD VERSION OF THE LAB
This is an archived version. Do not use this in your OPS235 course.

Fedora 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3)

Introduction

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.

In this lab, you will create three virtual machines. This also gives you an opportunity to experiment with different ways of installing Fedora. Later in this course you will install another operating system distribution in a virtual machine.

You should already have both a Fedora installation DVD and a Fedora LIVE CD.

In both cases, the boot media (which you used to load the installation software) and the installation source (the software that got installed) were the same: your CD/DVD provides both. However, the Fedora (and most other Linux distributions) permits you to use any combination of boot media and installation media:

Method	Boot Media	Install. Source
CD or DVD	✓	✓
Hard Disk	✓	✓
USB Flash Drive	✓	✓
Network (http/nfs repository)	✓	✓
PXE Network Boot	✓	X

Objectives

Understand Virtualization
Use KVM virtualization on Fedora
Use a variety of installation methods:
- Live Image Installation
- Network Installation
- Kickstart Installation
Understand the advantages and disadvantages of each type of installation, and be able to select the best installation method for a particular situation.

Required Materials (Bring to All Labs)

Fedora 17 LIVE CD
Fedora 17 x86_64 Installation DVD
SATA Hard Disk (in removable disk tray)
USB Memory Stick
Lab Logbook

Prerequisites

Completion and Instructor "Sign-off" of Lab 1: OPS235 Lab 1

Linux Command Online Reference

Each Link below displays online manpages for each command (via http://linuxmanpages.com):

virsh (Refer to Fedora Virtualization Guide link in the "Resources on the Web" section)
gzip / gunzip

Resources on the Web

Virtualization:

Live Image Installation:

Network Installation:

Kickstart Installation:

Fedora Virtualization Guide

Fedora 17 Installation Guide

Performing Lab 2

Preparation

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 Fedora mirror server -- note that you may need to change the directory name as well as the server name. The installation of the fedora3 virtual machine must be done at Seneca.

Open a web-browser, and open the OPS235 Lab #2 WIKI.

NOTE: You need to enter your "MySeneca" username and password to obtain a "wired" Internet connection (otherwise, you will not be able to perform the "groupinstall" command in the next step). Remember to perform a "wired-connection" (logging in with your MySeneca username and password via a web-browser) every time you boot-up your host machine...
Install the Fedora virtualization software: yum groupinstall "Virtualization" or pkcon install @virtualization The virtualization software installed is in three parts:

A system service named libvirtd that manages the VMs.
Tools to manage virtualization, including the virt-manager graphical tool and the virsh command-line tool.
The actual virtual machines themselves.

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

Reboot your fedora host now
virt-manager may not work properly unless you reboot after installing the virtualization software.

After rebooting your computer system, and logging back into your account, start the graphical tool by selecting the menu options Activities>Applications>System Tools>Virtual Machine Manager or by typing the command virt-manager

Run virt-manager as a regular user
Running virt-manager as root may not work due to configuration issues.

Investigation 1: Installing from a Live Disc

Using an Image instead of a Live Disc
It is recommended that you perform this installation from your Fedora LIVE CD. As a matter of interest (for future reference), it is possible to install directly from the ISO file you used to burn your Live CD. There are many Internet tutorials that show the individual how to perform that task.

Introduction

In this investigation, you will install Fedora from your live disc, and observe the differences between this type of installation and the DVD installation previously performed.

VM Details

Name: fedora1
Boot media: Fedora Live CD
Installation source: Fedora Live CD
Memory: 768MB
Disk space: 10GB
CPUs: 1

Screen-Shot Thumbnail Reference

Virtual Machine Screen Shots Thumbnails
While performing the Virtual Machine setup, click on the thumbnails below to provide a "visual reference" while performing this section.

Virtual Machine Manager: Create a New Virtual Machine

Step 1 of 5: Create a New Virtual Machine

Step 2 of 5: Create a New Virtual Machine

Step 3 of 5: Create a New Virtual Machine

Step 4 of 5: Create a New Virtual Machine

Step 5 of 5: Create a New Virtual Machine

Steps

In the Virtual Machine Manger, click on the icon to Create a Virtual Machine in the upper-left corner:
(refer to Virtual Machine Manager thumbnail above).
A window will appear with the title New VM. There are five steps to be completed; click Forward after each step:
Step 1 of 5: Enter the virtual machine (called fedora1) name and select Local install media (refer to Step 1 of 5 thumbnail above).
Step 2 of 5: Insert the CDROM or DVD containing the Fedora 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 Fedora 17 (refer to Step 2 of 5 thumbnail above).
Step 3 of 5: Set the memory to 768 MB and the number of CPUs to 1 (refer to Step 3 of 5 thumbnail above).
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 (refer to Step 4 of 5 thumbnail above).
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 (refer to Step 5 of 5 thumbnail above).

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.

Fedora LIVE CD Install Screen Shots Thumbnails
While performing the Fedora 17 LIVE CD install, click on the thumbnails below to provide a "visual reference" while performing this particular Fedora installation.

The Virtual Machine will now start.

Ignore and close the "Failed To Load" dialog box. Search for the panel on the upper-left-hand side of the screen.

Login to the VM and double-click:
Applications
>System Tools
>Install to Hard Disk.

Select Specialized Storage Devices

Select Virtio Block Device.

You will get the Firstboot configuration questions during the boot process.

The virtual machine will now start. Select the default menu item labelled: Start Fedora 17. 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.

Login to the VM and click: Applications>System Tools>Install to Hard Drive. The installation program, similar to the one used when installing Fedora 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.

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.

During the installation process, when prompted for a storage device, first select Specialized Storage Devices, and then select the Virtio Block Device option.
When prompted for the hostname, enter fedora1, and when prompted for the timezone, select Toronto - Eastern Time Ontario, and 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.
When the installation is complete, click on the reboot button at the bottom right-hand corner of the screen.

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 optionally send the hardware profile to the Fedora Project). Create a user with the same name as your Matrix account.
Login using the new user account.

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

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
Find out the IP address of your virtual machine: ifconfig eth0
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
Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): ssh IPaddress

Switch to Virtual Machine Manager Window
If you are currently in a Virtual machine, but want to switch to the Virtual Machine Manager Window, simply click Activities> Select the Virtual Machine manager window.

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

Investigation 2: Installing from the 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.

Introduction

It is possible to install Fedora entirely from the network. In this investigation, you will install Fedora from a webserver on Seneca's LAN.

VM details

Name: fedora2
Boot media: Network installation
Installation source: http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/
Memory: 1024MB
Disk space: 20GB
CPUs: 1

Steps

Create the VM (called fedora2) as you did with the fedora1 virtual machine, except:
- In step 1 of 5, set the installation type to Network Install (HTTP, FTP, or NFS).
- In step 2 of 5, provide the location of the software source by providing the URL http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/
- In step 2 of 5, set the OS Type to Linux and Version to Fedora 17.
Observe the boot process. How is it different from booting from an optical disc (CD/DVD)?
Start the installation process (make certain to use information in the VM Details section above).
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).
On the software selection screen, select Graphical Desktop.
On the same screen, select the "Fedora 17 - x86_64" and the "Fedora 17 - x86_64 - Updates". Leave "Installation Repo" selected. DO NOT enable the "Test Updates" repository.
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.

Investigation 3: Installing from the Network using Kickstart

Introduction

When Fedora is installed using the techniques you have used so far, the user is asked a number of questions. In some situations, it is better to provide the answers to these questions in a file rather than answer them individually. This type of file is called a kickstart file.

In this investigation, a kickstart file is provided for you. You can also create or modify a kickstart file using a regular text editor or a graphical tool.

VM details

Name: fedora3
Boot media: Network installation
Installation source: http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/
Kickstart location: http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora17-kickstart.cfg
Memory: 1024MB
Disk space: 15GB
CPUs: 1

Steps

Create the VM as you did with the fedora2 virtual machine, specifying a network install as before, except:
- In step 2 of 5, after entering the URL for the installation source, click on the URL Options control.
- Enter the Kickstart URL: http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora17-kickstart.cfg
Observe the installation. How is it different from booting from an optical disc (CD/DVD)?
Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations.
What happens when the installation is finished?
Take a look at the kickstart file (using the URL you entered) to determine the root password as well as the name and password for the first user account.
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 3 observations / questions in your lab log book.

Investigation 4: Updating and Comparing the VMs

In each VM, run this command: yum update
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?

Complete the following table (and transfer into your lab2 log-book notes):

	f17host	fedora1	fedora2	fedora3
Installation Method	Installation Disc	Live Disc	Network Installation	Network Installation + Kickstart
Packages Installed
Updates Installed immediately after installation
Software could be selected during installation
Disk layout could be selected during installation
No questions asked during installation
Total installation time (after installation questions)
Amount of disk space used
Questions asked during first boot
Advantages of this type of installation
Disadvantages of this type of installation
This type of installation is recommended for...

Investigation 5: 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.

Start the fedora1 virtual machine, and stop the fedora2 and fedora3 virtual machines.
Switch to the f19host machine, and open a shell terminal.
Enter these commands into your f19host machine and note the result:
- virsh list
- virsh list --all
- virsh list --inactive
Now, shut-down your fedora1 VM normally, and close the fedora1 VM window. Make certain NOT to close the Virtual Machine Manager main window.
Switch to your terminal and issue the command: virsh start fedora1
Check to see if your fedora1 VM is now running.
Switch to the terminal and issuevirsh list --all and confirm the status of the fedora1 VM.
There are other commands that can be used (such as suspend, or shutdown). The "shutdown" command may not always work since it sends a request to "shutdown virtual machine gracefully", but may not always work. Why do you think it is useful to have commands to manipulate VMs?

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 cord out of the wall on a physical machine!

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

Investigation 6: How do I backup a virtual machine?

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 xlm 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!

Shut down all of the virtual machines.
Change to the directory /var/lib/libvirt/images/. Note the size of the files in this directory. What do these files contain?
Make a compressed backup of the fedora3.img file to your home directory with this command: gzip < fedora3.img > ~YourUserId/fedora3.img.backup.gz
(Note: Make certain to use the redirection signs "<" and ">" properly in the command!)

Make sure the backup is successful!
If there are any error messages, DO NOT proceed past this point. You're going to destroy your fedora3 virtual machine and restore it using the backup you have created -- if there are any problems with the backup, you will not have a working virtual machine, and will have to re-install it.

Compare the size of the compressed and original files.
Start the fedora3 VM.
Make certain that you are in your fedora VM and not in your Fedora main system!
Wreck only your fedora 3 system! Try this command inside the fedora3 virtual machine: rm -rf /*
Shut down the VM. If you tried to start the Fedora3 VM, it would not boot since all system files have been removed!
Restore the original image from the backup in your home directory by typing this command: gunzip < ~YourUserId/fedora3.img.backup.gz > fedora3.img
Restart the VM. Is it working normally?
Create compressed backups of your other virtual machines.

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 fedora 3 xml configuration file, and prove that a "clone" can be added to your list.Please perform the following step:
1. Verify that you are in the directory: /var/lib/libvirt/images/.
2. Execute the following command: virsh dumpxml fedora3 >fedora3.xml
3. Examine the file fedora3.xml. What does it contain? What format is it in?
4. Make a copy of fedora3.xml called fedora3a.xml.
5. Edit the file fedora3a.xml, making the following changes:
Change the name (in the file, not the file name) to fedora3a

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.
1. Issue this command: virsh define fedora3a.xml
2. Issue the command virsh list --all and record any changes.
3. Issue the command: virsh undefine fedora3a
4. List all of the virtual machines again, and note any changes.
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...
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?

Backing up VMs
It is essential to back up your VMs at the end of each lab, so you can easily restore them if something goes wrong in the next lab.

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.

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

Investigation 7: Kickstart Files

SSHD and Firewall
If you have restarted your virtual machine fedora1, the sshd server you started in investigation 1 (step 15) will no longer be running. In addition, the firewall will have reverted to its original state. In order to use scp, below, you will need to restart ssh and adjust the firewall again.

If students cannot backup their kickstart files using the scp command, they can use a web-browser to access their Seneca e-mail with attachment (copy kickstart file to their home directory first!). For the text-based Linux system "fedora3", students can use the mail command (refer to the man command to learn how to send e-mail attachments).

When you perform a non-Kickstart installation, the installation program creates a Kickstart file in the /root directory for reference.

Obtain the kickstart files for all four of your installations (your disk pack f17host, plus the fedora1, fedora2, and fedora3 virtual machines).
To prevent confusion, copy your kickstart files to kickstart filenames that describe their purpose (eg. kickstart_host, kickstart_fedora1, kickstart_fedora2, etc...)
Copy them all to your f17host system (tip: use scp), or use the hint in the tip box above to send via e-mail.
Compare these files. What are the differences? Similarities? (Tip: you may want to use tools such as sdiff to help with the comparison).
How could you use the kickstart file produced by the installation program to perform additional, identical installations?

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

Completing the Lab

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.
Four kickstart files.
All virtual machines fully updated.
All virtual machines backed up.
Installation comparison table filled in.
Lab Logbook (lab2) notes filled-in.

Preparing for Quizzes

What is the name of the Fedora installation program?
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?
Which type of installation works best for confirming compatibility with hardware before installation? Why?
Which type of installation works best for installing large numbers of computers? Why?
What factors affect installation time?
How can you reduce the number of software updates required immediately after installation?
Why would you enable additional repositories during installation?
What does the file /root/anaconda-ks.cfg contain, and how is it created?
How do you start and stop virtual machines?
How do you SSH into your virtual machines?
What is the purpose of and relationship between these pieces of software?
- libvirt
- libvirtd
- virsh
- virt-manager
- virt-install
- kvm
The kickstart installation (fedora3) was a network installation. Can a kickstart file be used with a DVD installation?
The kickstart installation (fedora3) was fairly fast. Why? Under what circumstances would it take a long time, even on a fast network?
What other types of installation sources are possible (besides Live Disc, Installation Disc, and Network?)

@@ Line 1: / Line 1: @@
 [[Category:OPS235]][[Category:OPS235 Labs]]
-=OPS235 Lab 2 GNU/Linux Installation - Fedora 12=
+{{Admon/caution|THIS IS AN OLD VERSION OF THE LAB|'''This is an archived version. Do not use this in your OPS235 course.'''}}
-==Objectives==
+= Fedora 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3) =
-#To perform a GNU/Linux installation using the Fedora 12 distribution
+== Introduction ==
-#To perform boot time customization and configuration
-#To obtain network configuration from a DHCP server
-#To secure the boot loader by adding password protection
-#To investigate GRUB boot loader configuration
-==Reference==
+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:
-* [http://linuxmanpages.com/ man pages]
-** mount
-** rpm
-** hostname
-** uname
-** ps
-** ifconfig
-** netstat
-** route
-** nslookup
-** wc
-** grub
-* Resources on the web
+:* '''Software testing''' -- Using multiple operating systems simultaneously on a single computer for testing and experimentation.
-** [http://fedora.redhat.com/docs/release-notes/ Fedora Release Notes]
+:* '''Network simulation''' -- Testing network services, protocols, and security scenarios with a small number of computers.
-** [http://docs.fedoraproject.org/install-guide/ Fedora Installation Guide]
+:* '''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.
-** [http://www.gnu.org/software/grub/manual/html_node/Security.html#Security Protecting Grub]
+:* '''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).
-** [http://opensource.sgi.com/LDP/HOWTO/Kernel-HOWTO/grubconf.html Grub Details and Sample Config]
+:* '''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.
-** [http://www.aspencrypt.com/crypto101_hash.html One-way Hash Function]
-** [http://www.dedoimedo.com/computers/grub.html GRUB Tutorial]
-** [http://www.securitystats.com/tools/password.php Password Security]
-==Required Material==
+{|cellpadding="8" width="100%"
+|- valign="top"
+|
-* Fedora 12 x_64 Installation DVD - You can burn this onto a DVD-R in the Open Lab
+'''In this lab, you will create three virtual machines'''. This also gives you an opportunity to experiment with different ways of installing Fedora. Later in this course you will install another operating system distribution in a virtual machine.
-* SATA Hard Disk (the same one used for Lab 1)
-* USB Memory Stick (minimum 64M)
-==Prerequisite==
-* Completion of Lab 1
+You should already have both a '''Fedora installation DVD''' and a '''Fedora LIVE CD'''.
-==Introduction==
-In this lab, you are going to install the Fedora (GNU/Linux Distribution) to your hard disk from DVD.
+In both cases, the boot media (which you used to load the installation software) and the installation source (the software that got installed) were the same: your CD/DVD provides both. However, the Fedora (and most other Linux distributions) permits you to use any combination of boot media and installation media:
-You need a number of hard disk partitions/physical volumes for this installation: the /dev/sda1 (300M),  the /dev/sda2 extended partition, the /dev/sda5 (300M), all created in Lab 1, and 4 new physical volumes which you will create during this lab.
+|
+{|border="1" cellpadding="3" width="100%"
+|-
+! Method
+! Boot Media
+! Install. Source
+|-
+! CD or DVD
+! &#10003;
+! &#10003;
+|-
+! Hard Disk
+! &#10003;
+! &#10003;
+|-
+! USB Flash Drive
+! &#10003;
+! &#10003;
+|-
+! Network (http/nfs repository)
+! &#10003;
+! &#10003;
+|-
+! PXE Network Boot
+! &#10003;
+! X
+|}
-After the installation, you will collect baseline information about your Fedora GNU/Linux system, do some post installation configuration to prepare your system for the remainder of the labs, manipulate the GRUB configuration, and start using the system.
+|}
-==Instructions==
+== Objectives ==
-# Insert and secure your SATA hard disk to the removable disk slot.
+* '''Understand Virtualization'''
-# Power up the computer.
+* '''Use KVM virtualization on Fedora'''
-# Insert the Fedora 12 x_64 Installation DVD into the DVD drive.
+* '''Use a variety of installation methods:'''
-# Reboot the system.
+** Live Image Installation
+** Network Installation
+** Kickstart Installation
+* '''Understand the advantages and disadvantages of each type of installation, and be able to select the best installation method for a particular situation.'''
-===Investigation 1: How do you install Fedora?===
-{{Admon/note | Please take note! | Fedora uses a type of partition management called Logical Volume Management (LVM). In LVM, disk partitions are called Physical Volumes (PVs) and provide storage to a Volume Group (VG). This storage is then split into various Logical Volumes (LVs). The advantage to this scheme is that you can change LV size and you can add and remove PVs after installation. For example, you can add a new disk to your system and then increase the size of your existing filesystems using that extra disk space.
-Please be careful to enter all LVM information accurately, including the VG and LV names. We will investigate and manipulate LVM in future labs.}}
+== Required Materials (Bring to All Labs) ==
-At the Welcome Screen choose "Install or upgrade an existing system" to launch the Graphical installation program and select the following options (you can use the media test to verify that your DVD burned correctly; --It will take some time-- otherwise, skip it):
+* Fedora 17 LIVE CD
+* Fedora 17 x86_64 Installation DVD
+* SATA Hard Disk (in removable disk tray)
+* USB Memory Stick
+* Lab Logbook
-# Language - English
-# Keyboard Configuration - U.S. English
-# Set your hostname to - f12host (one word, no space, all lowercase)
-# Set your timezone to - America/Toronto and check that your system time is correct
-# Root Password: enter a password of your own choosing. Pick one that is really, really hard to guess to protect your system. (Recommendation: use the first letter and all the punctuation from a favorite phrase or song verse. For example, "To be or not to be, that is the question!" could become the password "Tbontb,titq!").
-# Disk Partition Setup - Specify a Custom Layout, and then set up the installation with this configuration:
-#* Find your existing 300MB partition (/dev/sda1). Edit this entry so that the mountpoint is /boot and is formatted as an ext3 filesystem.
-#* Don't touch the other existing 300M partition (/dev/sda5).
-#* Create 4 new partitions that are 20% of the remaining space on your disk (minimum 15000 MB) in size. Set the File System Type to Physical Volume (LVM). Should be /dev/sda6 to /dev/sda9.
-#* Use the LVM button to create a Volume Group. Set the Volume Group Name to '''vg_main''' and set the Physical Extent size to '''4MB'''.
-#* Click on the Add button to create a logical volume within that volume group:
-#** Mount point / (root), filesystem type ext4, logical volume name root, size 50GB (50000MB).
-# Say yes to continue without a swap partition.
-# Say yes to format /dev/sda1.
-# Accept Boot Loader defaults.
-# Accept Office and Productivity and repository defaults.
-{{Admon/note | Please take note! | The installation process will take about 15 minutes to complete on the P4 CPU system when using DVD. Click the Reboot button on the screen to reboot the system after the installation is complete. There is a post installation setup after boot.}}
+==Prerequisites==
-# Reboot
+* Completion and Instructor "Sign-off" of Lab 1: [[OPS235 Lab 1]]
-# Check the License Agreement. What license is used for the Fedora distribution? What activities do have restrictions and obligations?
-# Create a user account for yourself using the same name as your learn account.
-# Set date and time. Normally, you would want to enable Network Time Protocol, but since we will be experimenting with the networking turned off in later labs, leave it disabled.
-# Click on Do Not Send Hardware Profile.
-# Finish the post-installation customization, wait for the login screen to appear, and then login to your Learn account.
-Answer the Investigation 1 question in your lab log book.
+==Linux Command Online Reference==
+Each Link below displays online manpages for each command (via [http://linuxmanpages.com/ http://linuxmanpages.com]):
+:* '''virsh''' (Refer to Fedora Virtualization Guide link in the "Resources on the Web" section)
+:* [http://linuxmanpages.com/man1/gzip.1.php gzip / gunzip]
-===Investigation 2: How many files packages and files are installed on the system?===
-For the rest of the tasks in this lab, you must login to your system using your Learn account and execute all commands under your learn account. If you get a Permission Denied message when trying to execute a command, then switch to the superuser account by running the command su -  and type in the password for "root". Once the intended command is executed, type "exit" to exit from the superuser account and return to your regular Learn account.
+== Resources on the Web ==
+{|cellpadding="8" width="100%"
+|- valign="top"
+| '''Virtualization''':
+| '''Live Image Installation:'''
+| '''Network Installation:'''
+| '''Kickstart Installation:'''
-Record the commands used and the output generated in each of the following steps:
+|- valign="top"
+|
+[http://docs.fedoraproject.org/virtualization-guide/f13/en-US/html/ Fedora Virtualization Guide]
+|
+* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Fedora_Live_Images/ Fedora 17 Live Image Guide]
+* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Quick_Start_Guide/ Fedora 17 Installation Quick Start Guide]
+|
+[http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ Fedora 17 Installation Guide]
+* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86/ Preparing for a Network Installation]
+* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86 Performing a Network Installation]
+|
+[http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ Fedora 17 Installation Guide]
+* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/sn-automating-installation.html Automating the Installation with Kickstart]
+* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ch-kickstart2.html Kickstart Installations]
+* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ch-redhat-config-kickstart.html Kickstart Configurator]
-# To find all the mount points, enter the command:  ''mount''
+|}
-#* Study the output and record all the mount points in your log book.
-# The name of the installation log file is ''/root/install.log'' -- It is an ASCII file (how can you be sure?) and can be viewed with the ''less'' command.
-# 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 listed in the installation log file:
-#* ''grep ________________ /root/install.log | wc -l''
-# Using the ''rpm'' command: you can also use the following commands to list all the installed packages, and the total number of packages installed:
-#* ''rpm -q -a''
-#* ''rpm -q -a | wc -l''
-#* ''rpm -qa   | wc -l''
-# The -q option means query, and the -a option means all (in other words, query all installed software packages). Did you get the same number of packages from the above two methods?
-# Some of the files on your system were installed with the software packages, and some were created by system activity (for example, by creating your Learn account and by logging in). If you know the package name (from the install.log), you can list all the files that were installed from the package by using the following command:
-#* ''rpm -q -l package_name''
-# This combines the -q (query) option with the -l (list filenames) option.
-# You can pipe the outupt through wc -l to count the number of lines:
-#* ''rpm -ql package_name| wc -l''
-# Using what you learned in steps 3 and 4, get a count of the total number of files installed by all of the software packages on your system.
-# To find out the name that you have assigned to your Linux system, enter the command:  ''hostname''
-# To find out the kernel version of your GNU/Linux workstation and the date it was created, enter the command:   ''uname -r''
-# To find out all the system processes running on your GNU/Linux workstation, enter the command: ''ps -ef''
-# To capture the list of all the system processes to a file called ''ps.lst'', enter the command:  ''ps -ef > ps.lst''
-# Copy the installation log file /root/install.log and the file ps.lst to a USB memory key, or scp to your matrix account as a backup.
-{{Admon/tip |Updating Fedora| You need to complete a system update. Start the Firefox web browser, turn off popup window blocking (select ''Edit>Preferences'', then select the Content tab and uncheck the box to Block Popups), then login to SeneNET. Open a terminal and <code>su -</code> to start a shell as root. Enter the command <code>yum update</code> 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 Fedora Repository mirror.}}
+=Performing Lab 2=
+== Preparation ==
-<!-- {{Admon/tip |SELinux| The final task is to turn off SELinux. SELinux is a Linux feature that provides a variety of security policies, including U.S. Department of Defense style mandatory access controls, through the use of Linux Security Modules in the Linux kernel. While it is certainly something you would leave on in a real world environment, it is beyond the scope of this course and does interfere with some of our activities. To disable SELinux, click on '''System => Administration => SELinux Management'''. Set the "System Default Enforcing Mode" to Disabled. Quit and reboot your system.}} -->
+{{Admon/tip|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 [http://mirrors.fedoraproject.org/publiclist Fedora mirror server] -- note that you may need to change the directory name as well as the server name. The installation of the '''fedora3''' virtual machine <u>must</u> be done at Seneca.}}
-===Investigation 3: What is a runlevel?===
+# '''Open a web-browser''', and open the '''OPS235 Lab #2 WIKI'''. '''<br /><br />NOTE:''' You need to enter your "MySeneca" username and password to obtain a "wired" Internet connection (otherwise, you will not be able to perform the "groupinstall" command in the next step). Remember to perform a "wired-connection" (logging in with your MySeneca username and password via a web-browser) every time you boot-up your host machine...<br /><br />
+# Install the Fedora virtualization software: <code>yum groupinstall "Virtualization"</code> or <code>pkcon install @virtualization</code>  The virtualization software installed is in three parts:
+:* '''A system service named ''libvirtd''''' that manages the VMs.
+:* '''Tools to manage virtualization''', including the <code>virt-manager</code> graphical tool and the <code>virsh</code> command-line tool.
+:* The actual '''virtual machines''' themselves.
+<ol>
+ <li value="3">Start the virtualization service: <code>service libvirtd start</code></li>
+ <li>The firewall configuration is altered by the addition of the virtualization software. Restart the firewall so that these changes become active: <code>service iptables restart</code></li>
+</ol>
-Investigation 3:What is a runlevel?
+{{Admon/caution|Reboot your fedora host now|virt-manager may not work properly unless you reboot after installing the virtualization software.}}
-All the system processes running on your system are controlled by the "init" process which has the process ID (pid) of 1. And this process is the "granddaddy" of all the other processes on your system.
+<ol>
+ <li value="5">After rebooting your computer system, and logging back into your account, start the graphical tool by selecting the menu options '''Activities'''>'''Applications'''>'''System Tools'''>'''Virtual Machine Manager''' or by typing the command <code>virt-manager</code></li>
+</ol>
-The purpose of the "init" process is to start and stop other programs in a particular sequence according to the file called /etc/inittab and other files in various directories under the /etc/rc.d/init.d/ directory.
+{{Admon/important|Run virt-manager as a regular user|Running virt-manager as root may not work due to configuration issues.}}
-A great explanation of init and its place in the boot process can be found here. http://www.kevinboone.com/boot.html
+== Investigation 1: Installing from a Live Disc ==
-At any given time on a Linux/Unix system, a pre-defined set of base processes are running according to the so-called "runlevel" of the system which can be set by the init process. The init process gets the value for the system's runlevel from its main configuration file /etc/inittab. A system's runlevel can also be changed by using the init or telinit commands (they are equivalent in Linux). A system's runlevel is usually denoted with a number from 0 through 6; different systems may have a different set of base processes for each "runlevel", but these descriptions usually apply:
+{{Admon/tip|Using an Image instead of a Live Disc|It is recommended that you perform this installation from your Fedora LIVE CD. As a matter of interest (for future reference), it is possible to install directly from the ISO file you used to burn your Live CD. There are many Internet tutorials that show the individual how to perform that task.}}
-- Shutdown
+==== Introduction ====
-- Single user maintenence mode
-- Network operation, text mode display only
-- Network operation, full graphical user interface
-- Reboot
-** Note not all distributions use the same runlevel configurations. Debian and Ubuntu based distro's are different.
+In this investigation, you will install Fedora from your live disc, and observe the differences between this type of installation and the DVD installation previously performed.
-To find out the value of the runlevel your GNU/Linux system goes into after boot, enter the command: grep initdefault /etc/inittab
+==== VM Details ====
-You should get a single line containing ":" as the field delimiter. The second field stores the value of the runlevel the init process will use after a reboot. Record the output in your log book.
+* '''Name:''' fedora1
+* '''Boot media:''' Fedora Live CD
+* '''Installation source:''' Fedora Live CD
+* '''Memory:''' 768MB
+* '''Disk space:''' 10GB
+* '''CPUs:''' 1
-A list of processes that should be running at a given runlevel can be found in the directory /etc/rc.d/rcX.d where X is the runlevel.
+==== Screen-Shot Thumbnail Reference ====
-Do a directory listing of that directory and study what files are in there. Pay attention to the first three characters of each file name. They have special meaning to the system. Record your observation in your log book.
+{{Admon/note|Virtual Machine Screen Shots Thumbnails|While performing the Virtual Machine setup, click on the thumbnails below to provide a '''"visual reference"''' while performing this section.
+}}
-Make a backup of the file /etc/inittab with the command:  cp /etc/inittab /etc/inittab.original
+{|cellpadding="8" width="100%"
-Edit the file /etc/inittab and change the default runlevel to 3. Save the change and reboot your system.
+|[[Image:Virt-manager1.png|thumb|125px| '''Virtual Machine Manager:''' Create a New Virtual Machine]]
+|[[Image:Virt-manager2.png|thumb|100px|'''Step 1 of 5:''' Create a New Virtual Machine ]]
+|[[Image:virtual-manager3.png|thumb|100px|'''Step 2 of 5:''' Create a New Virtual Machine ]]
+|[[Image:virtual-manager4.png|thumb|100px|'''Step 3 of 5:''' Create a New Virtual Machine ]]
+|[[Image:virtual-manager5.png|thumb|100px|'''Step 4 of 5:''' Create a New Virtual Machine ]]
+|[[Image:virtual-manager6.png|thumb|100px|'''Step 5 of 5:''' Create a New Virtual Machine ]]
+|}
-Reboot your system. After the reboot, you should get a "Text Login Screen". Login with your Learn account and type startx at the command prompt.
+==== Steps ====
-Describe what happens in your log book.
-Enter the command: runlevel
+# In the Virtual Machine Manger, click on the icon to ''Create a Virtual Machine'' in the upper-left corner: <br />(refer to '''Virtual Machine Manager''' thumbnail above).
-This shows the previous and current runlevel. Record the values in your book.
+# A window will appear with the title ''New VM''. There are five steps to be completed; click Forward after each step:
-Answer the Investigation 3 question.
+# '''Step 1 of 5:''' Enter the virtual machine (called '''fedora1''') name and select '''Local install media'''  (refer to ''Step 1 of 5'' thumbnail above).
+# '''Step 2 of 5:''' '''Insert the CDROM or DVD containing the Fedora 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 '''Fedora 17''' (refer to ''Step 2 of 5'' thumbnail above).
+<!-- {{Admon/tip|Using an ISO image|Instead of using a physical CD or DVD, you can use an ISO image of a CD or DVD. The virtualization software will make this ISO image appear like an actual CD within the virtual machine. Because hard disks are faster then optical discs, this will work faster than an actual CD/DVD.}}{{Admon/note|Choosing the operating system type and version|The purpose of the ''OS type'' and ''Version'' fields is to fine-tune some of the virtual machine settings for best performance. The VM will work even if these are set incorrectly.}} -->
+# '''Step 3 of 5:''' Set the memory to '''768 MB''' and the number of CPUs to '''1''' (refer to ''Step 3 of 5'' thumbnail above).
+# '''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''' (refer to ''Step 4 of 5'' thumbnail above).
+# '''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''' (refer to ''Step 5 of 5'' thumbnail above).
-Investigation 4: What is the network configuration?
+{{Admon/important|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.|'''}}
-To check the network configuration settings obtained from the DHCP server, run the following commands:
-ifconfig
-route
-netstat -rn
-nslookup (at the > prompt, enter the word "server" (do not type the quotes) and record the output. Type exit to leave nslookup).
-Describe the output in your log book. Record the following information from the outputs into your lab log:
+{{Admon/note|Fedora LIVE CD Install Screen Shots Thumbnails|While performing the Fedora 17 LIVE CD install, click on the thumbnails below to provide a '''"visual reference"''' while performing this particular Fedora installation.
-MAC address (physical or hardware address) of the ethernet network interface
+}}
-The IP address (logical address) assigned by the DHCP server
-The default route (gateway)
-The DNS nameserver
-Answer the Investigation 4 question.
+{|cellpadding="8" width="100%"
-Investigation 5: How do You Secure the Grub Boot Loader?
+|[[Image:fedoralive1.png|thumb|100px| The Virtual Machine will now start.]]
-By default, the Grub boot loader allows anyone with access to the computer at boot time to set the runlevel, or change the boot parameters, which can allow them to influence the init process and which kernel image is loaded. Anyone with access to the boot prompt can therefore bypass security controls and control which software is loaded. For example, rebooting to runlevel 1, known as single user mode, gives the user root priveleges without the need for a password! Obviously, giving a non-administrator this much control can be dangerous, and it is wise to protect the boot loader with a secure password.
+|[[Image:failedtoload.png|thumb|140px| '''Ignore and close the "Failed To Load" dialog box'''. Search for the panel on the upper-left-hand side of the screen.]]
+|[[Image:fedoralive2.png|thumb|140px|Login to the VM and double-click:<br /> '''Applications'''<br />>'''System Tools'''<br />>'''Install to Hard Disk'''.]]
+|[[Image:selectstorage1.png|thumb|100px|Select '''Specialized Storage Devices''']]
+|[[Image:selectstorage2.png|thumb|100px|Select '''Virtio Block Device'''.]]
+|[[Image:finishcdinstall.png|thumb|100px|You will get the ''Firstboot'' configuration questions during the boot process.]]
+|}
+<ol>
+ <li value="8">'''The virtual machine will now start'''. Select the default menu item labelled: '''Start Fedora 17'''. 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.</li>
+</ol>
-We will need to choose a password, encrypt with the grub programs hash utility(called md5crypt, and add the encrypted hash of your password to the grub configuration file, /etc/grub.conf
+<ol>
-First, choose a suitable password.
+ <li value="9">Login to the VM and click: '''Applications'''>'''System Tools'''>'''Install to Hard Drive'''. The installation program, similar to the one used when installing Fedora 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.</li>
+</ol>
-Do not forget it, or you will not be able to change boot parameters when you boot your system! If you need to write it down, put it in a safe place, where no one will be able to tell what it is for.
+{{Admon/note|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.
-Open the grub program by typing the command: grub
+}}
+<ol>
+ <li value="10">During the installation process, when prompted for a storage device, first select '''Specialized Storage Devices''', and then select the '''Virtio Block Device''' option.</li>
+ <li>When prompted for the hostname, enter '''fedora1''', and when prompted for the timezone, select '''Toronto - Eastern Time Ontario''', and 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'''.</li>
+ <li>When the installation is complete, click on the '''reboot''' button at the bottom right-hand corner of the screen.</li>
+</ol>
-At the grub prompt, type in the command: md5crypt
+<ol>
-When prompted for a password, carefully type in your password. The program will display the encrypted hash of your password. Carefully write this down.
+ <li value="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 optionally send the hardware profile to the Fedora Project). Create a user with the same name as your Matrix account.</li>
+ <li>Login using the new user account.</li>
+</ol>
-Type the command: quit  to exit the grub program.
+{{Admon/note|Network / Service Considerations|Please perform the tasks below in order allow these Fedora systems to be able to communicate with each other. '''Failure to properly perform these operations can cause problems in future labs'''.|
+}}
-Open the grub configuration file, /etc/grub.conf , for editing.
+<ol>
-This file is actually linked to /boot/grub/grub.conf.
+ <li value="15">Enable SSH access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):<br /> <code>service sshd start; chkconfig sshd on</code></li>
+ <li>Find out the IP address of your virtual machine: <code>ifconfig eth0</code> </li>
+ <li>Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine:<br />  <code>iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT</code></li>
+ <li>Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): <code>ssh ''IPaddress''</code></li>
+</ol>
-Carefully add the line
+{{Admon/tip|Switch to Virtual Machine Manager Window|If you are currently in a Virtual machine, but want to switch to the Virtual Machine Manager Window, simply click '''Activities'''> '''Select the Virtual Machine manager window'''.}}
-password --md5 password-hash        (note: password-hash is the hash you generated with md5crypt)
+'''Answer the Investigation 1 observations / questions in your lab log book.'''
-to the file between the splashimage line and the title line. If there are other lines there, there is no need to remove them. Just insert your password line as a new line.
+== Investigation 2: Installing from the Network ==
-It should look something like this:
+{{Admon/tip|Authenticate to the network|The rest of this lab uses network access.''' Be sure to authenticate to the network using your browser before proceeding'''.}}
- ...
+=== Introduction ===
-splashimage=(hd0,0)/boot/grub/splash.xpm.gz
-password --md5 $1$jxcdN0$hVHViq1aiPf8FziuGJGZp0
-hiddenmenu
-title Fedora
-...
-You can find a more complete sample of this file here.
+It is possible to install Fedora entirely from the network. In this investigation, you will install Fedora from a webserver on Seneca's LAN.
-Make sure you have not made a mistake. What you type in must match exactly the output from the md5crypt command.
+==== VM details ====
-While you are editing the file you should also increase the timeout for grub to automatically boot the default OS. Edit the line timeout=0 to timeout=5 to give us more time to interrupt the process.
+* '''Name:''' fedora2
+* '''Boot media:''' Network installation
+* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/
+* '''Memory:''' 1024MB
+* '''Disk space:''' 20GB
+* '''CPUs:''' 1
-Save the file and exit. Your Grub boot loader is now password protected.
+==== Steps ====
+# Create the VM (called '''fedora2''') as you did with the ''fedora1'' virtual machine, except:
+#* In '''step 1 of 5''', set the installation type to '''Network Install (HTTP, FTP, or NFS)'''.
+#* In '''step 2 of 5''', provide the location of the software source by providing the URL http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/
+#* In '''step 2 of 5''', set the ''OS Type'' to '''Linux''' and ''Version'' to '''Fedora 17'''.
+# Observe the boot process. How is it different from booting from an optical disc (CD/DVD)?
+# Start the installation process (make certain to use information in the ''VM Details'' section above).
+# 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).
+# On the software selection screen, select '''Graphical Desktop'''.
+# '''On the same screen, select the "Fedora 17 - x86_64" and the "Fedora 17 - x86_64 - Updates". Leave "Installation Repo" selected. ''DO NOT'' enable the "Test Updates" repository'''.
+# 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'''.
-Make sure the configuration file is owned by root, and set the permissions so only root can read and write.
+'''Answer the Investigation 2 observations / questions in your lab log book.'''
-Find the section of this article that explains how to change the runlevel at boot time, and read it. Reboot your system, trying to change to runlevel 1 from the boot prompt, and see if the password protection worked.
+== Investigation 3: Installing from the Network using Kickstart ==
- From now on, when you want to change boot parameters when you boot, you must type lowercase
-    p
+=== Introduction ===
- at the boot prompt and enter the required password.
+When Fedora is installed using the techniques you have used so far, the user is asked a number of questions. In some situations, it is better to provide the answers to these questions in a file rather than answer them individually. This type of file is called a ''kickstart'' file.
-Completing the Lab
+In this investigation, a kickstart file is provided for you. You can also create or modify a kickstart file using a regular text editor or a graphical tool.
-Check off the following items and sign your name before asking your instructor to check your lab:
+==== VM details ====
-I have completed the following tasks in full:
-[  ] Task 1 - Install GNU/Linux Workstation using Fedora 10
+* '''Name:''' fedora3
+* '''Boot media:''' Network installation
+* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/
+* '''Kickstart location:''' http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora17-kickstart.cfg
+* '''Memory:''' 1024MB
+* '''Disk space:''' 15GB
+* '''CPUs:''' 1
-[  ] Task 2 - Collect system information after installation.
+==== Steps ====
+# Create the VM as you did with the ''fedora2'' virtual machine, specifying a network install as before, except:
+#* In step 2 of 5, after entering the URL for the installation source, click on the '''URL Options''' control.
+#* Enter the Kickstart URL: http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora17-kickstart.cfg
+# Observe the installation. How is it different from booting from an optical disc (CD/DVD)?
+# Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations.
+# What happens when the installation is finished?
+# '''Take a look at the kickstart file (using the URL you entered) to <u>determine</u> the root password as well as the name and password for the first user account'''.
+# 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'''.
-[  ] Task 3 - Customize and configure boot time environment
+'''Answer the Investigation 3 observations / questions in your lab log book.'''
-[  ] Task 4 - Collect network information
+== Investigation 4: Updating and Comparing the VMs ==
-[  ] Task 5 - Password protect Grub Bootloader
-Student Signature: _____________________    Date: ________________
+# In each VM, run this command: <code>yum update</code>
-Arrange evidence for each of these items on your screen, then ask your instructor each item:
+# 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?
-[  ] Grub is password protected.
+Complete the following table (and transfer into your lab2 log-book notes):
-[  ] Can login with student's "learn" account
+{|border="1" width="100%" cellpadding="5"
+|-
+! ||f17host||fedora1||fedora2||fedora3
+|-
+|'''Installation Method'''||Installation Disc||Live Disc||Network Installation||Network Installation + Kickstart
+|-
+|'''Packages Installed'''|| || || ||
+|-
+|'''Updates Installed immediately after installation'''|| || || ||
+|-
+|'''Software could be selected during installation'''|| || || ||
+|-
+|'''Disk layout could be selected during installation'''|| || || ||
+|-
+|'''No questions asked during installation'''|| || || ||
+|-
+|'''Total installation time''' (after installation questions)|| || || ||
+|-
+|'''Amount of disk space used'''|| || || ||
+|-
+|'''Questions asked during first boot'''|| || || ||
+|-
+|'''Advantages of this type of installation'''|| || || ||
+|-
+|'''Disadvantages of this type of installation'''|| || || ||
+|-
+|'''This type of installation is recommended for...'''|| || || ||
+|}
-[  ] Has all the mount points
+== Investigation 5: Managing Virtual Machines from the Command Line ==
-[  ] Has the package count
+{{Admon/note|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.}}
-[  ] Has edited the default runlevel
+# Start the ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.
+# Switch to the f19host machine, and open a shell terminal.
+# Enter these commands into your f19host machine and note the result:
+#* <code>'''virsh list'''</code>
+#* <code>'''virsh list --all'''</code>
+#* <code>'''virsh list --inactive'''</code>
+# Now, shut-down your fedora1 VM normally, and close the fedora1 VM window. Make certain NOT to close the Virtual Machine Manager main window.
+# Switch to your terminal and issue the command: <code>'''virsh start fedora1'''</code>
+# Check to see if your fedora1 VM is now running.
+# Switch to the terminal and issue<code>'''virsh list --all'''</code> and confirm the status of the fedora1 VM.
+# There are other commands that can be used (such as suspend, or shutdown). The "shutdown" command may not always work since it sends a request to "shutdown virtual machine gracefully", but may not always work. Why do you think it is useful to have commands to manipulate VMs?
-[  ] Has the correct IP address and MAC address
+{{Admon/note|Virtual Machine Does not Shutdown from Command|If the Virtual machine fails to shutdown from the <code>virsh shutdown</code> 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 cord out of the wall on a physical machine!|}}
-[  ] Find out the default route (gateway)
-[  ] IP of the DNS name server
+'''Answer the Investigation 5 observations / questions in your lab log book.'''
-Instructor Signature: _____________________    Date: ________________
+== Investigation 6: How do I backup a virtual machine? ==
-Preparing for the Quizzes
+{{Admon/important|Backing up VMs|There are two general processes in order to back up your images:<ol><li>'''Compressing your images''' (also recommended to backup up to external storage USB Key) using the '''gzip''' command.</li><li>'''Backup the VM xlm 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).</li></ol><br />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.<br />Failure to take the time to make and confirm backups can result in loss of lab work for the student!|}}
-How many packages were installed?
+# Shut down all of the virtual machines.
+# Change to the directory <code>/var/lib/libvirt/images/</code>. Note the size of the files in this directory. What do these files contain?
+# Make a compressed backup of the <code>fedora3.img</code> file to your home directory with this command: <code>'''gzip < fedora3.img > ~YourUserId/fedora3.img.backup.gz'''</code><br />('''Note: Make certain to use the redirection signs "<" and ">" properly in the command!''')
+{{Admon/caution| Make sure the backup is successful!|If there are any error messages, '''DO NOT''' proceed past this point. You're going to destroy your fedora3 virtual machine and restore it using the backup you have created -- if there are any problems with the backup, you will not have a working virtual machine, and will have to re-install it.}}
+<ol>
+ <li value="4">Compare the size of the compressed and original files.</li>
+ <li>Start the '''''fedora3''''' VM.</li>
+ <li>'''Make certain that you are in your fedora VM and <u>not</u> in your Fedora main system!'''</li>
+ <li>Wreck <u>only</u> your fedora 3 system! Try this command inside the fedora3 virtual machine: <code>'''rm -rf /*'''</code></li>
+ <li>Shut down the VM. If you tried to start the Fedora3 VM, it would not boot since all system files have been removed!</li>
+ <li>Restore the original image from the backup in your home directory by typing this command: <code>'''gunzip < ~YourUserId/fedora3.img.backup.gz > fedora3.img'''</code></li>
+ <li>Restart the VM. Is it working normally?</li>
+  <li>Create compressed backups of your other virtual machines.</li>
+</ol>
+<ol>
+<li value="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 fedora 3 xml configuration file, and prove that a "clone" can be added to your list.Please perform the following step:<ol type="a">
+<li>Verify that you are in the directory: <code>/var/lib/libvirt/images/</code>.</li>
+ <li>Execute the following command: <code>virsh dumpxml fedora3 >fedora3.xml</code></li>
+ <li>Examine the file <code>fedora3.xml</code>. What does it contain? What format is it in?</li>
+ <li>Make a copy of <code>fedora3.xml</code> called <code>fedora3a.xml</code>.</li>
+ <li>Edit the file <code>fedora3a.xml</code>, making the following changes:</li>
+</ol>
+::* Change the name (in the file, not the file name) to <code>fedora3a</code>
+::* 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.
+<ol type="a" >
+ <li value="6">Issue this command: <code>virsh define fedora3a.xml</code>
+ <li>Issue the command <code>virsh list --all</code> and record any changes.
+ <li>Issue the command: <code>virsh undefine fedora3a</code>
+ <li>List all of the virtual machines again, and note any changes. </li></ol>
+ <li>For the remainder of these labs, it is assumed that you will backup <u>'''both'''</u> the images and xml configuration files for <u>'''all'''</u> 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...</li>
+<li>Answer this question in your log book:</li>
+</ol>
+::* In order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?
-How many files (correct to the nearest hundred) were installed?
+{{Admon/important|Backing up VMs|It is essential to back up your VMs at the end of each lab, so you can easily restore them if something goes wrong in the next lab.}}
-How many mount points were used?
+{{Admon/tip|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.}}
-How many users were created automatically on your system (do not count your learn account)?
+'''Answer the Investigation 6 observations / questions in your lab log book.'''
-What is your learn account's UID and GID?
+== Investigation 7: Kickstart Files ==
-What is your learn account's home directory?
+{{Admon/tip|SSHD and Firewall|If you have restarted your virtual machine ''fedora1'', the sshd server you started in investigation 1 (step 15) will no longer be running. In addition, the firewall will have reverted to its original state. In order to use '''scp''', below, you will need to restart ssh and adjust the firewall again.<br /><br />If students cannot backup their kickstart files using the '''scp''' command, they can use a web-browser to access their Seneca e-mail with attachment (copy kickstart file to their home directory first!). For the text-based Linux system "fedora3", students can use the '''mail''' command (refer to the man command to learn how to send e-mail attachments). }}
-What is the home directory for the user "root"?
+When you perform a non-Kickstart installation, the installation program creates a Kickstart file in the <code>/root</code> directory for reference.
-How do you determine the host name of your GNU/Linux workstation?
+# Obtain the kickstart files for all four of your installations (your disk pack ''f17host'', plus the ''fedora1'', ''fedora2'', and ''fedora3'' virtual machines).
+# To prevent confusion, copy your kickstart files to kickstart filenames that describe their purpose (eg. kickstart_host, kickstart_fedora1, kickstart_fedora2, etc...)
+# Copy them all to your f17host system (tip: use <code>scp</code>), or use the hint in the tip box above to send via e-mail.
+# Compare these files. What are the differences? Similarities? (Tip: you may want to use tools such as <code>sdiff</code> to help with the comparison).
+# How could you use the kickstart file produced by the installation program to perform additional, identical installations?
-What command can display the NIC's MAC address?
+'''Answer the Investigation 7 observations / questions in your lab log book.'''
-Which file contains the default "runlevel" value for your GNU/Linux workstation?
+= Completing the Lab =
+'''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.
+# Four kickstart files.
+# All virtual machines fully updated.
+# All virtual machines backed up.
+# Installation comparison table filled in.
+# Lab Logbook (lab2) notes filled-in.
+= Preparing for Quizzes =
+# What is the name of the Fedora installation program?
+# 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?
+# Which type of installation works best for confirming compatibility with hardware before installation? Why?
+# Which type of installation works best for installing large numbers of computers? Why?
+# What factors affect installation time?
+# How can you reduce the number of software updates required immediately after installation?
+# Why would you enable additional repositories during installation?
+# What does the file <code>/root/anaconda-ks.cfg</code> contain, and how is it created?
+# How do you start and stop virtual machines?
+# How do you SSH into your virtual machines?
+# What is the purpose of and relationship between these pieces of software?
+#* libvirt
+#* libvirtd
+#* virsh
+#* virt-manager
+#* virt-install
+#* kvm
+# The kickstart installation (fedora3) was a network installation. Can a kickstart file be used with a DVD installation?
+# The kickstart installation (fedora3) was fairly fast. Why? Under what circumstances would it take a long time, even on a fast network?
+# What other types of installation sources are possible (besides Live Disc, Installation Disc, and Network?)

Difference between revisions of "OPS235 Lab 2 - Fedora17"

Latest revision as of 11:29, 24 September 2018

Contents

Fedora 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3)

Introduction

Objectives

Required Materials (Bring to All Labs)

Prerequisites

Linux Command Online Reference

Resources on the Web

Performing Lab 2

Preparation

Investigation 1: Installing from a Live Disc

Introduction

VM Details

Screen-Shot Thumbnail Reference

Steps

Investigation 2: Installing from the Network

Introduction

VM details

Steps

Investigation 3: Installing from the Network using Kickstart

Introduction

VM details

Steps

Investigation 4: Updating and Comparing the VMs

Investigation 5: Managing Virtual Machines from the Command Line

Investigation 6: How do I backup a virtual machine?

Investigation 7: Kickstart Files

Completing the Lab

Preparing for Quizzes

Navigation menu

Search