[[Category:OPS235]][[Category:OPS235 Labs]]{{Admon/importantcaution|Unbind your MAC addressTHIS IS AN OLD VERSION OF THE LAB|Before proceeding with '''This is an archived version. Do not use this lab, [[Unbinding MAC Addresses on Fedora|unbind in your MAC address]]OPS235 course.'''}}=Logical Volume Management and Software Package Management=
= Using Virtual Machines =
== Objectives Introduction==
* Understand Virtualization* Use KVM virtualization on Fedora* Use a variety of installation methods** Live Image Installation** Network Installation** Kickstart InstallationIn this lab you're going to:
== Reference Material ==:* Learn how to add and remove software packages on your different Linux systems.:* Learn how to properly adjust your various Linux file systems by using and managing LVM both graphically (fedora2) as well as command line (fedora3).
Virtualization* [http://docs.fedoraproject.org/virtualization-guide/f13/en-US/html/ Fedora 13 Virtualization Guide]== Required Materials (Bring to All Labs) ==
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 Installation17 LIVE CD** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ Fedora 13 17 x86_64 Installation Guide]DVD*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/sn-automating-installation.html Automating the Installation with Kickstart]SATA Hard Disk (in removable disk tray)*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ch-kickstart2.html Kickstart Installations]USB Memory Stick*** [http://docs.fedoraproject.org/install-guide/f13/en-US/html/ch-redhat-config-kickstart.html Kickstart Configurator]Lab Logbook
== Required Materials Prerequisites==
* Removable disk pack with Fedora installed (see Completion and Instructor "Sign-off" of Lab 2: [[OPS235 Lab 2|Lab 2]]).* Fedora 13 x86_64 Live CD.
{{Admon/tip|Performing this Lab off the Seneca network|This lab uses servers which are on the Seneca network and which are not available from other locations ==Linux Command Online Reference==Each Link below displays online manpages for each command (such as your home). If you attempt this lab from another location, adjust the belmont.senecac.on.ca URLs to point to another via [http://mirrorslinuxmanpages.fedoraprojectcom/ http://linuxmanpages.org/publiclist Fedora mirror servercom] -- 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.}}):
{|width="100%" cellpadding= Introduction ="5"|'''LVM Information Utilities:'''|'''LVM Management Utilities:'''|'''Additional Utilities:'''|- valign="top"|*[http://linuxmanpages.com/man8/vgs.8.php vgs]*[http://linuxmanpages.com/man8/lvs.8.php lvs]*[http://linuxmanpages.com/man8/pvs.8.php pvs]*[http://linuxmanpages.com/man8/vgdisplay.8.php vgdisplay]*[http://linuxmanpages.com/man8/lvdisplay.8.php lvdisplay]*[http://linuxmanpages.com/man8/pvdisplay.8.php pvdisplay]|*[http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-system-config-lvm.html system-config-lvm] (Tutorial)*[http://linuxmanpages.com/man8/lvextend.8.php lvextend]*[http://linuxmanpages.com/man8/resize2fs.8.php resize2fs]*[http://linuxmanpages.com/man8/lvcreate.8.php lvcreate]*[http://linuxmanpages.com/man8/lvreduce.8.php lvreduce]*[http://linuxmanpages.com/man8/pvcreate.8.php pvcreate]*[http://linuxmanpages.com/man8/vgextend.8.php vgextend]|*[http://linuxmanpages.com/man8/mount.8.php mount]*[http://linuxmanpages.com/man8/umount.8.php umount]*[http://linuxmanpages.com/man8/yum.8.php yum]*[http://linuxmanpages.com/man8/rpm.8.php rpm]|}
A ==Resources on the web==Additional links to tutorials and HOWTOs:'''Please read this page to get an overview of LVM:''virtual machine'<br /><br />:* [[Logical Volume Management]] (' ''Note:''' It is recommended to return to this guide as a software simulation of a computer which can be used as though it were actual hardwarereference when performing the next several investigations):* [http://fedoranews.org/alex/tutorial/rpm/ Using the RPM Utility]:* [http://www. It's possible to run multiple virtual machines on one computer, reducing hardware requirements and introducing flexibilitycentos. Some common uses of virtualization include:org/docs/5/html/yum/ Using the YUM Utility]
* = 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.Package Management =
In this lab, == Investigation 1: How do 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 machines.query the RPM database? ==
You have already used RPM maintains a Fedora live disc and an installation discdatabase of installed software. This information is very useful to system administrators. In both casesLab 3, you queried that database using RPM with the -q argument. When you query the boot media (which RPM database, you can separately specify::* Which packages you used want to load the installation software) and the installation source do an <u>operational task</u> (where the software that got installed came fromlike installing or removing a package) were the same, using a '''select-option''': they CD* What <u>information</DVD provided both. Howeveru> you want about those packages, the Fedora (and most other Linux distributions) permits you to use any combination of boot media and installation media:using a '''query-option'''
* Boot Media** CD or DVD** Hard disk** USB flash drive** Network boot'''Perform the following steps:'''
* Installation source# Using information from the man page for <code>rpm</code>, fill in this information:** CD {|width="100%" border="1" cellpadding="5"|-!Option!Meaning!Select or DVDquery option?!Example command|-| -a|Select all packages|select-option| |-| -l| | | |-| -i|Show the package information.| | |-** Hard disk| -f filename** USB flash drive| ** Network HTTP or NFS software repository| | |-|packagename|Select just this package|select-option| |}
== Instructions =='''Answer the Investigation 1 observations / table contents in your lab log book.'''
=== Preparation =Investigation 2: How do you install and remove software with RPM? ==
{{Admon/tip|Update # Use the graphical file manager (Nautilus) to change to the directory on your Fedora Installation|ItDVD. Go to the sub-directory called 's a good idea ''Packages''' and then go to ensure that your Fedora installation is fully updated before proceeding. You can update your system the sub-directory '''l''' (for files beginning with the graphical tool located on letter l like the menu at '''lynx''' package). You should see a file called: <code>System>Administrationlynx-2.8.7-8.fc17.x86_64.rpm</code>Software Update (or type # Execute the following command : <code>gpkrpm -updatei lynx-2.8.7-view8.fc17.x86_64.rpm</code>), or by typing either of these commands# Issue an RPM query to check that lynx is installed. Record this command in your lab log-book.# Issue the following command: <code>pkcon updaterpm -e lynx</code> or # Issue an RPM query to verify that lynx is no longer installed. Record this command in your lab log-book.# Move to the appropriate sub-directory for packages that begin with the letter '''b'''.# Issue the following command: <code>yum updaterpm -i BackupPC-3.2.1-7.fc17.x86_64.rpm</code>}}and note the result
# Install '''Answer the Fedora virtualization software: <code>yum groupinstall "Virtualization"<Investigation 2 observations /code> or <code>pkcon install @virtualization</code> The virtualization software installed is questions in three parts:## A system service named your lab log book.''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>
{{Admon/important|Run virt-manager as a regular user|Running virt-manager as root may not work due to configuration issues.}}== Investigation 3: How do you install and remove software with ''yum''? ==
{{Admon/cautionnote|Reboot your fedora hostInternet Connection|There appears In order for yum to be an issue with supplying your VM's with work you require a dynamic IP unless connection to the host is restarted after installing "Virtualization"Internet. '''Reboot now Establish this connection by using the browser to avoid this problem.'''log into SeneNET}}
=== Investigation 1: Installing from a Live Disc ===# Change to your home directory.
{{Admon<ol> <li value="2">Issue the command: <code>yum install BackupPC</tip|Using an Image instead of code> and answer <code>y</code> to the question about installation. <ol type="a Live Disc|If you do not have a Live Disc available, you can download "> <li>Where did ''yum'' get the BackupPC software?</li> <li>Why could ''yum'' install BackupPC when rpm couldn't?</li> </ol> </li> <li>Issue an RPM query to verify that BackupPC is installed.iso image file from httpRecord this command in your lab log-book.</li> <li>Issue the command:<code>yum remove BackupPC</code></belmontli> <li>Issue an RPM query to verify that BackupPC is no longer installed.senecac.onRecord this command in your lab log-book.ca</fedorali> <li>Install <code>nled</releasescode> using '''yum'''. Record this command in your lab log-book.</13li> <li>Issue this command: <code>yum info cups</Livecode></x86_64li></Fedora-13-x86_64-Liveol>::* Based on the result, do you think that cups is a useful package for your system? If not, try removing it.iso <ol> <li value="8">Unused and then use the iso image file in place of the physical unneeded software can present a security risk and ties up diskspace 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.}}</li></ol>
==== Introduction ===='''Answer the Investigation 3 observations / questions in your lab log book.'''
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.=Logical Volume Management (Introduction)=
==== VM Details ==Check Current LVM Information Prior to Performing Investigations ==
* Name: fedora1* Boot media: Fedora Live CD* Installation source: Fedora Live CD* Memory: 512MB* Disk space: 10GB* CPUs: 1'''LVM''' ('''Logical Volume Management''') is used to manage hard disk drives / partitions for Unix/Linux systems. LVM provides more flexibility than just working with hard disks / hard disk partitions. '''Volume Groups''' are areas used to define '''Physical Volumes''' (i.e. hard disks, disk partitions, or other forms of storage devices). '''Logical Volumes''' are then used to relate directories (mount points) to a specific physical volume or for a "range" or "span" of physical volumes.
==== Steps ====Therefore, LVM allows more flexibility and growth potential for Linux systems (for example, having Logical volumes span multiple hard disks). Fedora uses LVM by default upon installation. Other Linux distributions may provide the capacity to install LVM, or later install and then use Logical Volume Management.
{{Admon'''Although the concept of LVM is simple, it takes practice and preparation (or "thinking ahead") in order to correctly use this valuable tool'''. It is important for students to gain an understanding of LVM, and how to manage their file-systems using LVM. It is recommended for students to read the following resource prior to this lab and/note|Fedora 12 Screen Shotsor return to the following resource while performing this lab: [[Logical Volume Management]] At this point, having completed [[OPS235 Lab 2|The Lab 2]] you should have roughly the following screen shots disk storage setup:<br />('''Note:''' These results are output from Fedora 12the '''vgs''', '''lvs''', and '''pvs''' commands that provide volume group, physical volume and logical volume information for each of the virtual machines that you created in lab2. The Fedora 13 version of virt-manager varies slightly -- there Before proceeding, check these values with your own system to see if you are a few extra controls generally "on some dialogs which may be ignoredthe right track".}}<br /><br />
# In the Virtual Machine Manger, click on the icon 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 Disc.# 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 VG #PV #LV #SN Attr VSize VFree vg_fedora1 1 2: Installing from the Network === 0 wz--n- 9.50g 0
{{Admon PV VG Fmt Attr PSize PFree /tip|Authenticate to the network|The rest of this lab uses network access. Be sure to authenticate to the network using your browser before proceedingdev/vda3 vg_fedora1 lvm2 a-- 9.}}50g 0
==== Introduction ==== LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_root vg_fedora1 -wi-ao 8.03g lv_swap vg_fedora1 -wi-ao 1.47g
It is possible to install Fedora entirely from the network. In this investigation, you will install Fedora from a webserver on Seneca* '''fedora2'''s LAN.
==== VM details ==== VG #PV #LV #SN Attr VSize VFree vg_fedora2 1 3 0 wz--n- 14.50g 3.25g
* Name: fedora2 PV VG Fmt Attr PSize PFree* Boot media: Network installation* Installation source: http: /dev/belmontvda3 vg_fedora2 lvm2 a-- 14.senecac50g 3.on.ca/fedora/releases/13/Fedora/x86_64/os/* Memory: 512MB* Disk space: 15GB* CPUs: 125g
==== Steps ==== LV VG Attr LSize Origin Snap% Move Log Copy% Convert# Create the VM as you did with the ''fedora1'' virtual machine, except:#* In step lv_home vg_fedora2 -wi-ao 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/x86_64/os/97g #* In step 2 of 5, set the ''OS Type'' to "Linux" and ''Version'' to "Fedora 13" # Observe the boot process lv_root vg_fedora2 -wi-ao 7. How is it different from booting from an optical disc (CD/DVD)?81g # Start the installation process. When you get to the disk partitioning step, enable the checkbox labelled ''Review and modify partition layout''. 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 ext3 or ext4 as the filesystem type).# On the software selection screen, select ''Graphical Desktop''.# On the same screen, select the "Fedora 13 lv_swap vg_fedora2 - x86_64" and the "Fedora 13 wi- 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 installationsao 1.47g
=== Investigation * '''fedora3 (Note: This VM has no GUI installed)''' VG #PV #LV #SN Attr VSize VFree vg_fedora3 1 3: Installing from the Network using Kickstart === 0 wz--n- 9.51g 0
==== Introduction ==== PV VG Fmt Attr PSize PFree /dev/vda3 vg_fedora3 lvm2 a-- 9.51g 0
When Fedora is installed using the techniques you have used so far, the user is asked a number of questions LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_home vg_fedora3 -wi-ao 1. In some situations, it is better to provide the answers to these questions in a file rather than answer them individually00g lv_root vg_fedora3 -wi-ao 8. This type of file is called a 00g lv_swap vg_fedora3 -wi-ao 520.00m * '''f17host (i.e. "removable hard disk" or "disk pack")'kickstart'' file.
In Does not use LVM. Confirm 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 toolthe same commands used above.
==== {{Admon/note|VM details ====Backups and Recovery|Most of these investigations will take place in your virtual machines. If you make a significant mistake, your virtual machine may not boot. Remember that you created backups of your virtual machines in Lab 2, and you can restore them if something goes wrong.<br /><br />'''Remember: if you did not create backups for all of your VMs, then you don't have any restoration points to fall-back to!'''|}}
* Name== Investigation 4: fedora3* Boot media: Network installation* Installation source: http://belmont.senecac.on.ca/fedora/releases/13/Fedora/x86_64/os/* Kickstart location: http://zenit.senecac.on.ca/~chris.tyler/fedora13Extend the size of lv_root using command-vda-ks.cfg* Memory: 512MB* Disk space: 10GB* CPUs: 1line tools ==
==== 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 Perform 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 investigation in (use the user ID and password information from the previous step). Compare the experience to the first time you booted the other virtual machinesfedora3.
=== Investigation 4: Updating Let's say that you have run out of disk space on your computer (fedora3), you need more space on the root filesystem, perhaps to host more webpages or a larger database or new software. What are your options? Getting a replacement harddrive would probably require reinstallation of the operating system and Comparing backup/restore of the VMs ===data.
# In each VMBecause we're using LVM though - we can avoid that. We can add a new harddrive (which will serve as a physical volume) to the volume group, run this command: <code>yum update</code># Record and extend the answers root logical volume 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?make use of the new available space.
Complete '''Perform the following tableoperations to increase the size of lv_root in fedora3:'''
{|border="1" width="100%"|-! ||f13host||fedora1||fedora2||fedora3|-|<u>'''Installation Method<font>Steps:</font>'''||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...'''|| || || |||}</u>
=== Investigation 5<ol> <li>Run the following commands and make note of the output: Managing Virtual Machines from </li> <code>ls /dev/vd* pvs vgs lvs df -h</code> <li>Open the fedora3 virtual machine console</li> <li>Go to the hardware details view</li> <li>Click "Add Hardware" and add a new storage device of 2GBs, make sure it's a VirtIO disk.</li> <li>Go back to the console view</li> <li>Run the same ls command now, what's changed?</li> <li>Now we'll make the new device as a physical volume, add it to the Command Line ===volume group, and extend lv_root:</li> <code>pvcreate /dev/vdb
{{Admon vgextend vg_fedora3 /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.}}dev/vdb
# Start the ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.# Enter these commands and note the result:#* <code>virsh list</code>#* <code>virsh list lvextend -l +100%FREE -allr vg_fedora3/lv_root</code>#* <code>virsh list --inactive </codeli># Start the ''fedora3'' virtual machine from Now rerun the command line: <code>virsh start fedora3<ls/code># Repeat the commands from step 2 and notice any changes.# Stop the ''fedora3'' virtual machine: <code>virsh shutdown fedora3<pvs/code># Confirm that ''fedora3'' has been shut down.# Execute this command: <code>virsh dumpxml fedora3 >fedora3.xml<vgs/code># Examine the file <code>fedora3.xml<lvs/code>df commands. What does it containhas changed and what caused those changes? What format is it in?# Edit the file fedora3.xml, making the following changes:#* Change the name to <code>fedora3a</codeli>#* 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: <codeli>virsh define fedora3.xml</code># Issue Among the command <code>virsh list changes, note that your root filesystem is now 2GB bigger --alland you have not even rebooted your machine!</codeli> and record any changes.# Issue the command: <code>virsh undefine fedora3a</codeol># List all of the virtual machines again, and note any changes.
=== '''Answer the Investigation 6: How do I backup a virtual machine? ===4 observations / questions in your lab log book.'''
# 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 with this command== Investigation 5: <code>gzip <fedora3.img >fedora3.img.backup.gz</code>{{Admon/caution|Make sure the backup is successful!|If there How are any error messages, '''DO NOT''' proceed past this point. You're going to destroy your fedora3 virtual machine and restore it LVMs managed using the backup you have created -system- if there are any problems with the backup, you will not have a working virtual machine, and will have to reconfig-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 <u>not</u> 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 /*</code># Shut down the VM.# Restore the original image from backup (type this command carefully): <code>gunzip <fedora3.img.backup.gz >fedora3.img</code># Restart the VM. Is it working normallylvm?# Create compressed backups of 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 in your lab book.==
{{Admon'''Perform this investigation on the VM named ''<u>fedora2</importantu>''.'''[[Image:Ops235_lab4_1.png|Backing up VMsthumb|right|Screenshot of system-config-lvm in Fedora. Click to enlarge.]]# Let's learn to administer (manage) our LVM graphically for our '''Fedora2''' Virtual Machine.<br />Fedora provides a tool called <code>system-config-lvm</code> to graphically administer LVM. Itwill appear on the menu as '''Application'''>'''Other'''>'''Logical Volume Management'''. The package may not be installed by default, so you will need to install it by issuing: (<code>yum install system-config-lvm</code>).<ol> <li value="2">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: <ol type="a"> <li>What are the names and sizes of the '''PV'''s?</li> <li>What is the name and size of the '''VG'''?</li> <li>What are the names and sizes of the '''LV'''s ?</li> <li>Is there any space in the VG which is not allocated to a good idea LV?</li> </ol> </li> <li>Increase the size of the home file-system to back up your VMs '''2 GB''': <ol type="a"> <li>Click on the LV containing the '''home''' filesystem.</li> <li>Click on ''Edit Properties''.</li> <li>Change the size to '''2 GB''' and click ''Ok''.</li> </ol> <li>Create a '''new 2G LV''' (LV Properties: linear) containing an ext4 filesystem named lv_archive and mount it at '''/archive''' <ol type="a"> <li>Click on ''Logical View''.</li> <li>Click the ''Create New Logical Volume''.</li> <li>Set the end of each labname, size, filesystem, so you can easily restore them if something goes wrong and mount point.</li> <li>Click ''Ok''.</li> </ol> <li>Backup <code>'''/etc'''</code> into <code>'''/archive'''</code></li></ol>::* Copy the files in /etc into the filesystem mounted at <code>/archive</code><br />(use the next labgraphical tools or the command line.}}If using cp, remember to use the -R option).<ol> <li value="6">Shrink the size of <code>lv_archive</code> to '''1 GB'''.</li> <li>Try shrinking the home file-system. What happens? Why?</li></ol>
{{Admon'''Answer the Investigation 5 observations /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 questions in your host systemlab log book.}}'''
=== Investigation 7: Kickstart Files ==Updated backup instructions =
{{Admon/tip|SSHD and Firewall|If you have restarted completed this lab correctly - please make sure you are still making full backups of your virtual machine ''fedora1'', the sshd server you started in section 1-16 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 againmachines.}}
When Remember adding a new harddrive to fedora3? You will need to back up that drive as well. If you perform a nondon't -Kickstart installationyou will only have half of your machine backed up, the installation program creates which is of no use for a Kickstart file in the <code>/root</code> directory for referencerecovery.
# Obtain = Completing the kickstart files for all four of your installations (your disk pack ''f13host'', plus the ''fedora1'', ''fedora2'', and ''fedora3'' virtual machines). Copy them all to your f13host system (tip: use <code>scp</code>).# 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?lab =
== Completing the Lab =={{Admon/important|Time for a new backup!|If you have successfully completed this lab, make a new backup of your virtual machines.}}
{{Admon'''Notes:'''# rpm command options# yum command options# How to use pvs/vgs/important | Important! | Arrange evidence of each lvs/df/pvcreate/vgextend/lvextend# Answer to this question "What is the license of the following items on the screen, and then ask your professor or lab monitor to check them:}}nautilus package?"
# Three working virtual machines created.'''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:'''# Four kickstart filesnled installed on the host (disk pack - main system f16host).# All virtual machines fully updatedUnnecessary/unused packages have been deleted (list at least 4, and show that they are no longer installed).# All Fresh backup of the virtual machines backed up.# Installation comparison table filled in.
== Preparing for the Quizzes ==
# What is the name of the Fedora installation programa VG? PV? LV?# Which factors recorded in your table (above) were due What commands are used to the type of installation performed, and which factors were due to the amount of software installeddetermine VG / PV / LV information?# Which type of installation works best for confirming compatibility with hardware before installation? WhyWhat does yum do that rpm does not?# Which type of installation works best for installing large numbers of computers? Why?List the steps to install a package via rpm command.# What factors affect installation time?List the steps to determine detailed information regarding an install package.# How can you reduce List the number of software updates required immediately after installation?steps to remove a package via rpm command.# Why would you enable additional repositories during installation?List the steps to install a package using the yum command.# What does List the steps to remove a package using the file <code>/root/anaconda-ksyum command.cfg</code> contain, and how # What is it createdthe total size of the "main" VG on your system?# How do you start and stop virtual machinescreate a LV?# How do you SSH into your virtual machinesdelete an LV?# What is How would you increase the purpose size of and relationship between these pieces of softwarethe root filesystem by 50 MB?#* libvirt#* libvirtd#* virsh#* virt-manager#* virt-install#* vncviewer#* kvm