Changes

[[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=

== Objectives Introduction==

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/note|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.}}):

{|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'''

{|width="100%" border= Instructions ="1" cellpadding="5"|-!Option!Meaning!Select or query option?!Example command|-| -a|Select all packages|select-option| |-| -l| | | |-| -i|Show the package information.| | |-| -f filename| | | |-|packagename|Select just this package|select-option| |}

{{Admon/tip|Update your Fedora Installation|It's a good idea to ensure that your Fedora installation is fully updated before proceeding. You can update your system == Investigation 2: How do you install and remove software with the graphical tool located on the menu at >System>Administration>Software Update (or type the command <code>gpk-update-view</code>), or by typing either of these commands: <code>pkcon update</code> or <code>yum update</code>}}RPM? ==

# Install Use 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 graphical file manager (Nautilus) to change to the directory on your Installation DVD. Go to the sub-directory called '''Packages''' and then go to the sub-directory '''l'libvirtd'' that manages (for files beginning with the letter l like the VMs'''lynx''' package).## Tools to manage virtualization, including the You should see a file called: <code>virtlynx-manager2.8.7-8.fc17.x86_64.rpm</code> graphical tool and # Execute the following command: <code>virshrpm -i lynx-2.8.7-8.fc17.x86_64.rpm</code> # Issue an RPM query to check that lynx is installed. Record this commandin your lab log-line toolbook.## The actual virtual machines themselves.# Start Issue the virtualization servicefollowing command: <code>service libvirtd startrpm -e lynx</code># The firewall configuration Issue an RPM query to verify that lynx is altered by no longer installed. Record this command in your lab log-book.# Move to the addition of appropriate sub-directory for packages that begin with the virtualization softwareletter '''b'''. 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 Issue the following command : <code>virtrpm -i BackupPC-manager3.2.1-7.fc17.x86_64.rpm</code>and note the result

{{Admon'''Answer the Investigation 2 observations /important|Run virt-manager as a regular user|Running virt-manager as root may not work due to configuration issuesquestions in your lab log book.}}'''

{{Admon/important|Reboot your fedora host|There appears to be an issue == Investigation 3: How do you install and remove software with supplying your VM's with a dynamic IP unless the host is restarted after installing "Virtualization".}}'yum''? ==

=== Investigation 1: Installing from {{Admon/note|Internet Connection|In order for yum to work you require a Live Disc ===connection to the Internet. Establish this connection by using the browser to log into SeneNET}}

{{Admon/tip|Using an Image instead of a Live Disc|If you do not have a Live Disc available, you can download the # Change to your home directory.iso image file from http://belmont.senecac.on.ca/fedora/releases/13/Live/x86_64/Fedora-13-x86_64-Live.iso and then use the iso image file in place of the physical disk.}}

<ol> <li value="2">Issue the command: <code>yum install BackupPC</code> and answer <code>y</code> to the question about installation. <ol type="a"> <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. Record this command in your lab log-book.</li> <li>Issue the command: <code>yum remove BackupPC</code></li> <li>Issue an RPM query to verify that BackupPC is no longer installed. Record this command in your lab log-book.</li> <li>Install <code>nled</code> using '''yum'''. Record this command in your lab log-book.</li> <li>Issue this command: <code>yum info cups</code></li></ol>::* Based on the result, do you think that cups is a useful package for your system? If not, try removing it.<ol> <li value== Introduction ===="8">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.</li></ol>

In this investigation, you will install Fedora from '''Answer the Investigation 3 observations / questions in your live disc, and observe the differences between this type of installation and the DVD installation previously performedlab log book.'''

==== VM Details ===Logical Volume Management (Introduction)=

{{Admon/note|Therefore, LVM allows more flexibility and growth potential for Linux systems (for example, having Logical volumes span multiple hard disks). Fedora 12 Screen Shots|The following screen shots are from Fedora 12uses LVM by default upon installation. The Fedora 13 version of virt-manager varies slightly -- there are a few extra controls on some dialogs which Other Linux distributions may be ignoredprovide the capacity to install LVM, or later install and then use Logical Volume Management.}}

# 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 Although the title ''New VM''. There are five steps to be completed; click Forward after each step:# Step 1 concept of 5: Enter the virtual machine name LVM is simple, it takes practice and select 'preparation (or "thinking ahead") in order to correctly use this valuable tool'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 It is important for the disc students to be recognizedgain an understanding of LVM, then select it as the install media. Set the ''OS type'' to Linux and the ''Version'' how to Fedora 13.<br />[[Image:Virt-manager3.png]]<!-manage their file- {{Admon/tip|Using an ISO image|Instead of systems using a physical CD or DVD, you can use an ISO image of a CD or DVDLVM. The virtualization software will make this ISO image appear like an actual CD within It is recommended for students to read the virtual machine. Because hard disks are faster then optical discs, following resource prior to this will work faster than an actual CDlab and/DVD.}}{{Admon/note|Choosing the operating system type and version|The purpose of the ''OS type'' and ''Version'' fields is or return 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 5following resource while performing this lab: Set the memory to 512 MB and the number of CPUs to 1.<br />[[Image:Virt-manager4.pngLogical Volume Management]]# 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 /> At this point, having completed [[Image:Virt-manager5.pngOPS235 Lab 2|Lab 2]]# Step 5 of 5: Review the options that you should have selected. '''Make a note of roughly the following disk storage location.''' If anything needs to be changed, use the ''Back'' button to go back and edit it; otherwise, click ''Finish''.setup:<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 'Note:'hard drive'' of the virtual machine.# Login to the VM and double-click on These results are output from the ''Install to Hard Drive'vgs' 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 'lvs'America/Toronto'', and when asked about storage, select ''Use Entire Disk'pvs'. '''Use the default values commands that provide volume group, physical volume and logical volume information for all other fields.''' Notice that the installer does not ask you what software should be installed; compare the installation time to the amount each 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 menumachines that you created in lab2. You will get the ''Firstboot'' configuration questions during the boot process (asking you to create a userBefore proceeding, set the date and time, and optionally send the hardware profile to the Fedora Project). Create a user check these values with the same name as your Matrix account.# Login using the new user account.# Enable SSH access own system to your virtual machine with these commands: <code>service sshd start; chkconfig sshd see if you are generally "on</code># Find out the IP address of your virtual machine: <code>ifconfig eth0right track".<br /code># Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): <code>ssh ''IPaddress''<br /code>

{{Admon/tip|Authenticate to the network|The rest of this lab uses network access VG #PV #LV #SN Attr VSize VFree vg_fedora1 1 2 0 wz--n- 9. Be sure to authenticate to the network using your browser before proceeding.}}50g 0

It is possible to install Fedora entirely from the network LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_root vg_fedora1 -wi-ao 8. In this investigation, you will install Fedora from a webserver on Seneca's LAN03g lv_swap vg_fedora1 -wi-ao 1.47g

* Name: fedora2 VG #PV #LV #SN Attr VSize VFree* Boot media: Network installation* Installation source: http://belmont.senecac vg_fedora2 1 3 0 wz--n- 14.on50g 3.ca/fedora/releases/13/Fedora/x86_64/os/* Memory: 512MB* Disk space: 15GB* CPUs: 125g

==== Steps ==== PV VG Fmt Attr PSize PFree# 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: /dev/belmont.senecac.on.ca/fedora/releases/13/Fedora/x86_64/os/#* In step 2 of 5, set the ''OS Type'' 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 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 vda3 vg_fedora2 lvm2 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, uncheck the box for ''Office and Productivity'' (as well as the other software choices).# On the same screen, select the "Fedora 13 - x86_64" and the "Fedora 13 - x86_64 - Updates". ''DO NOT'' enable the "Test Updates" repository.# Complete the installation 14. Record the time taken to install, and compare this to the time taken by the previous installations50g 3.25g

When Fedora is installed using the techniques you have used so far, the user is asked PV VG Fmt Attr PSize PFree /dev/vda3 vg_fedora3 lvm2 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-- 9.51g 0

In this investigation, a kickstart file is provided for you LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_home vg_fedora3 -wi-ao 1. You can also create 00g lv_root vg_fedora3 -wi-ao 8.00g lv_swap vg_fedora3 -wi-ao 520.00m * '''f17host (i.e. "removable hard disk" or modify a kickstart file using a regular text editor or a graphical tool."disk pack")'''

* Name: fedora3* Boot media: Network installation* Installation source: http:{{Admon//belmontnote|VM Backups and Recovery|Most of these investigations will take place in your virtual machines.senecacIf you make a significant mistake, your virtual machine may not boot.onRemember that you created backups of your virtual machines in Lab 2, and you can restore them if something goes wrong.ca/fedora/releases/13/Fedora/x86_64<br /os><br /* Kickstart location>'''Remember: http://zenit.senecac.on.ca/~chris.tyler/fedora13if you did not create backups for all of your VMs, then you don't have any restoration points to fall-vda-ks.cfg* Memory: 512MB* Disk space: 10GB* CPUs: 1back to!'''|}}

==== Steps ====# Create the VM as you did with Investigation 4: Extend the ''fedora2'' virtual machine, specifying a network install as before, except:#* In step 2 size 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/fedora13lv_root using command-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. Compare the experience to booting the other virtual machines.line tools ==

# In each VMLet's say that you have run out of disk space on your computer (fedora3), run this command: <code>yum update</code># Record you need more space on the answers root filesystem, perhaps to these questions in host more webpages or a larger database or new software. What are 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 othersoptions?Getting a replacement harddrive would probably require reinstallation of the operating system and backup/restore of the data.

=== Investigation 5'''Perform the following operations to increase the size of lv_root in fedora3: Managing Virtual Machines from the Command Line ==='''

{{Admon<u>'''<font>Steps:</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.}}font>'''</u>

# Start <ol> <li>Run the ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.# Enter these following commands and make note of the resultoutput:#* <code>virsh list</codeli>#* <code>virsh list ls /dev/vd* pvs vgs lvs df --allh</code>#* <codeli>virsh list --inactive</code># Start Open the ''fedora3'' virtual machine from the command line: <code>virsh start fedora3console</codeli># Repeat the commands from step 2 and notice any changes.# Stop the ''fedora3'' virtual machine: <codeli>virsh shutdown fedora3Go to the hardware details view</codeli># Confirm that ''fedora3'' has been shut down.# Execute this command: <codeli>virsh dumpxml fedora3 >fedora3Click "Add Hardware" and add a new storage device of 2GBs, make sure it's a VirtIO disk.xml</codeli># Examine the file <codeli>fedora3.xmlGo back to the console view</codeli>. What does it contain? What format is it in?# Edit <li>Run the file fedora3.xmlsame ls command now, making the following changes:#* Change the name to what's changed?<code/li>fedora3a </codeli>#* Change at least one of Now we'll make the hexadecimal characters in new device as a physical volume, add it to the UUID. Do not change the length of the UUID. Valid hexadecimal characters are 0-9 volume group, and a-f.# Issue this commandextend lv_root: <code>virsh define fedora3.xml</codeli># Issue the command <code>virsh list --all<pvcreate /code> and record any changes.# Issue the command: <code>virsh undefine fedora3a<dev/code># List all of the virtual machines again, and note any changes.vdb

# Shut down all of the virtual machines. lvextend -l +100%FREE -r vg_fedora3/lv_root</code># Change to the directory <codeli>Now rerun the ls/var/libpvs/libvirtvgs/images/<lvs/code>. Note the size of the files in this directorydf commands. What do these files containhas changed and what caused those changes?# Make a compressed backup of the <code>fedora3.img</codeli> file with this command: <code>gzip <fedora3.img >fedora3.img.backup.gz </codeli># Compare Among the size of the compressed changes, note that your root filesystem is now 2GB bigger - and original files.# Start the ''fedora3'' VM.# Wreck it! Try this command inside the fedora3 virtual you have not even rebooted your machine (DO NOT do this on your main Fedora system!): <code>rm -rf /*</codeli># Shut down the VM.# Restore the original image from backup: <code>gunzip <fedora3.img.backup.gz >fedora3.img</codeol># Restart the VM. Is it working normally?# 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.

=== '''Answer the Investigation 7: Kickstart Files ===4 observations / questions in your lab log book.'''

When you perform a non== Investigation 5: How are LVMs managed using system-Kickstart installation, the installation program creates a Kickstart file in the <code>/root</code> directory for reference.config-lvm? ==

# Obtain '''Perform this investigation on the kickstart files for all four VM named ''<u>fedora2</u>''.'''[[Image:Ops235_lab4_1.png|thumb|right|Screenshot of your installations system-config-lvm in Fedora. Click to enlarge.]]# Let's learn to administer (your disk pack, plus manage) our LVM graphically for our '''Fedora2''' Virtual Machine.<br />Fedora provides a tool called <code>system-config-lvm</code> to graphically administer LVM. It will appear on the menu as '''Application'''>'''Other'''>'''fedora1Logical 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'fedora2'', s?</li> <li>What is the name and size of the '''VG'fedora3'' virtual machines).?</li># Compare these files. <li>What are the differencesnames and sizes of the '''LV'''s? Similarities</li> <li>Is there any space in the VG which is not allocated to a LV? </li> </ol> </li> <li>Increase the size of the home file-system to '''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''' (TipLV 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 name, size, filesystem, and mount point.</li> <li>Click ''Ok''.</li> </ol> <li>Backup <code>'''/etc'''</code> into <code>'''/archive'''</code></li></ol>:: you may want * Copy the files in /etc into the filesystem mounted at <code>/archive</code><br />(use the graphical tools or the command line. If using cp, remember to use tools such as the -R option).<ol> <li value="6">Shrink the size of <code>sdifflv_archive</code> to help with the comparison)'''1 GB'''.</li># How could you use <li>Try shrinking the kickstart home file produced by the installation program to perform additional, identical installations-system. What happens? Why?</li></ol>

== Completing '''Answer the Lab ==Investigation 5 observations / questions in your lab log book.'''

# Three working If you completed this lab correctly - please make sure you are still making full backups of your virtual machines created.# Four kickstart files.# All virtual machines fully updated.# All virtual machines backed up.# Time required to create each VM recorded.

== Preparing Remember adding a new harddrive to fedora3? You will need to back up that drive as well. If you don't - you will only have half of your machine backed up, which is of no use for the Quizzes ==a recovery.

= 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.}} '''Notes:'''# rpm command options# yum command options# How to use pvs/vgs/lvs/df/pvcreate/vgextend/lvextend# Answer to this question "What is the name license of the Fedora installation programnautilus package?" '''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:'''# What are nled installed on the advantages host (disk pack - main system f16host).# Unnecessary/unused packages have been deleted (list at least 4, and disadvantages of each type of installation?show that they are no longer installed).# Which type Fresh backup of installation works best the virtual machines. = Preparing for confirming compatibility with hardware before installationQuizzes = # What is a VG? PV? WhyLV?# Which type of installation works best for installing large numbers of computers? WhyWhat commands are used to determine VG / PV / LV information?# What factors affect installation timedoes yum do that rpm does not?# How can you reduce List the steps to install a package via rpm command.# List the steps to determine detailed information regarding an install package.# 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