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.'''}} = Fedora 19 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3) =
== Introduction ==
:* '''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).
You should already have both a '''Fedora installation DVD''' and a '''Fedora LIVE DVDCD'''.
In both cases, the boot media (which you used to load the installation software) and the installation source (the software that got installed) were the same: your CD/DVD provides both. However, the Fedora (and most other Linux distributions) permits you to use any combination of boot media and installation media:
|
! Install. Source
|-
! CD or DVD
! ✓
! ✓
! ✓
! ✓
|-6
! PXE Network Boot
! ✓
== Required Materials (Bring to All Labs) ==
* Fedora 19 17 LIVE CD* Fedora 17 x86_64 Installation DVD
* SATA Hard Disk (in removable disk tray)
* USB Memory Stick
* Lab Logbook
==Prerequisites==
:* '''virsh''' (Refer to Fedora Virtualization Guide link in the "Resources on the Web" section)
:* [http://linuxmanpages.com/man1/gzip.1.php gzip / gunzip]
== Resources on the Web ==
|- valign="top"
|
[http://docs.fedoraproject.org/virtualization-guide/f13/en-US/Fedora/19/html/Virtualization_Getting_Started_Guide/index.html Fedora Virtualization Getting Started Guide]
|
* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Fedora_Live_Images/ Fedora 17 Live Image Guide]* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Quick_Start_Guide/ Fedora 19 17 Installation Quick Start Guide]
|
[http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ Fedora 19 17 Installation Guide]* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86/ Preparing for a Network Installation]* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86 Performing a Network Installation]
|
[http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ Fedora 19 17 Installation Guide]* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/sn-automating-installation.html Automating the Installation with Kickstart]* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ch-kickstart2.html Kickstart Installations]* [http://docs.fedoraproject.org/en-US/Fedora/1917/html/Installation_Guide/ch-redhat-config-kickstart.html Kickstart Configurator]
|}
# '''Open a web-browser''', and open the '''OPS235 Lab #2 WIKI'''. '''<br /><br />NOTE:''' You need to enter your "MySeneca" username and password to obtain a "wired" Internet connection (otherwise, you will not be able to perform the "groupinstall" command in the next step). Remember to perform a "wired-connection" (logging in with your MySeneca username and password via a web-browser) every time you boot-up your host machine...<br /><br />
# Open a shell terminal, and login to Install the root account.Fedora virtualization software: <code>yum groupinstall "Virtualization"</code> or <code>pkcon install @virtualization</code> The virtualization software installed is in three parts: {{Admon/tip|Remember to use :* '''A system service named ''libvirtd''su -''' prior to running administration commands|A common mistakes students make in OPS235 is to forget to log into that manages the root account prior VMs.:* '''Tools to running administration commands. Therefore, if a command doesnmanage virtualization'''t work, ask yourself, "is this is an administration including the <code>virt-manager</code> graphical tool and the <code>virsh</code> command?"}}-line tool.:* The actual '''virtual machines''' themselves.
<ol>
</ol>
{{Admon/tipcaution|More About KVMReboot your fedora host now| The KVM virtualization software installed is in three parts:<ol><li>'''A system service named ''libvirtd''''' that manages the VMs.</li><li>'''Tools to manage virtualization''', including the <code>virt-manager</code> graphical tool and may not work properly unless you reboot after installing the <code>virsh</code> command-line tool.</li><li>The actual '''virtual machines''' themselvesvirtualization software.</li></ol>}}
<ol>
<li value="45">Start After rebooting your computer system, and logging back into your account, start the virtualization service using graphical tool by selecting the systemctl command: <codemenu options '''Activities'''>'''systemctl start libvirtd.serviceApplications'''</code></li> <li>The firewall configuration is altered by the addition of the virtualization software. Restart the firewall so that these changes become active: <code'''System Tools'''>'''systemctl restart iptables.serviceVirtual Machine Manager'''or by typing the command <code>virt-manager</code></li>
</ol>
{{Admon/tipimportant|Maybe reboot your fedora host nowRun virt-manager as a regular user|Sometimes Running virt-manager does as root may not work properly unless you reboot after installing the virtualization softwaredue to configuration issues.}}
== Investigation 1: Installing from a Live Disc ==
==== Introduction ====
In this investigation, you will install Fedora from your live disc, and observe the differences between this type of installation and the DVD installation previously performed.
==== VM Details ====
* '''Name:''' fedora1
* '''Boot media:''' Fedora 19 Desktop Live DVDCD* '''Installation source:''' Fedora 19 Desktop Live DVDCD* '''Memory:''' 1024MB768MB* '''Disk space:''' 15GB10GB
* '''CPUs:''' 1
# In the Virtual Machine Manger, click on the icon to ''Create a Virtual Machine'' in the upper-left corner: <br />(refer to '''Virtual Machine Manager''' thumbnail above).
# A window will appear with the title ''New VM''. There are five steps to be completed; click Forward after each step:
# '''Step 1 of 5:''' Enter the virtual machine (called '''fedora1''') name and select '''Local install media (ISO image or CDROM)''' (refer to ''Step 1 of 5'' thumbnail above).# '''Step 2 of 5:''' '''Insert the CDROM or DVD containing the Fedora Live Disc image. Wait a moment for the disc to be recognized''', You should see a black dialog box appear that recognizes the DVD. Click on the black box to confirm.# Click the '''Forward''' Button.# Under "Location your install media section", then select "'''Use CDROM or DVD'''"as the install media. Set the ''OS type'' to '''Linux''' and the ''Version'' to '''Fedora 1917''' (refer to ''Step 2 of 5'' thumbnail above), then click the '''Forward''' Button.
<!-- {{Admon/tip|Using an ISO image|Instead of using a physical CD or DVD, you can use an ISO image of a CD or DVD. The virtualization software will make this ISO image appear like an actual CD within the virtual machine. Because hard disks are faster then optical discs, this will work faster than an actual CD/DVD.}}{{Admon/note|Choosing the operating system type and version|The purpose of the ''OS type'' and ''Version'' fields is 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 5:''' Set the memory to '''1024 768 MB''' and the number of CPUs to '''1''' (refer to ''Step 3 of 5'' thumbnail above), Then click the '''Forward''' button.# '''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 '''15 10 GB''' and check-mark checkmark the box labelled labeled '''Allocate entire disk now''' (refer to ''Step 4 of 5'' thumbnail above), then click the '''Forward''' button.
# '''Step 5 of 5:''' Review the options that you have selected. '''Make a note of the storage location.''' If anything needs to be changed, use the ''Back'' button to go back and edit it; otherwise, click '''Finish''' (refer to ''Step 5 of 5'' thumbnail above).
{{Admon/note|Fedora LIVE DVD CD Install Screen Shots Thumbnails|While performing the Fedora 19 17 LIVE DVD CD install, click on the thumbnails below to provide a '''"visual reference"''' while performing this particular Fedora installation.
}}
|}
<ol>
<li value="108">'''The virtual machine will now start'''. Select the default menu item labelled: '''Install to Hard DriveStart Fedora 17'''. The virtual machine is running from the live disc at this point, and no software has been installed on the ''hard drive'' of the virtual machine. </li>
</ol>
<ol>
<li value="9">Login to the VM and click: '''Applications'''>'''System Tools'''>'''Install to Hard Drive'''. The installation program, similar to the one used when installing Fedora in Lab 1, will appear. You will get a warning at one point during the installation process that the disk "May contain data" or "may need to be re-initialized" -- this is simply a warning that the virtual disk is completely blank, and it is safe to proceed with the installation.</li>
</ol>
{{Admon/note|Virtual Machine Screen Size|The virtual machine screen size will change resolution as it switches from text to graphics mode. Use the VM menu option View>Resize to VM to resize the window to show the entire VM display. If this is larger than your screen size, use View>Scale Display>Always to scale the image so it fits on your screen.
}}
<ol>
<li value="1110">The Installation Summary dialog box will appear (similar to what you encountered in lab1 for your full DVD install). It is assumed that you will be familiar with the general steps on During the installation process. <li>Set the Time Zone , when prompted for "a storage device, first select '''TorontoSpecialized Storage Devices'''".</li> <li>When back at the main installation summary menu, and then select the '''Installation DestinationVirtio Block Device'''option.</li> <li>In When prompted for the Installation Options dialog box Confirm approx. hostname, enter '''15 GBfedora1''' , and when prompted for the timezone, select '''Virtio Block DeviceToronto - Eastern Time Ontario''' , and click the when asked about storage, select '''DoneUse All Space''' button in the top left-hand corner. '''Note: It may take a few minutes to access Use the <u>next</u> Installation Options dialog box, so please be patient!default values for all other fields.'''</li> <li>Click "'''I want to review/modify my disk partitions before continuing'''", confirm Notice that the partition scheme is set installer does not ask you what software should be installed; compare the installation time to '''LVM''', and click the '''Continue''' button.</li> <li>In the Manual Partitioning dialog box, click on the link "'''Click here amount of time it took to create them automatically'''"</li> <li>Review the automatically created partitions in the next dialog boxdo your Lab 2 installation. Record this information in your lab log-book the partition names and related sizes, and note the virtual hard disk device name (i.e. vda1). </li>Click the '''Donetable contained in Investigation 4''' button at the top left-hand corner.</li> <li>Confirm When the Summary of Changesinstallation is complete, and then click on the "'''Accept Changesreboot'''" button located on at the bottom right-hand side. Note: please be patient, and wait a few minutes until you can access corner of the Installation Summary dialog box. Click Begin Installation. Note the time that it takes to complete this installation.</li> <li>During the installation process, set a root password and create a least one regular user accountscreen.</li> </ol> {{Admon/tip|Screen Lock|If during the install process, the screen locks, drag the mouse upwards, and simply press enter to unlock the screen (no password is required for a live user).|}}
<ol>
<li value="2013">After Start the installation process has completedVM from its disk image. This can be done graphically by selecting the Virual machine name, click and then clicking on the '''QuitOpen''' button. This should return you to the LIVE version of Linux that was running to help install to the Hard Drive. Click on the live username located at the top right-hand corner , and power-off then click the machine. It is recommended to completely shutdown the virtual machine, then '''start your fedora1 virtual machineplay''' button when the next screen appears (or by selecting Virtual Machine>Run from the virtual machine manager windowmenu).</li> <li>Open You will get the ''Firstboot'' configuration questions during the boot process (asking you to create a terminal (shell)user, set the date and time, and log into root.</li> <li>Change your host name optionally send the hardware profile to fedora1 (refer to last week's notesthe Fedora Project).</li> <li>Use Create a user with the <code>hostname</code> command to verify that you set same name as your hostname to "fedora1"Matrix account.</li> <li>Compare the installation time to Login using the amount of time it took to do this type of installation. Record this information in the '''table contained in Investigation 4'''new user account.</li>
</ol>
{{Admon/note|Network / Service Considerations|Please perform the tasks below in order allow these Fedora systems to be able to communicate with each other. '''Failure to properly perform these operations can cause problems in future labs'''.|
<ol>
<li value="2515">Enable SSH access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):<br /> <code>systemctl service sshd start sshd; systemctl enable chkconfig sshd.serviceon</code></li>
<li>Find out the IP address of your virtual machine: <code>ifconfig eth0</code> </li>
<li>Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine:<br /> <code>iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT</code></li>
* '''Name:''' fedora2
* '''Boot media:''' Network installation
* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/1917/Fedora/x86_64/os/* '''Memory:''' 768MB1024MB* '''Disk space:''' 15GB20GB
* '''CPUs:''' 1
# Create the VM (called '''fedora2''') 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 location of the software source by providing the URL http://belmont.senecac.on.ca/fedora/releases/1917/Fedora/x86_64/os/#* In '''step 2 of 5''', set the ''OS Type'' to '''Linux''' and ''Version'' to '''Fedora 1917'''. # Observe the boot process. How is it different from booting from an optical disc (CD/DVD)?
# Start the installation process (make certain to use information in the ''VM Details'' section above).
# When you get to the disk partitioning step, select '''Use All Space''' and enable the checkbox labelled '''Review and modify partition layout'''.If an dialog box displays a permissions problem, then click yes to proceed. On the next screen, change the logical volumes as follows:
#* '''Add a logical volume with a size of 2000 MB and a mountpoint of /home''' (you can name it whatever you want, and use '''ext4''' as the file-system type).
# On the software selection screen, select '''Graphical Desktop'''.
# '''On the same screen, select the "Fedora 19 17 - x86_64" and the "Fedora 19 17 - x86_64 - Updates". Leave "Installation Repo" selected. ''DO NOT'' enable the "Test Updates" repository'''.
# Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations.Record this information in the '''table contained in Investigation 4'''.
* '''Name:''' fedora3
* '''Boot media:''' Network installation
* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/1917/Fedora/x86_64/os/* '''Kickstart location:''' http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora19Fedora17-kickstart.cfg* '''Memory:''' 768MB1024MB* '''Disk space:''' 10GB15GB
* '''CPUs:''' 1
# Create the VM as you did with the ''fedora2'' virtual machine, specifying a network install as before, except:
#* In step 2 of 5, after entering the URL for the installation source, click on the '''URL Options''' control.
#* Enter the Kickstart URL: http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora19Fedora17-kickstart.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?
{|border="1" width="100%" cellpadding="5"
|-
! ||f19hostf17host||fedora1||fedora2||fedora3
|-
|'''Installation Method'''||Installation Disc||Live Disc||Network Installation||Network Installation + Kickstart
# Switch to your terminal and issue the command: <code>'''virsh start fedora1'''</code>
# Check to see if your fedora1 VM is now running.
# Switch to the terminal and issue the command: <code>'''virsh list --all'''</code> and confirm the status of the fedora1 VM.# There are other commands that can be used (such as ''suspend'', or ''shutdown''). The "shutdown" command may not always work since it sends a request to "shutdown virtual machine gracefully", but may not always work. Why do you think it is useful to have commands to manipulate VMs?
{{Admon/note|Virtual Machine Does not Shutdown from Command|If the Virtual machine fails to shutdown from the <code>virsh shutdown</code> command, then you can go to the '''Virtual Machine manager''' and '''halt''' or '''shutdown''' within the VM itself, then you can click the '''PowerOff''' button in the VM window. You'll want to avoid a forced shutdown since those are equivalent to yanking the cord out of the wall on a physical machine!|}}
# Shut down all of the virtual machines.
# Change to the directory <code>'''/var/lib/libvirt/images/'''</code>. Note the size of the files in this directory. What do these files contain?
# Make a compressed backup of the <code>fedora3.img</code> file to your home directory with this command: <code>'''gzip < fedora3.img > ~YourUserId/fedora3.img.backup.gz'''</code><br />('''Note: Make certain to use the redirection signs "<" and ">" properly in the command!''')
{{Admon/caution| Make sure the backup is successful!|If there are any error messages, '''DO NOT''' proceed past this point. You're going to destroy your fedora3 virtual machine and restore it using the backup you have created -- if there are any problems with the backup, you will not have a working virtual machine, and will have to re-install it.}}
<ol>
<li value="12">You should make a copy of the xml configuration file in case you "wipe" and re-install the host machine, and want to add a restored VM backups to the virtual machine manager list. We will demonstrate using the fedora 3 xml configuration file, and prove that a "clone" can be added to your list.Please perform the following step:<ol type="a">
<li>Verify that you are in the directory: <code>'''/var/lib/libvirt/images/'''</code>.</li> <li>Execute the following command: <code>'''virsh dumpxml fedora3 >fedora3.xml'''</code></li>
<li>Examine the file <code>fedora3.xml</code>. What does it contain? What format is it in?</li>
<li>Make a copy of <code>fedora3.xml</code> called <code>fedora3a.xml</code>.</li>
::* Change at least one of the hexadecimal characters in the UUID. Do not change the length of the UUID. Valid hexadecimal characters are 0-9 and a-f.
<ol type="a" >
<li value="6">Issue this command: <code>'''virsh define fedora3a.xml'''</code> <li>Issue the command <code>'''virsh list --all'''</code> and record any changes. <li>Issue the command: <code>'''virsh undefine fedora3a'''</code>
<li>List all of the virtual machines again, and note any changes. </li></ol>
<li>For the remainder of these labs, it is assumed that you will backup <u>'''both'''</u> the images and xml configuration files for <u>'''all'''</u> Virtual machines, when asked to backup your virtual machines. It is also highly recommended to backup these files to an external storage device (eg. USB key) in case the host machine gets "wiped" and you need to rebuild your HOST machine and then restore your Virtual Machines...</li>
When you perform a non-Kickstart installation, the installation program creates a Kickstart file in the <code>/root</code> directory for reference.
# Obtain the kickstart files for all four of your installations (your disk pack '''''f19host'''f17host'', plus the '''''fedora1''''', '''''fedora2''''', and '''''fedora3''''' virtual machines).
# To prevent confusion, copy your kickstart files to kickstart filenames that describe their purpose (eg. kickstart_host, kickstart_fedora1, kickstart_fedora2, etc...)
# Copy them all to your f19host f17host system (tip: use <code>'''scp'''</code>), or use the hint in the tip box above to '''send via e-mail'''.# Compare these files. What are the differences? Similarities? (Tip: you may want to use tools such as <code>'''sdiff'''</code> to help with the comparison).
# How could you use the kickstart file produced by the installation program to perform additional, identical installations?