Changes

{{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 2: Fedora 16 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3)=

! Network (http, /nfs repository)

==Required Materials (Bring to All Labs)==

* '''Fedora 16 17 LIVE CD''' * '''Fedora 16 x_64 17 x86_64 Installation DVD'''* '''SATA Hard Disk''' (in removable disk tray)* '''USB Memory Stick''' (minimum 64M)* '''Lab Logbook (Lab2 Reference Sheet)''' (to make notes and observations).

<span style="background-color:yellow;font-weight:bold'">[http://docs.fedoraproject.org/virtualization-guide/f13/en-US/html/ Fedora Virtualization Guide]</span>

* [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Fedora_Live_Images/ Fedora 16 17 Live Image Guide]* [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Quick_Start_Guide/ Fedora 16 17 Installation Quick Start Guide]

[http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ Fedora 16 17 Installation Guide]* [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86/ Preparing for a Network Installation]* [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86 Performing a Network Installation]

[http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ Fedora 16 17 Installation Guide]* [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/sn-automating-installation.html Automating the Installation with Kickstart]* [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ch-kickstart2.html Kickstart Installations]* [http://docs.fedoraproject.org/en-US/Fedora/1617/html/Installation_Guide/ch-redhat-config-kickstart.html Kickstart Configurator]

# <ol> <li value="3">Start the virtualization service: <code>service libvirtd start</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>service iptables restart</code></li></ol>

{{Admon/caution|Reboot your fedora hostnow|There appears to be an issue with supplying your VM's with a dynamic IP virt-manager may not work properly unless the host is restarted you reboot after installing "Virtualization". '''Reboot now to avoid this problemthe virtualization software.'''}}

<li value="45">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>

{{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 download install directly from the .iso image ISO file from http://belmont.senecac.on.ca/fedora/releases/16/you used to burn your Live/x86_64/Fedora-16-x86_64-Live.iso and install directoly from that fileCD. There are many Internet tutorials that show the individual how to perform that task.}}

# '''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 it '''Use CDROM or DVD''' as the install media. Set the ''OS type'' to '''Linux''' and the ''Version'' to '''Fedora 1617''' (refer to ''Step 2 of 5'' thumbnail above).

{{Admon/note|Fedora LIVE CD Install Screen Shots Thumbnails|While performing the Fedora 16 17 LIVE CD install, click on the thumbnails below to provide a '''"visual reference"''' while performing this particular Fedora installation.

<li value="8">'''The virtual machine will now start'''. You will see a window which displays Select the virtual video card from the VM. Itdefault menu item labelled: '''Start Fedora 17'''s important to note that the VM can (and often will) run even when this display is not present. 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> <livalue="9">Login to the VM and double-click: '''Applications'''>'''System Tools'''>'''Install to Hard DiskDrive'''. 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> <livalue="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 logout '''reboot''' button at the top bottom right-hand corner of the screen and select '''Power Off'''.</li></ol> <ol> <livalue="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>

{{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'''.|

<li value="1415">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>

* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/1617/Fedora/x86_64/os/* '''Memory:''' 768MB1024MB* '''Disk space:''' 15GB20GB

# Create the VM (called '''fedora2''') as you did with the ''fedora1'' virtual machine, except:

#* In '''step 2 of 5''', provide the location of the software source by providing the URL http://belmont.senecac.on.ca/fedora/releases/1617/Fedora/x86_64/os/#* In '''step 2 of 5''', set the ''OS Type'' to '''Linux''' and ''Version'' to '''Fedora 1617'''.

# 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:

# '''On the same screen, select the "Fedora 16 17 - x86_64" and the "Fedora 16 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'''. '''Answer the Investigation 2 observations / questions in your lab log book.'''

* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/1617/Fedora/x86_64/os/* '''Kickstart location:''' http://zenitwww.senecacdrivehq.oncom/file/df.caaspx/~chris.tylershareID10606286/fileID1269952040/fedora16-vdaFedora17-kskickstart.cfg* '''Memory:''' 512MB1024MB* '''Disk space:''' 10GB15GB

#* In step 2 of 5, after entering the URL for the installation source, click on the '''URL Options''' control.#* Enter the Kickstart URL: http://zenitwww.senecacdrivehq.oncom/file/df.caaspx/~chris.tylershareID10606286/fileID1269952040/fedora16-vdaFedora17-kskickstart.cfg

# '''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.'''

{|border="1" width="100%" cellpadding="5"

! ||f16hostf17host||fedora1||fedora2||fedora3

# Switch to the f19host machine, and open a shell terminal.# Enter these commands into your f19host machine and note the result:#* <code>'''virsh list'''</code>#* <code>'''virsh list --all'''</code>#* <code>'''virsh list --inactive'''</code># Start Now, shut-down your fedora1 VM normally, and close the fedora1 VM window. Make certain NOT to close the ''fedora3'' virtual machine from Virtual Machine Manager main window.# Switch to your terminal and issue the command line: <code>'''virsh start fedora3fedora1'''</code># Repeat the commands from step 2 and notice any changesCheck to see if your fedora1 VM is now running.# Stop Switch to the terminal and issue<code>''fedora3'' virtual machine: <code>virsh shutdown fedora3</code># Confirm that 'list --all'fedora3'' has been shut down.# Execute this command: </code>virsh dumpxml fedora3 >fedora3and confirm the status of the fedora1 VM.xml</code># Examine the file <code>fedora3There are other commands that can be used (such as suspend, or shutdown).xml</code>The "shutdown" command may not always work since it sends a request to "shutdown virtual machine gracefully", but may not always work. What does Why do you think it contain? What format is it inuseful to have commands to manipulate VMs?# Edit the file fedora3.xml, making the following changes:#* Change {{Admon/note|Virtual Machine Does not Shutdown from Command|If the name Virtual machine fails to shutdown from the <code>fedora3avirsh shutdown</code>#* Change at least one of command, then you can go to the '''Virtual Machine manager''' and '''halt''' or '''shutdown''' within the VM itself, then you can click the hexadecimal characters '''PowerOff''' button in the UUIDVM window. Do not change You'll want to avoid a forced shutdown since those are equivalent to yanking the length cord out of the UUID. Valid hexadecimal characters are 0-9 and wall on a-f.physical machine!|}}# Issue this command: <code>virsh define fedora3a.xml</code># Issue the command <code>virsh list --all</code> and record any changes.# Issue '''Answer the command: <code>virsh undefine fedora3a<Investigation 5 observations /code># List all of the virtual machines again, and note any changesquestions in your lab log book.'''

{{Admon/important|Backing up VMs|There are two general processes in order to back up your images:<ol><li>'''Compressing your images''' (also recommended to backup up to external storage USB Key) using the '''gzip''' command.</li><li>'''Backup the VM xlm configuration file''' (preferably to USB key) using '''virsh''' shell command to add VM to virtual machine manager list (in the event that the HOST machine is "wiped" and re-installed, but VM images and xml configuration files have been backed up external storage).</li></ol><br />Taking the time to backup the image of the Operating System's file system allows the user to return to a '''"restoration point"''' using the '''gunzip''' command in case something bad occurs to the OS during a lab. <br />Failure to take the time to make and confirm backups can result in loss of lab work for the student!|}}

# 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.}}

<li>Start the '''''fedora3''''' VM.</li> <li>'''Make certain that you are in your fedora 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 ('''DO NOT''' do this on your main Fedora system, or you will have to repeat your '''lab2''' and portions of your '''lab3'''!): <code>'''rm -rf /*'''</code></li> <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> <li>Restore the original image from the backup (type in your home directory by typing this command carefully): <code>'''gunzip <~YourUserId/fedora3.img.backup.gz >fedora3.img'''</code></li>

</ol><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> <li>Edit the file <code>fedora3a.xml</code>, making the following changes:</li></ol>::* Change the name (in 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 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><li>Answer this question in your log book:</li>

{{Admon/tip|SSHD and Firewall|If you have restarted your virtual machine ''fedora1'', the sshd server you started in section investigation 1-16 (step 15) will no longer be running. In addition, the firewall will have reverted to its original state. In order to use '''scp''', below, you will need to restart ssh and adjust the firewall again.<br /><br />If students cannot backup their kickstart files using the '''scp''' command, they can use a web-browser to access their Seneca e-mail with attachment (copy kickstart file to their home directory first!). For the text-based Linux system "fedora3", students can use the '''mail''' command (refer to the man command to learn how to send e-mail attachments).}}

# Obtain the kickstart files for all four of your installations (your disk pack ''f16hostf17host'', 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 f16host f17host system (tip: use <code>scp</code>), or use the hint in the tip box above to send via e-mail.

{{Admon/important | Important! | '''Arrange evidence of for each of the following these items on the your screen, and then ask your professor or lab monitor instructor to check review themand sign off on the lab's completion:}}'''

= Preparing for the Quizzes =