1,576
edits
Changes
no edit summary
[[Category:OPS235]][[Category:OPS235 Labs]]
==Objectives=Fedora 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3) =
:* Resources '''Software testing''' -- Using multiple operating systems simultaneously on the weba single computer for testing and experimentation.:** [http://fedora.redhat'''Network simulation''' -- Testing network services, protocols, and security scenarios with a small number of computers.com/docs/release-notes/ Fedora Release Notes]:** [http://docs'''Isolation''' -- Protecting multiple sets of data by storing them on multiple virtual machines.fedoraprojectIf one of the virtual machines is compromised, the data on other virtual machines is still protected.org/install-guide/ Fedora Installation Guide]:** [http://www'''Server consolidation''' -- Reducing the number of physical servers in a network by moving physical machines to virtual machines.gnuThis saves hardware, administration, cooling, and electricity costs, and it can increase the utilization of hardware (by ensuring that the hardware is not under-loaded).org/software/grub/manual/html_node/Security.html#Security Protecting Grub]:** [http://opensource.sgi.com/LDP/HOWTO/Kernel'''Load-HOWTO/grubconf.html Grub Details balancing and Sample Config]** [http://www.aspencrypt.com/crypto101_hash.html Onedisaster recovery''' --way Hash Function]** [http://www.dedoimedo.com/It is possible to migrate virtual machines between different physical machines, to ensure that a workload is balanced across multiple computers/grub.html GRUB Tutorial]** [http://www.securitystats.com/tools/password, to allow routine hardware maintenance and upgrading, and to compensate for hardware failure or other disasters.php Password Security]
{|cellpadding="8" width=Required Material="100%"|- valign="top"|
In this labboth cases, the boot media (which you are going used to install load the installation software) and the installation source (the software that got installed) were the same: your CD/DVD provides both. However, the Fedora (GNU/and most other Linux Distributiondistributions) permits you to your hard disk from DVD.use any combination of boot media and installation media:
==InstructionsObjectives ==
* Fedora 17 LIVE CD
* Fedora 17 x86_64 Installation DVD
* SATA Hard Disk (in removable disk tray)
* USB Memory Stick
* Lab Logbook
== Resources on the Web =={{Admon/tip |Updating Fedoracellpadding="8" width="100%"|- valign="top"| '''Virtualization''':| '''Live Image Installation:'''| '''Network Installation:'''| You need to complete a system update. Start the Firefox web browser, turn off popup window blocking (select ''Edit>Preferences'Kickstart Installation:''', then select the Content tab and uncheck the box to Block Popups), then login to SeneNET. Open a terminal and <code>su -</code> to start a shell as root. Enter the command <code>yum update</code> This will download and install all of the packages that have been updated since the installation DVD image was created. If you complete this command at Seneca it should run quite fast as Seneca College hosts a Fedora Repository mirror.}}
{{Admon/caution|classReboot your fedora host now|virt-manager may not work properly unless you reboot after installing the virtualization software.}} <ol> <li value="5">After rebooting your computer system, and logging back into your account, start the graphical tool by selecting the menu options '''Activities'''>'''Applications'''>'''System Tools'''>'''Virtual Machine Manager''' or by typing the command <code>virt-manager</code></li></ol> {{Admon/important|Run virt-manager as a regular user|Running virt-manager as root may not work due to configuration issues.}} == Investigation 1: Installing from a Live Disc == {{Admon/tip|Using an Image instead of a Live Disc|It is recommended that you perform this installation from your Fedora LIVE CD. As a matter of interest (for future reference), it is possible to install directly from the ISO file you used to burn your Live CD. There are many Internet tutorials that show the individual how to perform that task.}} ==== 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 Live CD* '''Installation source:''' Fedora Live CD* '''Memory:''' 768MB* '''Disk space:''' 10GB* '''CPUs:''' 1 ==== Screen-Shot Thumbnail Reference ==== {{Admon/note|Virtual Machine Screen Shots Thumbnails|While performing the Virtual Machine setup, click on the thumbnails below to provide a '''"visual reference"''' while performing this section.}} {|cellpadding="8" width="100%" |[[Image:Virt-manager1.png|thumb|125px| '''Virtual Machine Manager:''' Create a New Virtual Machine]]|[[Image:Virt-manager2.png|thumb|100px|'''Step 1 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager3.png|thumb|100px|'''Step 2 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager4.png|thumb|100px|'''Step 3 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager5.png|thumb|100px|'''Step 4 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager6.png|thumb|100px|'''Step 5 of 5:''' Create a New Virtual Machine ]]|} ==== Steps ==== # 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''' (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''', then select '''Use CDROM or DVD''' as the install media. Set the ''OS type'' to '''Linux''' and the ''Version'' to '''Fedora 17''' (refer to ''Step 2 of 5'' thumbnail above).<!-- {{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 '''768 MB''' and the number of CPUs to '''1''' (refer to ''Step 3 of 5'' thumbnail above).# '''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 '''10 GB''' and checkmark the box labeled '''Allocate entire disk now''' (refer to ''Step 4 of 5'' thumbnail above).# '''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/important|Removing and Recreating VMs|If for some reason the user wants to remove a Virtual Machine, they can right-click the VM, and select delete in the Virtual Machine Manager. It is recommended to '''"delete the image file" in the remove VM dialog box when removing and then recreating a VM'''. Note: If you fail to properly remove the VM image file, it may affect the hard disk size for the new VM (i.e. use the old smaller size. Make certain to remove that VM image file prior to recreating the VM.|'''}} {{Admon/note|Fedora LIVE CD Install Screen Shots Thumbnails|While performing the Fedora 17 LIVE CD install, click on the thumbnails below to provide a '''"visual reference"''' while performing this particular Fedora installation.}} {|cellpadding="8" width="100%" |[[Image:fedoralive1.png|thumb|100px| The Virtual Machine will now start.]]|[[Image:failedtoload.png|thumb|140px| '''Ignore and close the "Failed To Load" dialog box'''. Search for the panel on the upper-left-hand side of the screen.]]|[[Image:fedoralive2.png|thumb|140px|Login to the VM and double-click:<br /> '''Applications'''<br />>'''System Tools'''<br />>'''Install to Hard Disk'''.]]|[[Image:selectstorage1.png|thumb|100px|Select '''Specialized Storage Devices''']]|[[Image:selectstorage2.png|thumb|100px|Select '''Virtio Block Device'''.]]|[[Image:finishcdinstall.png|thumb|100px|You will get the ''Firstboot'' configuration questions during the boot process.]]|}<ol> <li value="8">'''The virtual machine will now start'''. Select the default menu item labelled: '''Start 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="10">During the installation process, when prompted for a storage device, first select '''Specialized Storage Devices''', and then select the '''Virtio Block Device''' option.</li> <li>When prompted for the hostname, enter '''fedora1''', and when prompted for the timezone, select '''Toronto - Eastern Time Ontario''', and when asked about storage, select '''Use All Space'''. '''Use the default values for all other fields.''' Notice that the installer does not ask you what software should be installed; compare the installation time to the amount of time it took to do your Lab 2 installation. Record this information in the '''table contained in Investigation 4'''.</li> <li>When the installation is complete, click on the '''reboot''' button at the bottom right-hand corner of the screen.</li></ol> <ol> <li value="13">Start the VM from its disk image. This can be done graphically by selecting the Virual machine name, and then clicking on the '''Open''' button, and then click the '''play''' button when the next screen appears (or by selecting Virtual Machine>Run from the virtual machine menu). You will get the ''Firstboot'' configuration questions during the boot process (asking you to create a user, set the date and time, and optionally send the hardware profile to the Fedora Project). Create a user with the same name as your Matrix account.</li> <li>Login using the 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="15">Enable SSH access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):<br /> <code>service sshd start; chkconfig sshd on</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> <li>Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): <code>ssh ''IPaddress''</code></li></ol> {{Admon/tip|Switch to Virtual Machine Manager Window|If you are currently in a Virtual machine, but want to switch to the Virtual Machine Manager Window, simply click '''Activities'''> '''Select the Virtual Machine manager window'''.}} '''Answer the Investigation 1 observations / questions in your lab log book.''' == Investigation 2: Installing from the Network == {{Admon/tip|Authenticate to the network|The rest of this lab uses network access.''' Be sure to authenticate to the network using your browser before proceeding'''.}} === Introduction === It is possible to install Fedora entirely from the network. In this investigation, you will install Fedora from a webserver on Seneca's LAN. ==== VM details ==== * '''Name:''' fedora2* '''Boot media:''' Network installation* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/* '''Memory:''' 1024MB* '''Disk space:''' 20GB* '''CPUs:''' 1 ==== Steps ====# 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/17/Fedora/x86_64/os/#* In '''step 2 of 5''', set the ''OS Type'' to '''Linux''' and ''Version'' to '''Fedora 17'''. # 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:#* Reduce the size of the root LV to '''8000 MB'''.#* '''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 17 - x86_64" and the "Fedora 17 - x86_64 - Updates". Leave "Installation Repo" selected. ''DO NOT'' enable the "mediawikiTest 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'''. '''Answer the Investigation 2 observations / questions in your lab log book.''' == Investigation 3: Installing from the Network using Kickstart == === Introduction === When Fedora is installed using the techniques you have used so far, the user is asked a number of questions. In some situations, it is better to provide the answers to these questions in a file rather than answer them individually. This type of file is called a ''kickstart'' file. In this investigation, a kickstart file is provided for you. You can also create or modify a kickstart file using a regular text editor or a graphical tool. ==== VM details ==== * '''Name:''' fedora3* '''Boot media:''' Network installation* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/* '''Kickstart location:''' http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora17-kickstart.cfg* '''Memory:''' 1024MB* '''Disk space:''' 15GB* '''CPUs:''' 1 ==== Steps ====# 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/Fedora17-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?# '''Take a look at the kickstart file (using the URL you entered) to <u>determine</u> the root password as well as the name and password for the first user account'''.# Boot the virtual machine and log in (use the user ID and password information from the previous step). Compare the experience to the first time you booted the other virtual machines.Record this information in the '''table contained in Investigation 4'''. '''Answer the Investigation 3 observations / questions in your lab log book.''' == Investigation 4: Updating and Comparing the VMs == # In each VM, run this command: <code>yum update</code># Record the answers to these questions in your log book:#* How long did it take to run on each VM? How many packages were updated?#* Why does it take longer in some VMs than others? Complete the following table (and transfer into your lab2 log-book notes): {|border="1" width="100%" cellpadding="5"|-!Runlevel||f17host||fedora1||fedora2||fedora3|-!Description|'''Installation Method'''||Installation Disc||Live Disc||Network Installation||Network Installation + Kickstart|-|'''Packages Installed'''|| || || |||-|'''Updates Installed immediately after installation'''|| || || |||-|'''Software could be selected during installation'''|| || || |||-|'''Disk layout could be selected during installation'''|| || || |||-|'''No questions asked during installation'''|| || || |||-|'''Total installation time''' (after installation questions)|| || || ||
|-
|0'''Amount of disk space used'''|| || || ||Halt (powers off the system)
|-
|1'''Questions asked during first boot'''|| || || ||Single-user maintenance mode
|-
|3'''Advantages of this type of installation'''|| || || ||Network running, character-mode display only
|-
|5'''Disadvantages of this type of installation'''|| || || ||Network running, graphical user interface
|-
|6'''This type of installation is recommended for...'''|| || || ||Reboot
|}
# Start the ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.# Switch to the f19host machine, and open a shell terminal.# Enter these commands into your f19host machine and note the result:#* <code>'''virsh list'''</etccode>#* <code>'''virsh list --all'''</inittabcode>#* <code>'''virsh list --inactive'''</code> is # Now, shut-down your fedora1 VM normally, and close the configuration file, which sets fedora1 VM window. Make certain NOT to close the default runlevelVirtual Machine Manager main window.* # Switch to your terminal and issue the command: <code>'''virsh start fedora1'''</etc/rccode># Check to see if your fedora1 VM is now running.d/init.d# Switch to the terminal and issue<code>'''virsh list --all'''</code> is 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 directory of scriptsrequest to "shutdown virtual machine gracefully", but may not always work.Why do you think it is useful to have commands to manipulate VMs?
'''Answer the Investigation 5 observations / questions in your lab log book.'''
# To check 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 network configuration settings obtained from command!'''){{Admon/caution| Make sure the DHCP serverbackup is successful!|If there are any error messages, run '''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 following commandsbackup, you will not have a working virtual machine, describing and will have to re-install it.}}<ol> <li value="4">Compare the size of the compressed and original files.</li> <li>Start the output '''''fedora3''''' VM.</li> <li>'''Make certain that you are in your log bookfedora VM and <u>not</u> in your Fedora main system!'''</li> <li>Wreck <u>only</u> your fedora 3 system! Try this command inside the fedora3 virtual machine:#<code>'''rm -rf /* ifconfig'''</code></li>#* route <li>Shut down the VM. If you tried to start the Fedora3 VM, it would not boot since all system files have been removed!</li>#* netstat -rn <li>Restore the original image from the backup in your home directory by typing this command: <code>'''gunzip < ~YourUserId/fedora3.img.backup.gz > fedora3.img'''</code></li>#* nslookup (at <li>Restart the VM. Is it working normally?</li> <li>Create compressed backups of your other virtual machines.</li></ol><ol> prompt, enter <li value="12">You should make a copy of the word xml configuration file in case you "serverwipe" (do not type and re-install the quotes) host machine, and record want to add a restored VM backups to the outputvirtual machine manager list. Type exit We will demonstrate using the fedora 3 xml configuration file, and prove that a "clone" can be added to leave nslookup)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># Find <li>Execute the following information 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> <li>Edit the output of file <code>fedora3a.xml</code>, making the above commandsfollowing changes:</li>#</ol>::* MAC address Change the name (physical or hardware addressin the file, not the file name) to <code>fedora3a</code>::* Change at least one of the hexadecimal characters in the UUID. Do not change the length of the ethernet network interfaceUUID. Valid hexadecimal characters are 0-9 and a-f.#* The IP address <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 (logical addresseg. USB key) assigned by in case the DHCP serverhost machine gets "wiped" and you need to rebuild your HOST machine and then restore your Virtual Machines...</li>#* The default route (gateway)<li>Answer this question in your log book:</li></ol>#::* The DNS nameserverIn order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?
{{Admon/importanttip|Do not lose the GRUB passwordSSHD and Firewall|If you lose have restarted your virtual machine ''fedora1'', the GRUB password sshd server you started in investigation 1 (step 15) will not no longer be able running. In addition, the firewall will have reverted to change boot parameters when its original state. In order to use '''scp''', below, you boot will need to restart ssh and adjust the systemfirewall again. <br /><br />If you need to write it downstudents cannot backup their kickstart files using the '''scp''' command, put it in they can use a safe placeweb-browser to access their Seneca e-mail with attachment (copy kickstart file to their home directory first!). For the text-based Linux system "fedora3", where no one will be able students can use the '''mail''' command (refer to the man command to learn how to tell what it is forsend e-mail attachments).}}
'''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:'''
# How many packages were installedWhat is the name of the Fedora installation program?# How many files Which factors recorded in your table (correct above) were due to the nearest hundred) type of installation performed, and which factors were due to the amount of software installed?# How many mount points were usedWhich type of installation works best for confirming compatibility with hardware before installation? Why?# How many users were created automatically on your system (do not count your learn account)Which type of installation works best for installing large numbers of computers? Why?# What is your learn account's UID and GIDfactors affect installation time?# How can you reduce the number of software updates required immediately after installation?# What is your learn account's home directoryWhy would you enable additional repositories during installation?# What is does the home directory for the user "file <code>/root"/anaconda-ks.cfg</code> contain, and how is it created?# How do you determine the host name of start and stop virtual machines?# How do you SSH into your GNU/Linux workstationvirtual machines?# What command can display is the NIC's MAC addresspurpose of and relationship between these pieces of software?# Which * libvirt#* libvirtd#* virsh#* virt-manager#* virt-install#* kvm# The kickstart installation (fedora3) was a network installation. Can a kickstart file contains the default "runlevel" value for your GNU/Linux workstationbe used with a DVD installation?# The kickstart installation (fedora3) was fairly fast. Why? Under what circumstances would it take a long time, even on a fast network?# What other types of installation sources are possible (besides Live Disc, Installation Disc, and Network?)
