[[Category:OPS235]][[Category:OPS235 Labs]]
{{Admon/caution|THIS IS AN OLD VERSION OF THE LAB|'''This is an archived version. Do not use this in your OPS235 course.'''}}
=Logical Volume Management and Software Package Management=
==Introduction==
:* In this lab, you are 're going to learn how to properly adjust your various Linux file systems by using and managing LVM both graphically (fedora1, fedora2) as well as command line (fedora3). :* Also in this lab, you will learn how to add and remove software packages on your different Linux systems. ==Objectives==
#:* Learn about LVM concepts including Physical / Logical Volumes how to add and Volume Groupsremove software packages on your different Linux systems.#:* Learn how to properly resize adjust your various Linux file-systems by using and managing LVM, and understand the consequences to the filesystem due to mistakes.#Learn how to add and remove software packages using RPMboth graphically (fedora2) as well as command line (fedora3).
== Required Materials (Bring to All Labs) ==
==Required Materials (Bring to All Labs)== * '''Fedora 16 17 LIVE CD''' - You can burn this onto a CD-R in the Open Lab* '''Fedora 16 x_64 17 x86_64 Installation DVD''' - You can burn this onto a DVD-R in the Open Lab (or burn image onto a DVD+R if you are using the Freedom Toaster).* '''SATA Hard Disk''' (in removable disk tray)* '''USB Memory Stick''' (minimum 64M)* '''Lab Logbook (Lab3 Reference Sheet)''' (to make notes and observations).
==Prerequisites==
* Completion and Instructor "Sign-off" of Lab 2: [[OPS235 Lab 2]]
==Linux Command Online Reference==
:* [http://www.centos.org/docs/5/html/yum/ Using the YUM Utility]
= Software Package Management =
== Investigation 1: How do you query the RPM database? ==
RPM maintains a database of installed software. This information is very useful to system administrators. In Lab 3, you queried that database using RPM with the -q argument. When you query the RPM database, you can separately specify:
:* Which packages you want to do an <u>operational task</u> (like installing or removing a package), using a '''select-option'''
:* What <u>information</u> you want about those packages, using a '''query-option'''
'''Perform the following steps:'''
# Using information from the man page for <code>rpm</code>, fill in this information:
{|width="100%" border="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
|
|}
'''Answer the Investigation 1 observations / table contents in your lab log book.'''
== Investigation 2: How do you install and remove software with RPM? ==
=Logical Volume Management=# Use the 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''' (for files beginning with the letter l like the '''lynx''' package). You should see a file called: <code>lynx-2.8.7-8.fc17.x86_64.rpm</code># Execute the following command: <code>rpm -i lynx-2.8.7-8.fc17.x86_64.rpm</code># Issue an RPM query to check that lynx is installed. Record this command in your lab log-book.# Issue the following command: <code>rpm -e lynx</code># 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>rpm -i BackupPC-3.2.1-7.fc17.x86_64.rpm</code> and note the result
== Definition of LVM '''Answer the Investigation 2 observations / Check Current LVM Information Prior to Performing Investigations ==questions in your lab log book.'''
== Investigation 3: How do you install and remove software with ''yum''? == {{Admon/note|Internet Connection|In order for yum to work you require a connection to the Internet. Establish this connection by using the browser to log into SeneNET}} # Change to your home directory. <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="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> '''Answer the Investigation 3 observations / questions in your lab log book.''' =Logical Volume Management (Introduction)= == Check Current LVM Information for all Fedora 16 Installs =Prior to Performing Investigations ==
'''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.
'''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/or return to the following resource while performing this lab: [[Logical Volume Management]]
At this point, having completed [[OPS235 Lab 2|Lab 2]] you should have <u>roughly</u> the following disk storage setup:<br />
('''Note:''' These results are output from the '''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. Before proceeding, check these values with your own system to see if you are generally "on the right track".<br /><br />
<u>'''NOTE: Information based on a 250 GB Removable Hard Disk:'''</u>
* '''fedora1'''
lv_swap vg_fedora3 -wi-ao 520.00m
PV VG Fmt Attr PSize PFree /dev/vda2 vg_fedora3 lvm2 a- 9.80G 3.83G * '''f16host f17host (i.e. "removable hard disk" or "disk pack")''' VG #PV #LV #SN Attr VSize VFree vg_f16host 1 3 0 wz--n- 232.38g 0 PV VG Fmt Attr PSize PFree /dev/sda3 vg_f16host lvm2 a-- 232.38g 0 LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_home vg_f16host -wi-ao 176.62g lv_root vg_f16host -wi-ao 50.00g lv_swap vg_f16host -wi-ao 5.75g
{{Admon/note|VM Backups and Recovery|'''Most of these investigations will take place in your virtual machines.''' If you make a significant mistake, your virtual machine may Does not bootuse LVM. Remember that you created backups of your virtual machines in Lab 2, and you can '''restore them if something goes wrong'''Confirm this using the same commands used above.<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!'''|}}
{{Admon/note|VM 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!'''|}}
== Investigation 14: Adjusting Sizes Extend the size of lv_root and lv_home using command-line tools ==
=== Why Readjust sizes of lv_root and lv_home? ===Perform this investigation in fedora3.
If Let's say that you refer to the LV sizes have run out of disk space on your '''f16host'''computer (fedora3), you may notice that need more space on the size of '''lv_root''' (your root system) is quite small compared filesystem, perhaps to the size of '''lv_home'''host more webpages or a larger database or new software. The Virtual Machines that you have created What are stored in your options? Getting a replacement harddrive would probably require reinstallation of the directory pathname <code>/var/lib/libvirt/images/<operating system and backup/code>, and since you are required to make backups and create future VMs (assignments), you will run out restore of space!the data.
On the other hand, you may notice Because we're using LVM though - we can avoid that lv_home is extremely large. ThereforeWe can add a new harddrive (which will serve as a physical volume) to the volume group, we are going and extend the root logical volume to make use LVM management tools to redistribute those logical volume sizesof the new available space.
{{Admon/caution|LV resize is Required!|You '''MUST''' perform the following steps in order to re size lv_home and lv_root logical volumes. Failure to perform this operation will likely cause the user to run out of space in <code>/var/lib/libvirt/images/</code> directory used to hold future Virtual Machine installations (e.g. assignments).}} '''Perform the following operations to redistribute increase the sizes size of lv_root and lv_home in f16hostfedora3:'''
<u>'''<font>Steps:</font>'''</u>
# Make certain you are in your '''f16host''' system.
{{Admon/note|Resizing Logical Volumes While Still in Use|There is a problem when trying to resize lv_home while users are currently logged in. Please note and record the following procedure to resize these volumes. You should research these commands and gain an appreciation of why you are performing these sequence of commands.|}}
<ol>
<li value="2">'''Log-off all users on Run the following commands and make note of the GUI'''. You won't be able to complete this procedure if any users other than "root" are logged in.output:</li> <licode>Press the keyboard combination '''Ctrlls /dev/vd* pvs vgs lvs df -Alt-F2''' to a switch to a text-based Virtual Terminal. If you are having trouble connecting to a text-based terminal, try the '''Ctrl'''-'''Alt''' keys with another '''function''' key.h</licode> <li>Log into your root account (eg. '''username: ''root'' password: ''admin password''''')Open the fedora3 virtual machine console</li> <li>Enter Go to the following Linux commands:hardware details view</li> </olli>:: Click "Add Hardware" and add a new storage device of 2GBs, make sure it's a VirtIO disk.<code>umount /home</codeli>:: <codeli>lvreduce -L 20G -r vg_f16host/lv_homeGo back to the console view</codeli>:: <codeli>lvextend -l +100%FREE -r vg_f16host/lv_rootRun the same ls command now, what's changed?</codeli>:: <codeli>mount -Now we'll make the new device as aphysical volume, add it to the volume group, and extend lv_root:</codeli>:: <code>logout<pvcreate /dev/code>vdb
{{Admon vgextend vg_fedora3 /note|System error messages|You may experience "random" system error messages while you are performing this procedure. You can ignore these messages, but make certain that the above commands have been completed (i.e. "dont' panic and press ctrl-c"). You can issue the '''lvs''' command to confirm that lv_root now has more space...|}}dev/vdb
<ol> <li value="6">Press the keyboard combination '''Ctrl lvextend -Altl +100%FREE -F1''' to return to GUI (or similar key-combination with other function key). r vg_fedora3/lv_root</licode> <li>Log into your account.<Now rerun the ls/pvs/vgs/lvs/li> <li>Open a terminaldf commands.What has changed and what caused those changes?</li> <li>Issue Among the '''vgs''', '''pvs'''changes, note that your root filesystem is now 2GB bigger - and '''lvs''' commands to verify new volume information for you have not even rebooted your f16host.</li> <li>Proceed to Investigation #2.machine!</li>
</ol>
'''Answer the Investigation 1 4 observations / questions in your lab log book.'''
== Investigation 25: How are LVMs managed using system-config-lvm? ==
'''Perform this investigation on the VM named ''<u>fedora2</u>''.'''
<li>Try shrinking the home file-system. What happens? Why?</li>
</ol>
'''Answer the Investigation 2 observations / questions in your lab log book.'''
== Investigation 3: How are LVMs managed using Command-Line Tools? ==
'''Perform this investigation on the VM named ''<u>fedora3</u>''.'''
{{Admon/note|Only Take Notes - Do not Execute Commands|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. You are required to record the Linux commands to acheive the same results as in '''Investigation #2'''. You are '''<u>not</u>''' required to issue those commands on your '''fedora3''' VM.|}}
# Take time to view the following reference for LVM management via command line: [[Logical Volume Management]]
<ol>
<li value="2">Write down the exact commands used at each step as well as command output in your Lab3 log-book:
<!--
MURRAY: I commented out this section because the VG does not have available space with the new lab2 configuration. -CTyler
<li>Grow the '''home''' filesystem to '''2G''' using the command <code>lvextend</code>.</li>
<li>Create a '''new 2G LV''' containing an ext4 filesystem and mount it at '''/archive'''. See important note below:</li>
</ol>
{{Admon/note|Learn How to Learn|Refer to the section called '''Using LVM''' and sub-section '''Filesystems on LVs''' in [[Logical Volume Management]] to complete part "c".|}}
<ol type="a">
<li value="4">Reboot your Fedora3 VM to confirm the operation that you performed in the previous step.</li>
<li>Copy the contents of <code>'''/etc'''</code> into <code>'''/archive'''</code></li>
<li>Shrink <code>'''lv_archive'''</code> to '''1G''' (Refer to the section involving reducing file-systems in use [[Logical Volume Management]].<br />You should be using the commands: <code>umount</code>, <code>resize2fs</code>, <code>lvreduce</code>, and <code>mount</code>)</li> -->
</ol>
'''Answer the Investigation 3 observations / questions in your lab log book.'''
= Software Package Management =
== Investigation 4: How do you query the RPM database? ==
RPM maintains a database of installed software. This information is very useful to system administrators. In Lab 3, you queried that database using RPM with the -q argument. 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
'''Perform the following steps:'''
# Using information from the man page for <code>rpm</code>, fill in this information:
{|width="100%" border="1" cellpadding="5"
|-
!Option
!Meaning
!Is this a select-option or a query-option?
|-
| -a
|Select all packages
|select-option
|-
| -l
|
|
|-
| -p ''filename'''
|Select this uninstalled package
|
|-
| -i
|Show the package license, packager, URL, description, and other general information.
|
|-
| -f '''filename'''
|
|
|-
|'''packagename'''
|Select just this package
|select-option
|}
'''Answer the Investigation 4 observations / table contents in your lab log book.'''
== Investigation 5: How do you install and remove software with RPM? ==
# Change to the directory on your Installation DVD containing the file: <code>lynx-2.8.7-7.fc16.x86_64.rpm</code>
# Execute this command: <code>rpm -i lynx-2.8.7-7.fc16.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.2.1-6.fc16.x86_64.rpm</code> and note the result
'''Answer the Investigation 5 observations / questions in your lab log book.'''
== Investigation 6: How do you install and remove software with ''yum''? =Updated backup instructions =
{{Admon/note|Internet Connection|In order for yum to work If you require a connection to the Internet. Establish completed this connection by using the browser to log into SeneNET}} # Change to your home directory. <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.</li> <li>Issue the command: <code>yum remove BackupPC</code></li> <li>Issue an RPM query to verify that BackupPC is no longer installed.</li> <li>Install <code>nled</code> using '''yum'''.</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="8">Unused and unneeded software can present a security risk and ties up disk space needlessly. Find at least 4 other packages that lab correctly - please make sure you're not using on are still making full backups of 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> '''Answer the Investigation 6 observations / questions in your lab log bookvirtual machines.'''
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 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 license of the nautilus 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:'''
# Larger <code>/home</code> nled installed on '''fedora2'''.# Listing of Linux commands to perform Investigation #3 the host (via CLIdisk pack - main system f16host).
# Unnecessary/unused packages have been deleted (list at least 4, and show that they are no longer installed).
# '''nled''' installed on the host (disk pack - main system '''f16host''').
# Answer to this question:
#* What is the license of the '''nautilus''' package?
# Fresh backup of the virtual machines.
= Preparing for Quizzes =
= Preparing for the Quizzes =
# Describe the steps to switch between text-based and graphical consoles on your f16host system.
# List the steps required to swap sizes between lv_root and lv_home logical volumes on your f16host system.
# What is a VG? PV? LV?
# What commands are used to determine VG / PV / LV information?
