Changes

Jump to: navigation, search

OPS235 Lab 3 - Fedora17

2,831 bytes removed, 12:31, 24 September 2018
no edit summary
[[Category:OPS235]]{{Draft}}
[[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: LVM / Logical Volume Management and Software Package / User Management=
==Introduction==
:* In this lab, you are 're going to learn how to properly adjust your various Linux file system sizes by using and managing LVM. :* Also in this lab, you will learn how to add and remove software packages on your different Linux systems. :* You will also learn how to manage users on your Linux systems including the addition, removal or user accounts, as well as managing groups.
==Objectives==:* 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).
#Learn about LVM concepts including Physical / Logical Volumes and Volume Groups.#Learn how to properly resize file-systems using LVM, and understand the consequences to the filesystem due to mistakes.#Learn how to add and remove software packages using RPM.#Learn how to manage user accounts (add, remove).#Learn how to manage groups to allow / deny user access to files and directories.  ==Required Materials (Bring to All Labs)== * '''Fedora 16 LIVE CD''' - You can burn this onto a CD-R in the Open Lab* '''Fedora 16 x_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).
* Fedora 17 LIVE CD
* Fedora 17 x86_64 Installation DVD
* SATA Hard Disk (in removable disk tray)
* USB Memory Stick
* Lab Logbook
==Prerequisites==
* Completion and Instructor "Sign-off" of Lab 2: [[OPS235 Lab 2]]
 
==Linux Command Online Reference==
|'''LVM Management Utilities:'''
|'''Additional Utilities:'''
|'''User / Group Utilities:'''
|- valign="top"
|
*[http://linuxmanpages.com/man8/vgextend.8.php vgextend]
|
*[http://linuxmanpages.com/man8/mkfsmount.8.php mkfsmount]
*[http://linuxmanpages.com/man8/umount.8.php umount]
*[http://linuxmanpages.com/man8/yum.8.php yum]
*[http://linuxmanpages.com/man8/rpm.8.php rpm]
|
*[http://linuxmanpages.com/man8/useradd.8.php useradd]
*[http://linuxmanpages.com/man8/userdel.8.php userdel]
*[http://linuxmanpages.com/man8/groupadd.8.php groupadd]
*[http://linuxmanpages.com/man8/groupdel.8.php groupdel]
 
|}
 
==Resources on the web==
'''Please read this page to get an overview of LVM:'''<br /><br />
:* [[Logical Volume Management]] ('''Note:''' It is recommended to return to this guide as a reference when performing the next several investigations)
:*<span style="color[http:red;background-color:yellow;">Package Management</span>/fedoranews.org/alex/tutorial/rpm/ Using the RPM Utility]:*<span style="color[http:red;background-color:yellow;">User / Group Management</span>www.centos.org/docs/5/html/yum/ Using the YUM Utility]
=Logical Volume Software Package Management=
== First Preparation Investigation 1: How do you query the RPM database? ==
=== Check LVM Information for all Fedora 16 Installs ===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'''
'''LVMPerform the following steps:''' ('''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 represent specific portions of a file-system (directories) for that physical volume, or for a "range" or "span" of physical volumes.
Thus, LVM allows more flexibility and growth potential # Using information from the man page 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<code>rpm</code>, or later install and use Logical Volume Management.fill in this information:
It is important for students {|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 gain an understanding of LVM, the sub-directory called '''Packages''' and how then go to manage their 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-8.fc17.x86_64.rpm</code># Execute the following command: <code>rpm -i lynx-systems using LVM2.8.7-8.fc17.x86_64. It rpm</code># Issue an RPM query to check that lynx is recommended for students to read installed. Record this command in your lab log-book.# Issue the following resource prior 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> andnote the result '''Answer the Investigation 2 observations /or return 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 following resource while performing Internet. Establish this lab: [[Logical Volume Management]]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 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.
 
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.
 
'''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 32|Lab 32]] you should have <u>roughly</u> the following disk storage setup:<br />('''Note:''' These results are output from the '''vgs''', '''lvs''', and '''pvs''' commands within that provide volume group, physical volume and logical volume information for each of the virtual machinemachines that you created in lab2. You will be using Before proceeding, check these commands in values with your own system to see if you are generally "on the following lab investigations)right track".<br /><br />
* '''fedora1'''
* '''fedora2'''
VG #PV #LV #SN Attr VSize VFree vg_fedora2 1 2 3 0 wz--n- 14.50g 03.25g
PV VG Fmt Attr PSize PFree
/dev/vda3 vg_fedora2 lvm2 a-- 14.50g 03.25g
LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_root lv_home vg_fedora2 -wi-ao 131.03g 97g lv_swap lv_root vg_fedora2 -wi-ao 17.47g 81g PV VG Fmt Attr PSize PFree /dev/vda2 lv_swap vg_fedora2 lvm2 a- 14wi-ao 1.80G 4.07G47g
* '''fedora3''' ''' (Note: This VM has no GUI installed.)'''
VG #PV #LV #SN Attr VSize VFree
lv_swap vg_fedora3 -wi-ao 520.00m
PV VG Fmt Attr PSize PFree* '''f17host (i.e. "removable hard disk" or "disk pack")'''  Does not use LVM. Confirm this using the same commands used above. {{Admon/dev/vda2 vg_fedora3 lvm2 note|VM Backups and Recovery|Most of these investigations will take place in your virtual machines. If you make a- 9significant mistake, your virtual machine may not boot.80G 3Remember that you created backups of your virtual machines in Lab 2, and you can restore them if something goes wrong.83G<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!'''|}}
* '''f16host (i.e. "disk pack")'''== Investigation 4: Extend the size of lv_root using command-line tools ==
VG #PV #LV #SN Attr VSize VFree vg_f16host 1 3 0 wz--n- 232Perform this investigation in fedora3.38g 0
PV VG Fmt Attr PSize PFree 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/dev/sda3 vg_f16host lvm2 a-- 232restore of the data.38g 0
LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_home vg_f16host Because we're using LVM though -wi-ao 176.62g lv_root vg_f16host -wi-ao 50we can avoid that.00g lv_swap vg_f16host -wi-ao 5We 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.75g
'''Perform the following operations to increase the size of lv_root in fedora3:'''
{{Admon/note|Recovering VMs|<u>'''Most of these investigations will take place in you virtual machines.<font>Steps:</font>''' If you make a significant mistake, your virtual machine may not boot. Remember that you created backups of your virtual machines in Lab 3, and you can '''restore them if something goes wrong'''.}}</u>
== Second Preparation ==<ol> <li>Run the following commands and make note of the output:</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 volume group, and extend lv_root:</li> <code>pvcreate /dev/vdb
=== Adjust Storage Size in f16host === vgextend vg_fedora3 /dev/vdb
If you refer to the LV sizes of f16host, you may notice that the size of ''' lvextend -l +100%FREE -r vg_fedora3/lv_root''' (your root system) is quite small compared to the size of '''lv_home'''. Since virtual machines that you have created are stored in the directory pathname </code> <li>Now rerun the ls/varpvs/libvgs/libvirtlvs/imagesdf commands. What has changed and what caused those changes?</li> </codeli>Among the changes, then it is important note that there your root filesystem is ample space to accommodate future Virtual Machines (eg. assignments) or future growth of filenow 2GB bigger -systems. and you have not even rebooted your machine!</li></ol>
Therefore, before proceeding with Lab3 investigations, you will be required to make a readjustment'''Answer the Investigation 4 observations / questions in your lab log book.'''
== Investigation 5: How are LVMs managed using system-config-lvm? ==
== Investigation 1: How are LVMs are managed using system-config-lvm? ==
'''Perform this investigation on the VM named ''<u>fedora2</u>''.'''
[[Image:Ops235_lab4_1.png|thumb|right|Screenshot of system-config-lvm in Fedora. Click to enlarge.]]
# Let's learn to administer (manage or administer ) our LVM graphically for our Virtual Machine ('''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 System'''Application'''>Administration'''Other'''>'''Logical Volume Management'''. Verify that this The package is presentmay not be installed by default, and so you will need to install it if required 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 PVs'''PV'''s?</li>#* <li>What is the name and size of the '''VG'''?</li>#* <li>What are the names and sizes of the LVs'''LV'''s?</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 filesystem 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 ''' (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 name, size, filesystem, 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 graphical 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'''.# Try shrinking <code/li>/ </codeli> Try shrinking the home file-- what system. What happens? Why?</li></ol>
== Investigation 2: How are LVMs are managed using Command-Line Tools ==# You are going to repeat the same LVM management operations (as your did with the ''fedora2'' VM), but you will using command-line tools Answer the Investigation 5 observations / questions in the '''fedora 3''' VMyour lab log book. Since the fedora3 VM only operates in command-line mode, you will need to refer to the '''"Logical Volume Management"''' link above.# Write down the exact commands used at each step, and record appropriate command output:## Determine the current LVM configuration using the <code>pvs</code>, <code>vgs</code>, and <code>lvs</code> command.## Grow the home filesystem to 2G using the command <code>lvextend</code> and <code>resize2fs</code>.## Create a new 2G LV containing an ext4 filesystem and mount it at /archive (use <code>lvcreate</code>, <code>mkfs</code>, <code>mount</code>, edit the file <code>/etc/fstab</code>, and then reboot to confirm automatic mount).## Copy the contents of <code>/etc</code> into <code>/archive</code>.## Shrink <code>lv_archive</code> to 1G (use <code>umount</code>, <code>resize2fs</code>, <code>lvreduce</code>, and <code>mount</code>)
=Updated backup instructions = Investigation 3: How can a PV be added to an existing VG? =='''Add an additional 2 GB virtual disk to your ''<u>fedora1</u>'' system, and use it as an additional physical volume:'''# Start <code>virt-manager</code>.# Shutdown ''fedora1'' if it is running.# Open the console window for ''fedora1''.# Select the menu option View>Details.# Click ''Add Hardware'' button at the bottom left-hand corner.# In the ''Adding new virtual hardware'' window that appears, select a Hardware Type of ''"storage"'' and click ''"Forward"''.# Make certain option "Managed or other existing storage" is selected. Click on the ''Browse'' button, then click on ''New Volume''.# Give the new virtual disk file a name of <code>fedora1b</code>, a format of ''raw'', with a ''Max Capacity'' and ''Allocation'' of 2000 MB. Click ''Finish''.# Select the new virtual disk file ''fedora1b.img'' and click ''Choose Volume''.# Select a device type of ''Virtio Disk''.# Finish creating the new virtual disk by clicking ''Forward'' and then ''Finish''.# Boot the system. You should now have both <code>/dev/vda</code> and <code>/dev/vdb</code>.# Record the size of the volume group and the amount of free space <span class="plainlinks">[http://www.inleds.com/products/?cid=2<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"> led downlight singapore</span>](Hint: use a command that you learned in a previous lab).# Partition /dev/vdb with a single partition that fills the whole disk.# Check the messages printed when <code>fdisk</code> exits -- you may need to reboot the system in order for the new partition table to take effect.# Run this command to format the physical volume: <code>pvcreate /dev/''vdb1''</code># Add the new physical volume to the existing volume group: <code>vgextend ''nameOfVolumeGroup'' /dev/vdb1</code># Verify that the volume group is larger and has more free space.
{{Admon/note|Think!|The next part of If you completed this investigation requires some research, thought, and creativity.}}'''Using that additional space, create a separate filesystem for <code>/home</code>:'''# Create the logical volume <code>lv_home</code> (1G ext4)# Find a way to move the contents lab correctly - please make sure you are still making full backups of <code>/home</code> onto it.# Change your system configuration so that the new filesystem is mounted on <code>/home</code> from now onvirtual machines.
{{Admon/tip|SELinux relabelling may be required|Your system may report Remember adding a new harddrive to fedora3? You will need to back up that the files are not present in the new /home filesystem when they are clearly theredrive as well. This is due to the SecurityIf you don't -Enhanced Linux system (SELinux) preventing access to the filesyou will only have half of your machine backed up, because the files were tampered with (moved) and are which is of no longer recognized as home directory contentuse for a recovery. You can fix this problem by restoring the file context labels so that SELinux accepts the files as valid home directory content: <code>restorecon -r /home</code>}}
== Investigation 4: How can I use LVM to manage storage on my disk pack? =='''On your <u>f16host</u> (i.e. "disk pack"), using your choice of the GUI and/or command-line tools:'''# Create a new logical partition ('''NOT a logical volume!''') - minimum 5G, leaving at least 10G free space in the extended partition.# Add that partition as a PV into the existing VG (using the commands you used in the previous investigation).# Grow the root filesystem to fill the available space. = Package Management = == Investigation 5: 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 Steps: 1. Using information from the man page for <code>rpm</code>, fill in this information:{|width="100%" border="1"|-!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 Completing the package license, packager, URL, description, and other general information.| |-| -f '''filename'''| | |-|'''packagename'''|Select just this package|select-option|} Make sure that your lab notes answer the Investigation 5 question. == Investigation 6: 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-2.fc16.x86_64.rpm</code># Execute this command: <code>rpm -i lynx-2.8.7-2.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.1.0-16.fc16.noarch.rpm</code> and note the result Answer the Investigation 6 question.
== Investigation 7: How do you install and remove software with ''yum''? == {{Admon/noteimportant|Internet ConnectionTime for a new backup!|In order for yum to work If you require a connection to the Internet. Establish have successfully completed this connection by using the browser to log into SeneNET}} # Change to your home directory. # Issue the command: <code>yum install BackupPC</code> and answer <code>y</code> to the question about installation.#* Where did ''yum'' get the BackupPC software?#* Why could ''yum'' install BackupPC when rpm couldn't?# Issue an RPM query to verify that BackupPC is installed.# Issue the command: <code>yum remove BackupPC</code># Issue an RPM query to verify that BackupPC is no longer installed.# Install <code>nled</code> using '''yum'''.# Issue this command: <code>yum info cups</code>#* Based on the resultlab, do you think that cups is make a useful package for new backup of your system? If not, try removing itvirtual machines.# 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. Answer the Investigation 7 question.   = 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. Remember to also make a backup of the new second virtual disk drive on ''fedora1'Notes:' -- you now have two virtual disks on ''fedora1'', and therefore two image files, and therefore will need two backup files.}}# 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 proof evidence for each of the following these items on the your screen:# Two PVs , then ask your instructor to review them and sign off on the lab's completion:''fedora1'''.# Separate <code>/home</code> filesystem nled installed on the host (on an LVdisk pack - main system f16host) in '''fedora1'''.# Larger <code>/home</code> on '''fedora2''' and '''fedora3'''.
# Unnecessary/unused packages have been deleted (list at least 4, and show that they are no longer installed).
# Account created on '''fedora3''' matching your Matrix account.
# '''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 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 add the disk partition <code>/dev/sdb7</code> to your volume group "main"?
# How would you increase the size of the root filesystem by 50 MB?

Navigation menu