Changes

Jump to: navigation, search

OPS245 Lab 2

1,030 bytes added, 9 March
no edit summary
{{Admon/caution|DO NOT USE THIS VERSION OF THE COURSE. This page will no longer be updated.|'''Debian version here:''' https://seneca-ictoer.github.io/OPS245
<br>'''CentOS version here:''' https://seneca-ictoer.github.io/OPS245-C7<br>'''Andrew's version here:''' http://wiki.littlesvr.ca/wiki/OPS245_Lab_2}}
= LAB PREPARATION =
[[Image:vmware-1a.png|thumb|right|400px|At the end of lab2, your VMware Workstation application will contain '''4 virtual machines''' ('''c7host''' in your '''VMware Workstation''' application, and '''centos1, centos2, centos3 VMs''' in your '''KVM''' application). You will now have the option to run one virtual machine at a time, or run all machines simultaneously to learn about networking (covered in later labs) ]]
{{Admon/important|Run virt-manager as a regular user, not as root|Otherwise all your virtual machines will be owned by root and you won't be able to use them as a regular user.}}
<ol>
<li value="8">Start the graphical tool by selecting the menu options '''Applications'''>'''System Tools'''>'''Virtual Machine Manager''' or by typing the command<b><code><span style="color:#3366CC;font-size:1.2em;"> virt-manager</span></code></b>(without sudo!)</li>
<li>You will be learning in the next investigation to perform several different types of CentOS Linux installs.</li>
</ol>
 
===Part 2: Configure VMware Workstation for Nested VMs ===
# In a terminal use elavated privileges to edit the file called: '''/boot/efi/EFI/centos/grub.cfg'''<ul><li>'''If this file doesn't exist, double-check your UEFI settings in VMWare Workstation for c7host. If BIOS is selected, <u>you MUST redo Lab 1</u>.'''</li></ul>
# Search for the <b>first occurrence</b> of the Linux Kernel boot command. Do not make the following changes on more than one entry!
# Insert the boot option: '''kvm-intel.nested=1''' (for AMD processors '''kvm-amd.nested=1''') at the end of the Linux kernel boot options.
<ol>
<ol><li value="4">Save your editing changes, close the virtual machine application, and <u>'''reboot'''</u> your c7host VM.</li>
<li>If you configured your c7host VM for nested VMs, then you should get the output <b><code><span style="color:#3366CC;font-size:1.2em;">Y</span></code></b> when you issue the following command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">cat /sys/module/kvm_intel/parameters/nested</span></code></b></li><ul><li>For '''AMD''' processors, check the /sys/module/'''kvm_amd'''/parameters/nested file.You should get the output <b><code><span style="color:#3366CC;font-size:1.2em;">1</span></code></b></li></ul>
<ul><li>And if kvm_intel directory doesn't exist, double-check your '''Processors => Virtualization Engine (Intel VT-x/EPT...)''' settings in VMWare Workstation.</li></ul>
</ol>
:: '''Boot media:''' Network installation
:: '''CentOS Full Network Install URL:'''
:::*Seneca Lab: httpshttp://mirror.senecacollege.ca/centos/7/os/x86_64/('''NOTE: requires VPN'''):::*Home: httpshttp://mirror.netflash.net/centos/7/os/x86_64/
:: '''VM Image Pathname:''' /var/lib/libvirt/images/centos1.qcow2
:: '''Memory:''' 2048MB
# Select the '''Network Install''' option and click '''Forward'''.
# Enter (copy and paste) the URL located at the top of this section (depending whether you are at Seneca College or not) and click '''Forward'''.
# Set RAM size to 2048 MB and CPUs to 2, then click '''Forward'''.
# Set Hard Disk size to 15GB and click '''Forward'''.
# <span style="background-color:yellow;">Enter the name: '''centos1''', <u>AND</u> then select the option: '''Customize configuration before install''', and click '''Finish'''.</span>
# <span style="background-color:yellow;">Another dialog will appear. Click '''CPUs''' (or "processors") and on right-side under Configuration select '''Copy Host CPU Configuration''', click '''Apply''', and then click '''Begin Installation''' at the top left-hand side.</span>
#<span style="background-color:yellow;">During the install, select '''Gnome Desktop''' (software selection). For partitioning, select '''I will configure partition settingspartitions'''settings, click done, then select '''Click here to create them automatically'''. Set the / partition for '''ext4''' file-system type, and click '''Done'''.</span>#<span style="background-color:yellow;">Set the correct '''Date and Time Zone''', and then click on '''Network and Hostname'''. The network should be turned on'''ON'''. For hostname, enter: '''centos1''' and then click '''Done'''.</span>
# <span style="background-color:yellow;">Make sure that when you create your regular user account you check the box to make them an administrator.</span>
# <span style="background-color:yellow;">Complete the installation. Login to your regular user account, and perform a '''sudo yum update''' for the centos1 VM (reboot if required). Make certain to adjust your screen-saver settings if desired.</span>
{{Admon/important|Use same root password / regular username / regular user passwords for c7host and ALL VMs|To simplify the lab checking process make certain that you use the identical root password, regular username, and regular username password for VMs that you create in this labs as you did for c7host machine in lab1.<br><br>}}
<br>
<ol><li value="1314"><span style="background-color:yellow;">Repeat the steps as you did in the previous investigation ([https://wiki.cdot.senecacollege.ca/wiki/OPS235_Lab_2OPS245_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop , disable and disable remove firewalld, install iptables-services, start and enable iptables''' for this newly-created VM.</span></li><li><span style="background-color:yellow;">Repeat the steps as you did with c7host post-install to '''turn off (permissive) SELinux''' and perform a '''yum update'''.</span></li>
<li>Issue the following command to obtain the IPADDR for your centos1 VM to record in your lab2 logbook: <b><code><span style="color:#3366CC;font-size:1.2em;">ip address show</span></code></b></li>
<li>Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook.</li>
:: '''Boot media:''' Network installation
:: '''CentOS Full Network Install URL:'''
:::*Seneca Lab: httpshttp://mirror.senecacollege.ca/centos/7/os/x86_64/('''NOTE: requires VPN'''):::*Home: httpshttp://mirror.netflash.net/centos/7/os/x86_64/
:: '''VM Image Pathname:''' /var/lib/libvirt/images/centos2.qcow2
:: '''Memory:''' 2048MB
# Make certain to enter the name: '''centos2''', <u>AND</u> then select the option: '''Customize configuration before install''', and select '''Copy Host CPU Configuration''', click '''Apply''', and then click '''Begin Installation'''.
#When selecting the install options for centos2, do the same operation that you did in centos1 (but with '''Minimal Install''' software selection instead), but after '''automatically creating the partitions''', reduce the size of the root logical volume to '''8 GiB''' and add a logical volume with a size of '''2 GiB''' (mount point: '''/home''', name: '''home''', and make certain root and /home logical volumes have '''ext4''' file system).<br><br>
 
# <span style="background-color:yellow;">Complete the installation. Login to your regular user account.</span>
#<span style="background-color:yellow;">Repeat the steps as you did in the previous investigation ([https://wiki.cdot.senecacollege.ca/wiki/OPS235_Lab_2OPS245_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop and disable firewalld, install iptables-services, start and enable iptables''' for this newly-created VM.</span># <span style="background-color:yellow;">Repeat the steps as you did with c7host post-install to '''turn off (permissive) SELinux''' (using the command 'vi' instead of 'vim') and perform a '''yum update'''.</span>
# Issue the following command to obtain and record your centos2 IPADDR in your lab2 logbook: <b><code><span style="color:#3366CC;font-size:1.2em;">ip address show</span></code></b>
# Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook.
=== Part 3: Installing from a Network using a Kickstart File ===
{| width="40%" align="right" cellpadding="10"
|- valign="top"
|colspan="2"|{{Admon/important|Using a Kickstart file with a local install|Under most circumstances, a network install would be drawing the installation data from a server in the local network, allowing it to transmit data at higher speeds than we can achieve over the internet. If your download speed is slow enough that network installs are failing, it is acceptable to install these VMs from local media. However, you will still need to provide a kickstart file to Centos3. <br /><br />To do so, start the install process as normal for an installation from an iso file, but when presented with the menu giving you the option to 'Install CentOS 7' or 'Test this media &amp; install CentOS 7', highlight 'Install CentOS7' and press '''&lt;tab&gt;'''. This will open a prompt at the bottom of the window for you to enter grub configuration options. Type '''inst.ks&#61;https://raw.githubusercontent.com/OPS245/labs/main/centos7-kickstart.cfg''' and hit '''&lt;enter&gt;'''.}}
|}
 
:'''VM Details:'''
:::*Home: http://mirror.netflash.net/centos/7/os/x86_64/
:: '''Kickstart File URL (Kernel options): '''
:::* Home:''' <span style="color:green;font-weight:bold">ks=</span>https://ictraw.senecacollegegithubusercontent.cacom/~peter.callaghanOPS245/ops245labs/labsmain/centos7-kickstart.cfg
:: '''VM Image Pathname:''' /var/lib/libvirt/images/centos3.qcow2
:: '''Memory:''' 2048MB ('''IMPORTANT''' Do not use less than 2048MB during installation.)
# Create the VM (called '''centos3''')
# During the install, copy the network URL, then click the '''URL options''' to expand the '''kernel options''' input textbox. Type the following in the kernel options textbox: <ul><li><span style="color:green;font-weight:bold">ks=</span>https://ictraw.senecacollegegithubusercontent.cacom/~peter.callaghanOPS245/ops245labs/labsmain/centos7-kickstart.cfg</li></ul>
# Then click the '''forward''' button to proceed. Make certain to select the correct Memory Size and Disk Space size shown in the VM Details above
# Make certain to enter the name: '''centos3''', <u>AND</u> then select the option: '''Customize configuration before install''', and select '''Copy Host CPU Configuration''', click '''Apply''', and then click '''Begin Installation'''.
# Boot the virtual machine and log in (use the user ID and password information from the previous step to gain access to this VM).
# Compare the experience to the first time you booted the other virtual machines.
# <span style="background-color:yellow;">Repeat the steps as you did in the previous investigation ([https://wiki.cdot.senecacollege.ca/wiki/OPS235_Lab_2OPS245_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop and disable firewalld, install iptables-services, start and enable iptables''' for this newly-created VM.</span>
# <span style="background-color:yellow;">Repeat the steps as you did with c7host post-install to '''turn off SELinux''' and perform a '''yum update'''.</span><br />
:::You'll notice something when you go to set '''SElinux''' to '''permissive'''. The kickstart file already did that for you. It could even have performed the switch from firewalld to iptables for you (but it didn't).
:'''Perform the following steps:'''
# Shut down your '''centos1''', '''centos2''', and '''centos3''' VMs. For ''centos2'' and ''centos3'', which are CLI-only, you can issue the following command to shutdown: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo shutdown -hpoweroff</span></code></b>. Please be patient, the VMs will shut down!
# In your '''c7host''' VM, open a new Terminal window.
# Use elevated privileges ist to list the size and names of files in<b><code><span style="color:#3366CC;font-size:1.2em;">/var/lib/libvirt/images/</span></code></b><ul><li>What do these files contain?</li></ul># Use the command <b><code><span style="color:#3366CC;font-size:1.2em;">sudo -i</span></code></b> and enter your password if prompted. You are now root until you use the command <b><code><span style="color:#3366CC;font-size:1.2em;">'''exit</span></code></b> ''' to return to your normal user account.
# Change to the images directory by issuing the following command: <b><code><span style="color:#3366CC;font-size:1.2em;"> cd /var/lib/libvirt/images/</span></code></b>. Note that you did not need to use sudo, as you are already using elevated permissions.
# Make a compressed backup of your '''centos1.qcow2''', '''centos2.qcow2''', and '''centos3.qcow2''' files to your regular user's home directory by issuing each command (- one at a time(create '''backups''' directory '''within your regular user's home directory''' before running these commands):<br><b><code><span style="color:#3366CC;font-size:1.2em;">gzip < centos1.qcow2 > ~YourRegularUsername/backups/centos1.qcow2.gz</span></code></b><br><b><code><span style="color:#3366CC;font-size:1.2em;">gzip < centos2.qcow2 > ~YourRegularUsername/backups/centos2.qcow2.gz</span></code></b><br><b><code><span style="color:#3366CC;font-size:1.2em;">gzip < centos3.qcow2 > ~YourRegularUsername/backups/centos3.qcow2.gz</span></code></b><ul>'''NOTE:''' Make certain to use the redirection signs "<" and ">" properly in the command!</ul>
{{Admon/important |Please be patient|It may look like the command prompt is stuck but it could take a while for gzip to compress an entire operating system. '''NOTE:''' Do NOT press '''&lt;ctrl&gt;c''' to cancel this process. If you do, your archive will become incomplete and your recovery will be corrupt.}}
<ol><li value="57"> Compare the size of the compressed and original files (hint: use '''ls -lh'''). If file is very large (like 15GB), you didn't compress it and you need to remove that file and perform the previous step until you get it right!</li><li>Once you are '''sure you have all three VMs backed up''', use the <b><code><span style="color:#3366CC;font-size:1.2em;">exit</span></code></b> command to revert back to your normal user.</li>
<li> Start the '''''centos3''''' VM.</li>
<li> '''Make certain that you are in your VM and <u>not</u> in your main system!''' </li>
<li> Wreck <u>only</u> your centos3 system! Try this command inside the centos3 virtual machine:<b><code><span style="color:#3366CC;font-size:1.2em;">sudo rm -rf /*</span></code></b> (ignore error messages).</li>
<li> Shut down and restart the centos3 VM(you may need to use the '''Force Reset''' option to do so). It </lI><li> When the machine restarts it will not boot since all system files have been removed!</li><li> Use the '''Force Off''' option to turn centos3 back off.</li><li> Restore the original image from the backup from your home directory to your '''images''' directory by typing <b><code><span style="color:#3366CC;font-size:1.2em;">sudo -i</span></code></b> command first [do not forget to '''exit''' when you are done], then this command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">sudo gunzip < ~YourUserIdYourRegularUsername/backups/centos3.qcow2.gz > /var/lib/libvirt/images/centos3.qcow2'''</span></code></b></li>
<li> Restart the VM. Is it working normally?</li>
<li> You should also make a copy of the XML configuration file for each VM 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 centos3 XML configuration file, and prove that a "clone" can be added to your list.Please perform the following step:</li>
<li> Execute the following command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo virsh dumpxml centos3 > centos3.xml</span></code></b></li>
<li> Examine the file <b><code><span style="color:#3366CC;font-size:1.2em;">centos3.xml</span></code></b>. What does it contain? What format is it in?<br></li></ol>
# We will now learn how to download a compressed image file and XML configuration file and add it as a VM to the Virtual Machine Manager menu.
# Issue the following commands:<ul><li><b><code><span style="color:#3366CC;font-size:1.2em;">wget https://ictmatrix.senecacollege.ca/~ops235ops245/centos4.qcow2.backup.gz</span></code></b></li><li><b><code><span style="color:#3366CC;font-size:1.2em;">wget https://ictmatrix.senecacollege.ca/~ops235/labsops245/centos4.xml</span></code></b></li></ul>
# Use gunzip with elevated privileges to decompress the qcow2 image file into the '''/var/lib/libvirt/images''' directory.
# Issue the command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo virsh define centos4.xml</span></code></b># What happened in the virtual manager window? To In order to remove a VM entry in the Virtual Manager window, simply issue the command: '''virsh undefine vm_nameVM_name''' (without the '''.xml''' file extension)
# Start up your new centos4 VM.
# Click on the user <i>OPS235OPS245</i>, and click the cog icon.
# Notice <i>Cinnamon (Software Rendering)</i> is selected. The Cinnamon desktop environment has been installed on this VM. From this menu, you can select other installed desktop environments. This is how you switch between them. Write it down.
# Login with the password <b><i>ops235ops245</i></b>. Feel free to explore the new environment.
# Prior to your practical test, you will be required to perform a similar operation to download, unzip and run a VM image for your practical test.<br>
{{Admon/important|Shutting Down the Host while Virtual Machines are Running|If you shut down your host system while virtual machines are running, they will be suspended, and will resume the next time you boot your host system. Note that it is better to shut down the VMs prior to shutting down the host}}<ol><li value="12">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>
::* In order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?
=== Part 3: Using Shell Scripts the Command Line for VM Backup &amp; State Management===
{|width="40%" align="right" cellpadding="10"
|- valign="top"
|
{{Admon/tip|Bash Shell Scripting Tips:|<br>'''<u>Data Input</u>'''<br><ul><li>A shell script can obtain data from a number of methods: '''reading input files''', using '''arguments when issuing command''' (positional parameters), or '''prompting for data to store in a variable'''. The later method can be accomplished by using the '''read''' command.<br><br></li><li>Example:<br><br>''read -p "Enter your name: " userName''.<br><br></li></ul>'''<u>Mathematical Expressions</u>'''<br><ul><li>In the bash shell scripting, data is stored in variable as text, not other data types (ints, floats, chars, etc) like in compiled programs like C or Java. In order to have a shell script perform '''mathematical operations''', number or variable need to be surrounded by two sets of parenthesis '''((..))''' in order to convert a number stored as text to a binary number.<br><br></li><li>Examples<br><br>''var1&#61;5;var2&#61;10''<br>''echo "$var1 + $var2 &#61; $((var1+var2))"''<br><br>'''Note:''' shell does not perform floating point calculations (like '''5/10'''). Instead, other commands like '''awk''' or '''bc''' would be required for floating point calculations (decimals)<br><br></li></ul><u>'''Loops (for / while / until)'''</u><ul><li>Determinant loops (such as '''for''' loops) usually repeat for a preset number of times (eg. counts, positional parameters stored). In-determinant loops (such as '''while''' or '''until''' loops) may repeat based on unknown conditions (like waiting for user to enter correct data).<br><br></li><li>Conditional statements '''&amp;&amp;''' (run if previous command or test is true) and '''&#124;&#124;''' (run is previous command or test is false) can also be used when testing multiple conditions.<br><br></li><li>Examples:<br>''set ops235 is fun''<br>''for x''<br>''do''<br>&nbsp;''echo "argument is $x"''<br>''done''<br><br>''for x in $(ls)''<br>''do''<br> &nbsp;''echo "Filename: $x"''<br>''done''<br><br>''read -p "enter a whole number: " num''<br>''until echo $num &#124; grep -q "^[0-9][0-9]*$"''<br>''do''<br> &nbsp;''read -p "Incorrect. Please enter WHOLE NUMBER: " num''<br>''done''<br><br>''read -p "pick a number between 1 and 10: " num''<br>''while [ $num -lt 1 ] &#124;&#124; [ $num -gt 10 ]<br>''do''<br> &nbsp;''read -p "Incorrect. Please pick number between 1 and 10: " num''<br>''done''<br><br></li></ul>}}
|}
You will continue our use of the Bash Shell scripting by first creating a Bash Shell script that examining commands will allow the Linux sysadmin to select gather information about and manage their created VMs for backup to root's home directory. Afterwards you will download, view and run a couple Bash Shell scripts that use the virsh command to start and stop your virtual machinesVirtual Machines.
:'''Perform the following steps:'''
# Switch to the '''c7host''' machine, and open a shell terminal.
# Enter these admin commands into your '''c7host''' machine and note the result:
:: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo virsh list</span></code></b>:: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo virsh list --all</span></code></b>:: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo virsh list --inactive</span></code></b><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;">sudo 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></ol>
{{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="9">Open a Bash shell terminal.</li><li>Use elevated privileges to create a directory called /root/bin.</li><li>Use a text editor (such as <b><code><span style="color:#3366CC;font-size:1.2em;">vi</span></code></b> or <b><code><span style="color:#3366CC;font-size:1.2em;">nano</span></code></b>) to create a Bash Shell script called: <b><code><span style="color:#3366CC;font-size:1.2em;">backupVM.bash</span></code></b> in /root/bin directory.</li><li>Enter the following text content into your text-editing session:</li></ol><code style="color:#3366CC;font-family:courier;font-size:.9em;"><br>&#35;!/bin/bash  &#35; backupVM.bash<br>&#35; Purpose: Backs up pre-defined virtual machines<br>&#35;<br>&#35; USAGE: ./backupVM.bash<br>&#35;<br>&#35; Author: *** INSERT YOUR NAME ***<br>&#35; Date: *** CURRENT DATE ***  if [ $PWD != "/root" ] # only runs if in root's directory<br>then<br>&nbsp;echo "You must be located in /root" >&2<br>&nbsp;exit 1<br>fi</code><br><ol><li value="12">Save your editing session, but remain in the text editor.</li><li>This shell script is designed particularly for your centos1, centos2, and centos3 VMS.</li><li>The code displayed below will prompt the user if they wish for all VMs to be backed-up; otherwise, allow the user the option of specifying which VMs to be backed-up. Add the following code</li></ol><br><code style="color:#3366CC;font-family:courier;font-size:.9em;"> read -p "Backup all VMs? (y|n):" answer # prompt if all VMs to be backed-up if [ "$answer" = "y" ] # Backup all VMs if answer is yes<br>then<br>&nbsp;for num in 1 2 3 # Determinant loop for 3 arguments: 1, 2, and 3<br>&nbsp;do<br>&nbsp;&nbsp;echo "Backing up VM #$num"<br>&nbsp;&nbsp;gzip < /var/lib/libvirt/images/centos$num.qcow2 > ~yourusername/backups/centos$num.qcow2.gz<br><br>&nbsp;&nbsp;echo "VM #$num BACKUP DONE"<br>&nbsp;done<br><br>elif [ "$answer" = "n" ]<br>then<br>&nbsp;read -p "Which VM should be backed up? (1/2/3): " numanswer<br>&nbsp;until echo $numanswer | grep "^[123]$" >> /dev/null # Look for match of single digit: 1,2, or 3<br>&nbsp;do<br>&nbsp;&nbsp;read -p "Invalid Selection. Select 1, 2, or 3: " numanswer<br>&nbsp;done<br>&nbsp;echo "Backing up VM #$numanswer"<br>&nbsp;gzip < /var/lib/libvirt/images/centos$numanswer.qcow2 > ~yourusername/centos$numanswer.qcow2.gz<br><br>&nbsp;echo "VM #$numanswer BACKUP DONE"<br>else<br>&nbsp;echo "Invalid Selection... Aborting program"<br>&nbsp;exit 2<br>fi </code>  <ol><li value="15">Save, set permissions, and then run that shell script to backup centos1. Since that script will only work if you are in root's home directory, you will need to use the technique you learned earlier to temporarily become root. Confirm that this script did backup this image to root's home directory</li><li>Use the <b><code>wget</code></b> command to download, study, and run the following shell scripts on-line:<blockquote><b><code><span style=" pointer-events:none;cursor:default;color:#3366CC;font-size:1.2em;">https://ict.senecacollege.ca/~ops235/labs/vm-start-text.bash<br>https://ict.senecacollege.ca/~ops235/labs/vm-stop-text.bash</span></code></b><br><b><code><span style=" pointer-events:none;cursor:default;color:#3366CC;font-size:1.2em;">https://ict.senecacollege.ca/~ops235/labs/vm-start.bash<br>https://ict.senecacollege.ca/~ops235/labs/vm-stop.bash</span></code></b></blockquote></li><li>Try to understand what these Bash Shell scripts do.</li><li>You have completed lab2. Proceed to Completing The Lab, and follow the instructions for "lab sign-off".</li></ol> 
'''Answer INVESTIGATION 3 observations / questions in your lab log book.'''
|}
This week you have added some significant capabilities to your python scripting. The ability to run loops and make decisions makes your scripts much more powerful. In this investigation you will write a python script that backs up the centos1, centos2, and centos3 VMs, or lets the user to specify which VMs they want backed up.
<ol>
<li>In your '''bin ''' directory, create the file '''backupVM.py''', and populate with our standard beginning
<code style="color:#3366CC;font-family:courier;font-size:.9em;">
<br>
&#35;!/usr/bin/env python3<br />
&nbsp;&nbsp;exit()<br />
else:<br />
&nbsp;&nbsp;for machine in {print('Backing up centos1','centos2','centos3'}:)<br />&nbsp;&nbsp;os.system('gzip < /var/lib/libvirt/images/centos1.qcow2 > ~YourRegularUsername/backups/centos1.qcow2.gz')<br />&nbsp;&nbsp;print('Backing upcentos2' + machine)<br />&nbsp;&nbsp;os.system('gzip < /var/lib/libvirt/images/centos2.qcow2 > ~YourRegularUsername/backups/centos2.qcow2.gz')<br />&nbsp;&nbsp;print('Backing up centos3')<br />&nbsp;&nbsp;os.system('gzip < /var/lib/libvirt/images/' + machine + 'centos3.qcow2 > ~YourRegularUsername/backups/' + machine + 'centos3.qcow2.gz')<br />
</code>
<li>It should print out root, but with an extra new-line. You may have noticed this in your other python scripts so far: the data we get from os.popen() has an extra new-line on the end. We will need to modify the string(s) it gives us a bit. See the side-bar for hints on how to do so.</li>
<li>Modify the if statement so it is just getting the current username, not the username and a newline. You can do this using several steps and several variables, but it can also be done in a single line.</li>
<li>Now Test your script to make sure it works. If it doesn't, go back and fix it. '''Do not continue until it successfully makes backups of your VMs'''.</li><li>There is a weakness to this script as written. Every time you run it, it will make a backup of all three VMs. But what if you only made a change to one of them? Do we really need to wait through a full backup cycle for two machines that didn't change? As the script is currently written, we do. But we can make it better. We've provided the scripts with some comments below.</li><li><code style="color:#3366CC;font-family:courier;font-size:.9em;">&#35;!/usr/bin/env python3<br />&#35;&nbsp;backupVM.py<br />&#35;&nbsp;Purpose: Backs up virtual machines<br />&#35;<br />&#35;&nbsp;USAGE: ./backupVM.py<br />&#35;<br />&#35;&nbsp;Author: *** INSERT YOUR NAME ***<br />&#35;&nbsp;Date: *** CURRENT DATE ***<br />import os<br /><br />&#35;Make sure script recognizes you as is being run with elevated permissions<br />currentuser = os.popen('whoami').read().strip()<br />if currentuser != 'root ':<br />&nbsp;&nbsp;print(or at least running the "You must be root")<br />&nbsp;&nbsp;exit()<br />else<br /><br />&#35;The rest of this script identifies steps with root permissions)comments 'Step <something>'.<br />&#35;This is not a normal standard for commenting, it should workhas been done here to link the script<br />&#35; to the instructions on the wiki. <br /><br />&#35;Step A: Notice how we've used Find out if user wants to back up all VMs<br />&#35;Step B-1:use the + existing loop to combine several strings together back up all the VMs<br />&nbsp;&nbsp;print('Backing up centos1')<br />&nbsp;&nbsp;os.system('gzip < /var/lib/libvirt/images/centos1.qcow2 > ~YourRegularUsername/backups/centos1.qcow2.gz')<br />&nbsp;&nbsp;print('Backing up centos2')<br />&nbsp;&nbsp;os.system('gzip < /var/lib/libvirt/images/centos2.qcow2 > ~YourRegularUsername/backups/centos2.qcow2.gz')<br />&nbsp;&nbsp;print('Backing up centos3')<br />&nbsp;&nbsp;os.system('gzip < /var/lib/libvirt/images/centos3.qcow2 > ~YourRegularUsername/backups/centos3.qcow2.gz')<br />&#35;Step B-2: They don't want to pass back up all VMs, prompt them for which VM they want to back up<br />&#35;Step C: Prompt the user for the name of the osVM they want to back up<br />&#35;Step C-1: If the user chose Centos1, back up that machine.<br />&#35;Step C-2: If the user chose Centos2, back up that machine.<br />&#35;Step C-3: If the user chose Centos3, back up that machine.system command<br /></code></li><li>Before the block that backs up each machine add a prompt to ask the user if they want to back up all machines. We Use an if statement to check if they said yes (See comment 'Step A').<ul><li>if they did this because this script needs say yes, back up all the VMs using your existing block (Comment step B-1).</li><li>If they didn't say yes, do nothing for now (you could even use python variable 's pass statement).</li></ul></li><li>Test your script to make sure it works. Check what happens if you say 'yes' to be evaluated before the whole line gets handed over prompt, and check what happens if you say things other than 'yes'.</li><li>Now we have a script that asks the user if they want to back up all VMS, and if they say they do, it does. But if they don't want to osback up every VM, it currently does nothing.system</li><li>Add an else statement at comment Step B-2 to handle the user not wanting to back up every VM. If Inside that else clause (Comment step C) ask the user which VM they would like to back up (you left can even give them the variable names of available VMs (Centos1, Centos2, Centos3).</li><li>Now nest an if statement inside the quotesthat else (Comments C-1, C-2, python will ignore them as and C-3) so that your script can handle what your user just being part of a stringresponded with. If they asked for Centos1, back up Centos1. If they want to back up Centos2, only back up Centos2, etc. Hint: You might want to use elif for this.</li><li>Test your script again. By putting them outside of You should now have a stringscript that:<ul><li>Makes sure the user is running the script with elevated permissions.</li><li>Asks the user if they want to back up every VM.</li><li>If they want to back up every VM, and concatenating their value it backs up every VM.</li><li>If the user does not want to that stringback up every VM, we can evaluate the script asks them and feed them into which VM they do want to back up.</li><li>If the user selected a single VM, the script will back up that commandone VM.</li><li>Convert Now you may notice another issue with the rest script: The gzip lines are almost identical. The only difference in them is the name of the bash script above into pythonVM file being backed up. In the portion of code where you back up each machine individually (comment steps C-1, C-2, then test your python version and C-3) try replacing the machine name in the gzip command with a string variable that holds the machine's name instead. Note that you will have to make sure it worksus of string concatenation for this to work correctly.</li></ul></li>
</ol>
# Inside each virtual machine, run <b><code>ip a</code></b> on the command line. Open a Terminal window in centos1 to do so. You'll need the IP address of each machine for the next steps.
# Switch to your '''c7host''' VM, open a terminal, login as root, and change directory to '''/root/bin'''.
# Issue the Linux command: <b><code><span style="color:#3366CC;font-size:1.2em;">wget https://ictraw.senecacollegegithubusercontent.cacom/~peter.callaghanOPS245/ops245labs/labsmain/lab2-check.bash</span></code></b>
# Give the '''lab2-check.bash''' file execute permissions (for the file owner).
# Run the shell script and if any warnings, make fixes and re-run shell script until you receive "congratulations" message.
#Arrange proof of the following on the screen:
::&#x2713; '''<u>All</u> VMs''':<blockquote><ul><li>All 4 nested VMs '''created''' and '''running'''</li><li> Proof of '''yum updates''' on ALL VMs (i.e. results from '''yum update''' command)</li></ul></blockquote>
::<span style="color:green;font-size:1.5em;">&#x2713;</span>'''c7host VM''':<blockquote><ul><li>Run the '''lab2-check.bash''' script in front of your instructor (must have all <b><code><span style="color:#66cc00;border:thin solid black;font-size:1.2em;">&nbsp;OK&nbsp;</span></code></b> messages)</li></ul></blockquote>
::<span style="color:green;font-size:1.5em;">&#x2713;</span> Lab2 logbook notes completed.
#Upload a screenshot of the proof listed above, the output file generated by the lab2-check.bash script, your log book, and your backupVM.py to blackboard.
= Practice For Quizzes, Tests, Midterm &amp; Final Exam =
# List the steps to correctly restore your VMs from a USB disk to your c7host VM.
# How can you prompt the user for data and store into a variable?
# How do you perform mathematical operations in the Bash shell and within a Bash shell script?
# What is the difference between a determinant loop and an in-determinant loop?
# Show a few examples how loops can be used to error-check when prompting the user for data.
# What is the purpose of the '''&amp;&amp;''' and '''||''' symbols when used with logic?'
# What does the command '''rpm -qi centos-release''' do and why is it important?
# What is the difference between '''rpm -q centos-release''' and '''uname -a'''?

Navigation menu