1,576
edits
Changes
no edit summary
[[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=
:* 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).
== Required Materials (Bring to All Labs) ==
* Completion and Instructor "Sign-off" of Lab 2: [[OPS235 Lab 2]]
==Linux Command Online Reference==
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 aboutto 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:'''
!Option
!Meaning
!Is this a select-option Select or a query-option?!Example command
|-
| -a
|Select all packages
|select-option
|
|-
| -l
|
|
|
|-
| -i
|Show the package license, packager, URL, description, and other general 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? ==
# Change Use the graphical file manager (Nautilus) to change to the directory on your Installation DVD containing . 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 filecalled: <code>lynx-2.8.7-78.fc16fc17.x86_64.rpm</code># Execute this the following command: <code>rpm -i lynx-2.8.7-78.fc16fc17.x86_64.rpm</code># Issue an RPM query to check that lynx is installed.# ___________________________________________________Record this command in your lab log-book.# Issue this 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 this the following command: <code>rpm -i BackupPC-3.2.1-67.fc16fc17.x86_64.rpm</code> and note the result
'''Answer the Investigation 2 observations / questions in your lab log book.'''
</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>
'''Answer the Investigation 3 observations / questions in your lab log book.'''
=Logical Volume Management(Introduction)=
== Check Current LVM Information 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.
At this point, having completed [[OPS235 Lab 2|Lab 2]] you should have roughly 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 />
* '''fedora1'''
lv_swap vg_fedora3 -wi-ao 520.00m
* '''f16host f17host (i.e. "removable hard disk" or "disk pack")'''
Does not use LVM. Confirm this using the same commands used above.
{{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 4: Adjusting Sizes Extend the size of lv_root and lv_home == using command-line tools === Why Readjust sizes of lv_root and lv_home? === If you refer to the LV sizes of your '''f16host''', you may notice that the size of '''lv_root''' (your root system) is quite small compared to the size of '''lv_home'''. The Virtual Machines that you have created are stored in the directory pathname <code>/var/lib/libvirt/images/</code>, and since you are required to make backups and create future VMs (assignments), you will run out of space!
Because 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, and extend the root logical volume to make use of the new available space.
'''Perform the following operations to redistribute increase the sizes size of lv_root and lv_home in f16hostfedora3:'''
<u>'''<font>Steps:</font>'''</u>
<ol>
<li value="2">'''Log-off all users on Run the GUI'''. You won't be able to complete this procedure if any users other than "root" are logged in. <br />OR You can go into Runlevel 1 by using following commands and make note of the command "init 1" (without the quotes) in the terminal.output:</li> <licode>Press the keyboard combination '''Ctrl-Alt-F2''' to a switch to a textls /dev/vd* pvs vgs lvs df -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
</ol>
'''Answer the Investigation 5 observations / questions in your lab log book.'''
== Investigation 6: How are LVMs managed using Command-Line Tools? =Updated backup instructions =
= 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).
# Fresh backup of the virtual machines.
= Preparing for Quizzes =
# What is a VG? PV? LV?
# What commands are used to determine VG / PV / LV information?
