[[Category:OPS235]][[Category:OPS235 Labs]]{{Admon/important|Unbind your MAC address|Before proceeding with this lab, [[Unbinding MAC Addresses on Fedora|unbind your MAC address]].}}= State when starting Lab 3 =
= Using Virtual Machines =At this point, having completed [[OPS235 Lab 3|Lab 3]] you should have <u>roughly</u> the following disk storage setup:<br />('''Note:''' These results are output from the '''vgs''', '''lvs''', and '''pvs''' commands within each virtual machine. You will be using these commands in the following lab investigations)<br /><br />
== Objectives ==* '''fedora1'''
* Understand Virtualization This VM has a GUI and no free space in the VG. VG #PV #LV #SN Attr VSize VFree vg_fedora1 1 2 0 wz--n- 9.80G 0 LV VG Attr LSize * Use KVM virtualization on Fedora lv_root vg_fedora1 -wi-ao 8.83G * Use a variety of installation methods lv_swap vg_fedora1 -wi-ao 992.00M ** Live Image Installation ** Network Installation PV VG Fmt Attr PSize PFree** Kickstart Installation /dev/vda2 vg_fedora1 lvm2 a- 9.80G 0
== Reference Material ==* '''fedora2'''
Virtualization This VM has a GUI and free space in the VG. VG #PV #LV #SN Attr VSize VFree* [http://docs vg_fedora2 1 3 0 wz--n- 14.80G 4.fedoraproject07G LV VG Attr LSize lv_home vg_fedora2 -wi-ao 1.org/virtualization95G lv_root vg_fedora2 -wi-ao 7.81G lv_swap vg_fedora2 -wi-guideao 992.00M PV VG Fmt Attr PSize PFree /f13dev/envda2 vg_fedora2 lvm2 a-US/html/ Fedora 13 Virtualization Guide] 14.80G 4.07G
Installation Methods* Live Image Installation** [http://docs.fedoraproject.org/readme-live-image/en-US.html Fedora 13 Live Image Guide]** [http://docs.fedoraproject.org/installation-quick-start-guide/f13/en-US/html/ Fedora 13 Installation Quick Start Guide]* Network Installation** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ Fedora 13 Installation Guide]*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/s1-steps-network-installs-x86.html Preparing for a Network Installation]*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/s1-begininstall-perform-nfs-x86.html Performing a Network Installation]* Kickstart Installation** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ Fedora 13 Installation Guide]*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/sn-automating-installation.html Automating the Installation with Kickstart]*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ch-kickstart2.html Kickstart Installations]*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ch-redhat-config-kickstart.html Kickstart Configurator]'''fedora3'''
== Required Materials == This VM has no GUI installed. VG #PV #LV #SN Attr VSize VFree vg_fedora3 1 3 0 wz--n- 9.80G 3.83G LV VG Attr LSize lv_home vg_fedora3 -wi-ao 1.00G lv_root vg_fedora3 -wi-ao 4.00G lv_swap vg_fedora3 -wi-ao 992.00M PV VG Fmt Attr PSize PFree /dev/vda2 vg_fedora3 lvm2 a- 9.80G 3.83G
* Removable '''f13host (i.e. "disk pack with Fedora installed (see [[OPS235 Lab 2|Lab 2]]").* Fedora 13 x86_64 Live CD.'''
{{Admon Four PVs, minimum VG size 60G Single filesystem on vg_main/tip|Performing this Lab off the Seneca network|This lab uses servers which are on the Seneca network and which are not root, size 50G At least 10G available from other locations space in VG 20% of disk space unallocated to any partition (such as your homemin 15G). 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 must be done at Seneca.}}
== Introduction =Logical Volume Management =
A {{Admon/note|Recovering VMs|'''Most of these investigations will take place in you virtual machinemachines.''' is If you make a software simulation significant mistake, your virtual machine may not boot. Remember that you created backups of a computer which can be used as though it were actual hardware. It's possible to run multiple your virtual machines on one computerin Lab 3, reducing hardware requirements and introducing flexibilityyou can '''restore them if something goes wrong'''. 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.== Resources ==
In '''Please read this lab, you will create three virtual machines. This also gives you page to get an opportunity overview of LVM:'''<br /><br />('''Note:''' It is recommended to return to experiment with different ways of installing Fedora. Later in this course you will install another operating system distribution in guide as a virtual machinesreference when performing the next several investigations).<br /><br />* [[Logical Volume Management]]
You have already used == Investigation 1: How are LVMs are managed using system-config-lvm? =='''Perform this investigation on the VM named ''<u>fedora2</u>''.'''[[Image:Ops235_lab4_1.png|thumb|right|Screenshot of system-config-lvm in Fedora. Click to enlarge.]]# Let's learn to manage or administer our LVM graphically for our Virtual Machine ('''Fedora2''').<br />Fedora provides a Fedora live disc tool called <code>system-config-lvm</code> to graphically administer LVM. It will appear on the menu as System>Administration>Logical Volume Management. Verify that this package is present, and an installation discinstall it if required (<code>yum install system-config-lvm</code>). In both cases, # Use this tool to determine the current LVM configuration by clicking on the appropriate element and reading the properties in the right-hand panel -- write down the answers:#* What are the names and sizes of the PVs?#* What is the name and size of the VG?#* What are the names and sizes of the LVs?#* Is there any space in the boot media (VG which you used is not allocated to load a LV?# Increase the size of the installation software) and home filesystem to 2 GB:## Click on the installation source (where LV containing the software that got installed came from) were home filesystem.## Click on ''Edit Properties''.## Change the samesize to 2 GB and click ''Ok''.# Create a new 2G LV (LV Properties: they CDlinear) containing an ext4 filesystem named lv_archive and mount it at /DVD provided botharchive## Click on ''Logical View''. However## Click the ''Create New Logical Volume''.## Set the name, size, filesystem, and mount point.## Click ''Ok''.# Backup <code>/etc</code> into <code>/archive</code>#* Copy the Fedora files in /etc into the filesystem mounted at <code>/archive</code> (and most other Linux distributions) permits you use the graphical tools or the command line. If using cp, remember to use any combination the -R option).# Shrink the size of boot media and installation media:<code>lv_archive</code> to 1 GB.# Try shrinking <code>/</code> -- what happens? Why?
* Boot Media== Investigation 2: How are LVMs are managed using Command-Line Tools ==** CD or DVD# You are going to repeat the same LVM management operations (as your did with the ''fedora2'' VM), but you will using command-line tools in the '''fedora 3''' VM. Since the fedora3 VM only operates in command-line mode, you will need to refer to the '''"Logical Volume Management"''' link above.** Hard disk# Write down the exact commands used at each step, and record appropriate command output:** USB flash drive## Determine the current LVM configuration using the <code>pvs</code>, <code>vgs</code>, and <code>lvs</code> command.** Network boot## Grow the home filesystem to 2G using the command <code>lvextend</code> and <code>resize2fs</code>.## Create a new 2G LV containing an ext4 filesystem and mount it at /archive (use <code>lvcreate</code>, <code>mkfs</code>, <code>mount</code>, edit the file <code>/etc/fstab</code>, and then reboot to confirm automatic mount).## Copy the contents of <code>/etc</code> into <code>/archive</code>.## Shrink <code>lv_archive</code> to 1G (use <code>umount</code>, <code>resize2fs</code>, <code>lvreduce</code>, and <code>mount</code>)
* Installation source== Investigation 3: How can a PV be added to an existing VG? ==** CD '''Add an additional 2 GB virtual disk to your ''<u>fedora1</u>'' system, and use it as an additional physical volume:'''# Start <code>virt-manager</code>.# Shutdown ''fedora1'' if it is running.# Open the console window for ''fedora1''.# Select the menu option View>Details.# Click ''Add Hardware'' button at the bottom left-hand corner.# In the ''Adding new virtual hardware'' window that appears, select a Hardware Type of ''"storage"'' and click ''"Forward"''.# Make certain option "Managed or DVDother existing storage" is selected. Click on the ''Browse'' button, then click on ''New Volume''.# Give the new virtual disk file a name of <code>fedora1b</code>, a format of ''raw'', with a ''Max Capacity'' and ''Allocation'' of 2000 MB. Click ''Finish''.# Select the new virtual disk file ''fedora1b.img'' and click ''Choose Volume''.# Select a device type of ''Virtio Disk''.# Finish creating the new virtual disk by clicking ''Forward'' and then ''Finish''.# Boot the system. You should now have both <code>/dev/vda</code> and <code>/dev/vdb</code>.** Hard # Record the size of the volume group and the amount of free space <span class="plainlinks">[http://www.inleds.com/products/?cid=2<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"> led downlight singapore</span>](Hint: use a command that you learned in a previous lab).# Partition /dev/vdb with a single partition that fills the whole disk.** USB flash drive# Check the messages printed when <code>fdisk</code> exits -- you may need to reboot the system in order for the new partition table to take effect.** Network HTTP or NFS software repository# Run this command to format the physical volume: <code>pvcreate /dev/''vdb1''</code># Add the new physical volume to the existing volume group: <code>vgextend ''nameOfVolumeGroup'' /dev/vdb1</code># Verify that the volume group is larger and has more free space.
== Instructions =={{Admon/note|Think!|The next part of this investigation requires some research, thought, and creativity.}}'''Using that additional space, create a separate filesystem for <code>/home</code>:'''# Create the logical volume <code>lv_home</code> (1G ext4)# Find a way to move the contents of <code>/home</code> onto it.# Change your system configuration so that the new filesystem is mounted on <code>/home</code> from now on.
=== Preparation ==={{Admon/tip|SELinux relabelling may be required|Your system may report that the files are not present in the new /home filesystem when they are clearly there. This is due to the Security-Enhanced Linux system (SELinux) preventing access to the files, because the files were tampered with (moved) and are no longer recognized as home directory content. You can fix this problem by restoring the file context labels so that SELinux accepts the files as valid home directory content: <code>restorecon -r /home</code>}}
{{Admon/tip|Update your Fedora Installation|It== Investigation 4: How can I use LVM to manage storage on my disk pack? =='''s a good idea to ensure that On your Fedora installation is fully updated before proceeding. You can update your system with the graphical tool located on the menu at >System>Administration>Software Update (or type the command <codeu>gpk-update-viewf13host</codeu>(i.e. "disk pack"), or by typing either using your choice of these commands: <code>pkcon update<the GUI and/code> or <code>yum update</code>}}command-line tools:'''# Create a new logical partition ('''NOT a logical volume!''') - minimum 5G, leaving at least 10G free space in the extended partition.# Add that partition as a PV into the existing VG (using the commands you used in the previous investigation).# Grow the root filesystem to fill the available space.
# 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.# Start the virtualization service: <code>service libvirtd start</code># 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># Start the graphical tool by selecting the menu option Applications>System Tools>Virtual Machine Manager or by typing the command <code>virt-manager</code>= Package Management =
{{Admon/important|Run virt-manager as a regular user|Running virt-manager as root may not work due to configuration issues.}}== Investigation 5: How do you query the RPM database? ==
{{Admon/caution|Reboot your fedora host|There appears RPM maintains a database of installed software. This information is very useful to be an issue system administrators. In Lab 3, you queried that database using RPM with supplying your VM's with a dynamic IP unless the host is restarted after installing "Virtualization"-q argument. '''Reboot now to avoid this problem.'''}}When you query the RPM database, you can separately specify:* Which packages you want information about, using a select-option* What information you want about those packages, using a query-option
=== Investigation 1Steps: Installing from a Live Disc ===
1. Using information from the man page for <code>rpm</code>, fill in this information:{{Admon/tip|Using an Image instead of width="100%" border="1"|-!Option!Meaning!Is this a select-option or a Live Discquery-option?|-|If you do not have -a Live Disc available|Select all packages|select-option|-| -l| | |-| -p ''filename'''|Select this uninstalled package| |-| -i|Show the package license, packager, URL, description, you can download the and other general information.iso image file from http://belmont.senecac.on.ca/fedora/releases/13/Live/x86_64/Fedora| |-| -13f '''filename'''| | |-x86_64|'''packagename'''|Select just this package|select-Live.iso and then use the iso image file in place of the physical disk.}option|}
==== Introduction ====Make sure that your lab notes answer the Investigation 5 question.
In this investigation, == Investigation 6: How do you will install Fedora from your live disc, and observe the differences between this type of installation and the DVD installation previously performed.remove software with RPM? ==
==== VM Details ====# Change to the directory on your Installation DVD containing the file: <code>lynx-2.8.7-2.fc13.x86_64.rpm</code># Execute this command: <code>rpm -i lynx-2.8.7-2.fc13.x86_64.rpm</code># Issue an RPM query to check that lynx is installed.# Issue this command: <code>rpm -e lynx</code># Issue an RPM query to verify that lynx is no longer installed.# Issue this command: <code>rpm -i BackupPC-3.1.0-13.fc13.noarch.rpm</code> and note the result
* Name: fedora1* Boot media: Fedora Live CD* Installation source: Fedora Live CD* Memory: 512MB* Disk space: 10GB* CPUs: 1Answer the Investigation 6 question.
==== Steps ==Investigation 7: How do you install and remove software with ''yum''? ==
{{Admon/note|Fedora 12 Screen ShotsInternet Connection|The following screen shots are from Fedora 12. The Fedora 13 version of virt-manager varies slightly -- there are In order for yum to work you require a few extra controls on some dialogs which may be ignoredconnection to the Internet.Establish this connection by using the browser to log into SeneNET}}
# In the Virtual Machine Manger, click on the icon Change to ''Create a Virtual Machine'' in the upper-left corner: <br />[[Image:Virt-manager1.png]]# 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 name and select ''Local install media''.<br />[[Image:Virt-manager2.png]]# 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 it as the install media. Set the ''OS type'' to Linux and the ''Version'' to Fedora 13.<br />[[Image:Virt-manager3.png]]<!-- {{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 512 MB and the number of CPUs to 1.<br />[[Image:Virt-manager4.png]]# 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''.<br />[[Image:Virt-manager5.png]]# 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''.<br />[[Image:Virt-manager6.png]]# The virtual machine will now start. You will see a window which displays the virtual video card from the VM. It's important to note that the VM can (and often will) run even when this display is not present. 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 double-click on the ''Install to Hard Drive'' icon. The installation program, similar to the one used when installing Fedora in Lab 2, will appear. You will get a warning at one point during the installation process that the disk "may need to be re-initialized" -- this is simply a warning that the virtual disk is completely blank, and it is safe to select ''Re-initialize drive''.# During the installation process, when prompted for the drive, select "Virtio Block Device", when prompted for the hostname, enter "fedora1", when prompted for the timezone, select ''America/Toronto'', 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.# When the installation is complete, select the menu option System>Shutdown to stop the Live Dischome directory.# Start the VM from its disk image 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.# Enable SSH access to your virtual machine with these commands: <code>service sshd start; chkconfig sshd on</code># Find out the IP address of your virtual machine: <code>ifconfig eth0</code># Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine: <code>iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT</code># Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): <code>ssh ''IPaddress''</code>
=== Investigation 2# Issue the command: <code>yum install BackupPC</code> and answer <code>y</code> to the question about installation.#* Where did ''yum'' get the BackupPC software?#* Why could ''yum'' install BackupPC when rpm couldn't?# Issue an RPM query to verify that BackupPC is installed.# Issue the command: <code>yum remove BackupPC</code># Issue an RPM query to verify that BackupPC is no longer installed.# Install <code>nled</code> using '''yum'''.# Issue this command: Installing from <code>yum info cups</code>#* Based on the Network ===result, do you think that cups is a useful package for your system? If not, try removing it.# Unused and unneeded software can present a security risk and ties up disk space needlessly. Find at least 4 other packages that you're not using on your system, and remove them. Be careful to ensure that removing those packages does not also remove other software that you do need.
{{Admon/tip|Authenticate to Answer the network|The rest of this lab uses network accessInvestigation 7 question. Be sure to authenticate to the network using your browser before proceeding.}}
==== Introduction ===User/Group Management =
It is possible to install Fedora entirely from the network. In this investigation, you will install Fedora from a webserver on Seneca's LAN.== Investigation 8: The /etc/passwd file ==
==== VM details ====# Look at the /etc/passwd file.# Make note of the contents of that file.# Read about the file: http://linux.die.net/man/5/passwd # Make sure you know what information each field contains.# Why do you think there are so many users?# Look at the names of the users. What do you think these user names represent? Are they people?# What is the numeric user ID (UID) of the root user?# The user IDs of real users (people) are different from the user IDs of system accounts. What is the pattern?
* Name== Investigation 9: fedora2* Boot media: Network installation* Installation source: http://belmont.senecac.on.ca/fedora/releases/13/Fedora/x86_64/os/* Memory: 512MB* Disk space: 15GB* CPUs: 1Adding users ==
==== Steps ====# Create the VM 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 URL http://belmont.senecac.on.ca/fedora/releases/13/Fedora{{Admon/x86_64/os/#* In step 2 of 5, set note|Use f13host|Perform these steps in the ''OS Type'f13host' to "Linux" and ''Version'' to "Fedora 13" # Observe the boot process. How is it different from booting from an optical disc (CD/DVD)?# Start the installation processsystem. When you get Due to the disk partitioning stepa configuration issue, enable these steps may not work normally in the checkbox labelled ''Review and modify partition layout''. On the next screen, change the logical volumes as follows:#* Reduce the size fedora1 virtual host (previous versions 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 ext3 or ext4 as the filesystem typethis lab used fedora1 for this investigation).# On the software selection screen, select ''Graphical Desktop''.# On the same screen, select the "Fedora 13 - x86_64" and the "Fedora 13 - 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.}}
# Read the man page for the useradd command.# Create a new user account for each of your pod mates, using their learn account name as a user name. Give each user a password.# Grep the /etc/passwd file for each of the new users.#* What is the home directory of each user?#* What group is each user in?#* What else do you know about each user?#* Where are the passwords stored?# Look at the man page for /etc/shadow using the command man 5 shadow#* Grep the /etc/shadow file for each of the new users.#* Make note of this information. # Create two new dummy users, ops235_1 and ops235_2.# Investigate the home directory of one of your new users.#* What files are there? Be sure to include hidden files.#* What do you think these files are used for <span class=== Investigation 3"plainlinks">?#* How does the operating system determine which files are created in a new home account? The answer can be found here: http://www.linuxhowtos.org/Tips%20and%20Tricks/using_skel.htm#* Look at the files (including hidden files) in the template directory referred to in the article. Compare them to what is in a home directory for a new user. What do you notice?#* Create a new file in this directory with the following command: Installing from <code>touch foo</code>#* Create a new user named foobar, with the Network using Kickstart ===option to automatically create a home directory.#* Look at the contents of foobar's home directory. What do you notice?# Be sure to record your observations in your lab notes.
==== Introduction ===={{Admon/note|Use fedora3|Perform these steps in the '''fedora3''' virtual machine.}}# Add your matrix account user to '''fedora3'''.
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.== Investigation 10: Managing Groups ==
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{{Admon/note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}}
==== VM details ====# Read the man page for the groupadd and groupdel commands.# Note which option allows you to set the Group ID number (GID) when you create a new group.# Examine the file /etc/group#* Which values of GID are reserved for system accounts?#* Which values of GID are reserved for non-system user accounts?#8 What is the lowest available GID number for non-system users?#* What is the default group name of a new user?#* Add a new group named ops235 with a GID of 600.#* You are angry at some irresponsible users on your system.#** Add a new group named idiots.#** Look at /etc/group and note the GID of idiots.#** What GID is given to a new group if if you do not specify it?#** Your anger has subsided. Delete the idiots group.#** Look at /etc/group again and note the change.
* Name: fedora3* Boot media: Network installation* Installation source: http://belmontBe sure to record your observations in your lab notes.senecac.on.ca/fedora/releases/13/Fedora/x86_64/os/* Kickstart location: http://zenit.senecac.on.ca/~chris.tyler/fedora13-vda-ks.cfg* Memory: 512MB* Disk space: 10GB* CPUs: 1
==Investigation 11: Deleting users == 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://zenit.senecac.on.ca/~chris.tyler/fedora13-vda-ks.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.
=== Investigation 4: Updating and Comparing {{Admon/note|Use fedora1|Perform these steps in the VMs ==='''fedora1''' virtual machine.}}
# In each VM, run this Read the man page for the userdel command: <code>yum update</code># Record . Note which option automatically removes 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?users home directory when that user is deleted.
Complete # Delete the following table:user ops235_1 using the command <code>userdel ops235_1</code># Delete the user ops235_2 using the same command with the option which removes the home directory of the user.# Check the contents of the /home directory. What do you notice?# Check the contents of the /etc/group directory. What do you notice?
{|border="1" width="100%"|-! ||f13host||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 forBe sure to record your observations in your lab notes...'''|| || || |||}
=== Investigation 5: Managing Virtual Machines from the Command Line ===
{{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.}}== Investigation 12: Modifying users ==
# Start the ''{{Admon/note|Use fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.# Enter |Perform these commands and note the result:#* <code>virsh list</code>#* <code>virsh list --all</code>#* <code>virsh list --inactive</code># Start steps in the ''fedora3'' virtual machine from the command line: <code>virsh start fedora3</code># Repeat the commands from step 2 and notice any changes.# Stop the 'fedora1'fedora3'' virtual machine: <code>virsh shutdown fedora3</code># Confirm that ''fedora3'' has been shut down.# Execute this command: <code>virsh dumpxml fedora3 >fedora3.xml</code># Examine the file <code>fedora3.xml</code>. What does it contain? What format is it in?# Edit the file fedora3.xml, making the following changes:#* Change the 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.# Issue this command: <code>virsh define fedora3a.xml</code># Issue the command <code>virsh list --all</code> and record any changes.# Issue the command: <code>virsh undefine fedora3a</code># List all of the virtual machines again, and note any changes.}}
=== Investigation 6: How do I backup a virtual machine? ===# Read the man page for the usermod command. Note which options change the user's full name, primary group, supplementary groups, and shell.
# Shut down all Add each of your new users to the virtual machinesgroup ops235 (in other words, add ops235 to each user as a supplementary group).# Change to the directory Examine <code>/var/lib/libvirt/imagesetc/group</code>. Note the size of the files in this directory. What do these files containhas changed?# Make a compressed backup of Use the <code>fedora3.img</code> file with this usermod command: <code>gzip <fedora3.img >fedora3.img.backup.gz</code>{{Admon/caution|Make sure the backup is successful!|If there are any error messages, '''DO NOT'to associate each of your pod mates'' proceed past this point. You're going full name to destroy your fedora3 virtual machine and restore it using the backup you have created -- if there are any problems with the backuptheir user name, 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 as shown in your fedora VMtext. With each change, and <u>not</u> examine their entries in your Fedora main system.'''# Wreck <u>only</u> your fedora 3 system! Try this command inside the fedora3 virtual machine ('''DO NOT''' do this on your main Fedora system, or you will have to repeat your '''lab2''' and portions of your '''lab3'''!): <code>rm -rf /*<etc/code># Shut down the VM.# Restore the original image from backup (type this command carefully): <code>gunzip <fedora3.img.backup.gz >fedora3.imgpasswd</code># Restart the VMfile. Is it working normallyWhat has changed?# Create compressed backups of Be sure to record your other 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?# Write the answer to the Investigation 6 question observations in your lab booknotes.
{{Admon/important|Backing up VMs|It's a good idea 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.}}
{{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, <!-- == Investigation 13: Security Tip: Removing Unnecessary Users and will resume the next time you boot your host system.}}Groups ==
=== Investigation 7: Kickstart Files ==={{Admon/note|Use fedora1|Perform these steps in the '''fedora1''' virtual machine.}}
{{Admon/tip|SSHD The default Linux distribution installs many users and Firewall|If you have restarted your virtual machine ''fedora1''groups to the system for the purpose of running various services. You will rarely, if ever, need to run all of these services on a single server, and some are actually obselete for most systems. Servers tend to be specialized, for both performance and security reasons. For example, the sshd a web server you started in section 1-16 will no longer would probably not be runningas an email server and file server at the same time. In additionWhile having all the possible user accounts installed by default makes it easier to set services up, it also increases the firewall will have reverted to its original statecomplexity of the machine. In order to use ''scp''The more complex a system is, belowthe more places it can fail, you will need to restart ssh and adjust the firewall againhence its security is lessened. Therefore, we can increase our server's security by removing unnecessary users.}}
When you perform a non-Kickstart installationThere is no set list of users we can safely remove. The requirements of each system varies greatly, and it is up to the installation program creates a Kickstart file in administrator to know these requirements, and understand which accounts can be removed. However, the <code>/root</code> directory for referencelist we provide here can usually be removed, unless their services are specifically required.
# Obtain Before attempting the kickstart files for all four following, make backup copies of your installations (your disk pack ''f13host''/etc/passwd and /etc/group files, plus the in case we delete a user or group that is essential to our system''fedora1'', ''fedora2'', and ''fedora3'' virtual machines)s operation. Copy them all to # Carefully remove the following users from your f13host system , if they exist: #* games#* gopher#* lp (tip: use <code>scp</code>if no printer is installed).# Compare these files. What are the differences? Similarities? * news#* nfsnobody#* nscd (Tip: you may want to use tools such as <code>sdiff</code> to help with the comparisonif not using nscd).# How could you use * uucp# Carefully remove the kickstart file produced by the installation program to perform additionalfollowing groups from your system, identical installations?if they exist: #* games#* gopher#* lp (if no printer is installed)#* news#* nfsnobody#* nscd (if not using nscd)#* uucp -->
== Completing the Lab =lab =
{{Admon/important | ImportantTime for a new backup! | Arrange evidence If you have successfully completed this lab, make a new backup of each your virtual machines. Remember to also make a backup of the following items new second virtual disk drive on the screen''fedora1'' -- you now have two virtual disks on ''fedora1'', and therefore two image files, and then ask your professor or lab monitor to check them:therefore will need two backup files.}}
Arrange proof of the following on the screen:# Two PVs on '''fedora1'''.# Three working virtual machines createdSeparate <code>/home</code> filesystem (on an LV) in '''fedora1'''.# Larger <code>/home</code> on '''fedora2''' and '''fedora3'''.# Unnecessary/unused packages have been deleted (list at least 4, and show that they are no longer installed).<!-- # Four kickstart filesUnnecessary accounts and groups have been removed on '''fedora1'''.--># All virtual machines fully updatedAccount created on '''fedora3''' matching your Matrix account.# All virtual machines backed up'''nled''' installed on the host (disk pack - main system '''f13host''').# Installation comparison table filled inAnswer to this question: #* What is the license of the '''nautilus''' package?# Fresh backup of the virtual machines.
== Preparing for the Quizzes ==
# What is the name of the Fedora installation programa VG? PV?# 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 installedLV?# Which type of installation works best for confirming compatibility with hardware before installation? WhyWhat does yum do that rpm does not?# Which type What is the total size of installation works best for installing large numbers of computers? Whythe "main" VG on your system?# What factors affect installation timeHow do you create a LV?# How can do you reduce the number of software updates required immediately after installationdelete an LV?# Why How would you enable additional repositories during installation?# What does add the file disk partition <code>/rootdev/anaconda-ks.cfgsdb7</code> contain, and how is it createdto your volume group "main"?# How do would you start and stop virtual machines?# How do you SSH into your virtual machinesincrease the size of the root filesystem by 50 MB?# What is the purpose of and relationship between these pieces of software<code>/etc/fstab</code>?#* libvirt#* libvirtd#* virsh#* virt-manager#* virt-install#* vncviewer#* kvmWhat did you have to do in order to move the home directories onto a new filesystem? Why?