Changes

[[Category:OPS235]][[Category:OPS235 Labs]]

== 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).

|

! Install. Source

|-

! ✓

! ✓

! ✓

! ✓

! PXE Network Boot

! ✓

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

* 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"

|

|

|

|

|}

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

<ol>

</ol>

<ol>

</ol>

==== 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

* '''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:

<!-- {{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 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).

}}

|}

<ol>

</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>

<ol>

</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>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

* '''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)'''.

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

# 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

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

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

|-

|-

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

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

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

# To prevent confusion, copy your kickstart files to kickstart filenames that describe their purpose (eg. kickstart_host, kickstart_fedora1, kickstart_fedora2, etc...)

# How could you use the kickstart file produced by the installation program to perform additional, identical installations?