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.'''}}=OPS235 Lab 3: Logical Volume Management and Software Package Management=
==Introduction==
== Required Materials (Bring to All Labs) ==
==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]
=Logical Volume 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'''
# 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? == # 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 '''Answer the Investigation 2 observations / 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 />
* '''fedora1'''
lv_swap vg_fedora3 -wi-ao 520.00m
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 backup/restore of the data.
<u>'''<font>Steps:</font>'''</u>
<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 '''Ctrl-Alt-F3''' to a switch to a textls /dev/vd* pvs vgs lvs df -based Virtual Terminalh</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 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>''.'''
<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? What would you think would happen if you further reduced the size of your home file-systemWhy? </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 #1. 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: <ol type="a"> <li>Determine (and write down) the current LVM configuration using the <code>pvs</code>, <code>vgs</code>, and <code>lvs</code> command.</li><!-- 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> </li>
</ol>
'''Answer the Investigation 5 observations / questions in your lab log book.'''
= Updated backup instructions =
{{Admon/important|Time for a new backup!|If you have successfully completed this lab, make a new backup of your virtual machines.}}
'''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''' and '''fedora3'''the host (disk 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 the Quizzes =
# What is a VG? PV? LV?
# What commands are used to determine VG / PV / LV information?
# What does yum do that rpm does not?
# List the steps to install a package via rpm command.
# List the steps to determine detailed information regarding an install package.
# List the steps to remove a package via rpm command.
# List the steps to install a package using the yum command.
# List the steps to remove a package using the yum command.
# What is the total size of the "main" VG on your system?
# How do you create a LV?
# How do you delete an LV?
# How would you increase the size of the root filesystem by 50 MB?