Changes

<li>As you proceed throughout this lab, you will be required to fill in the comparison chart for the remaining 3 virtual machines that you will be installing.</li>

</ol>

=== Part 2: Installing from a Downloaded Image (Centos7 LIVE CD) ===

<li>Find out the IP address of your virtual machine and the name of your Ethernet network adaptor: <b><code><span style="color:#3366CC;font-size:1.2em;">ifconfig</span></code></b> </li>

<li>Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine:<br /> <b><code><span style="color:#3366CC;font-size:1.2em;">iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT</span></code></b></li><li>If you are logged in as root, logout to your regular user account.</li><li>Confirm that you can ssh to your virtual machine from the host (your main CentOS installation): <b><code><span style="color:#3366CC;font-size:1.2em;">ssh regularuserid@IPaddress</span></code></b> (where '''regularuserid''' is your regular user login id, and '''IPaddress''' is the '''IP_ADDRESS''' of your '''centos1''' VM!).</li><li>Make certain to '''disable SELinux for centos1''' (refer to lab1)</li><li>Adjust your screen-saver settings and run a '''yum update''' on your centos1 VM before proceeding to ''Part 2''</li></ol>

=== Part 3: Installing from a Network ===

# Repeat the steps as you did to '''start the SSH service''', '''set iptables to accept connections via ssh''', '''test connections between centos2 and centos1''', and '''disable SELinux''' (refer to lab1).

# Record the time taken to install, and compare this to the time taken by the previous installations. Record your findings in the Installation Comparison chart in lab2 logbook.

=== Part 4: Installing from a Network using a Kickstart File ===

=== Part 2: Managing Virtual Machines from the Command Line ===

{| width="40%" align="right" cellpadding="10"

|- valign="top"

{{Admon/important|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 power cord out of the wall on a physical machine!|}}

<ol><li value="4">Now, shut-down your centos1 VM normally, and close the centos1 VM window.</li><li>Switch to your terminal and issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">virsh start centos1</span></code></b></li><li>Using the appropriate command check to see if your centos1 VM is now running.</li><li>There are other commands that can be used (such as '''suspend''', or '''shutdown'''). The "shutdown" command may not always work since it relies on the guest handling a particular ACPI event. Why do you think it is useful to have commands to manipulate VMs?</li><li>Since this is a text-based version of Linux, you do not need to turn off the screen-saver.</li></ol>

=== Part 3: Backing Up Virtual Machines ===

::* In order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?

<ol><li value="24">A previous OPS235 student graciously created a shell script that you can download and run to check to see how you performed this lab (to see if you are on the right track).<br>Simply issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">wget http://matrix.senecac.on.ca/~murray.saul/ops235/lab2check2.bash</span></code></b> and run on your '''c7host machine'''.<br><br>'''If the shell script indicates any major errors, please inform your OPS235 instructor or lab assistant to advise what to do'''.<br><br></li></ol>

===Part 4: Automating Routine Tasks (Shell Scripting)===

</code>