Difference between revisions of "OPS245 Lab 2 dev"
(→Purpose / Objectives of Lab 2) |
|||
(78 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
= LAB PREPARATION = | = LAB PREPARATION = | ||
− | [[Image:vmware-1a.png|thumb|right|400px|At the end of lab2, your VMware Workstation application will contain '''4 virtual machines''' (''' | + | [[Image:vmware-1a-rhel.png|thumb|right|400px|At the end of lab2, your VMware Workstation application will contain '''4 virtual machines''' ('''r9host''' in your '''VMware Workstation''' application, and '''rhel1, rhel2, rhel3 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) ]] |
=== Purpose / Objectives of Lab 2=== | === Purpose / Objectives of Lab 2=== | ||
Line 65: | Line 65: | ||
===Part 1: Install KVM Virtualization Application=== | ===Part 1: Install KVM Virtualization Application=== | ||
− | We will now install the KVM package in order to create our remaining "nested" VMs. We will also be starting several services (including | + | We will now install the KVM package in order to create our remaining "nested" VMs. We will also be starting several services (including nftables) and disabling the firewalld service. We will learn more about managing firewalls using nftables in lab6. |
:'''Perform the following steps:''' | :'''Perform the following steps:''' | ||
− | # Log into your | + | # Log into your r9host machine. |
− | # perform a software update on your ''' | + | # perform a software update on your '''r9host''' VM by issuing the following command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo dnf update</span></code></b> |
{{Admon/important |Yum Update Hangs|If you experience yum update "hanging" around item 689 of over 1200 packages, issue the following commands <b>(in a new terminal!)</b>:<br><source>sudo pkill systemctl | {{Admon/important |Yum Update Hangs|If you experience yum update "hanging" around item 689 of over 1200 packages, issue the following commands <b>(in a new terminal!)</b>:<br><source>sudo pkill systemctl | ||
Line 77: | Line 77: | ||
</source>'''NOTE:''' Do NOT press '''<ctrl>c''' since it may cause your machine to cause a kernel panic when you restart your machine.}} | </source>'''NOTE:''' Do NOT press '''<ctrl>c''' since it may cause your machine to cause a kernel panic when you restart your machine.}} | ||
− | <ol><li value="3">Using elevated privileges, install the virtualization software by issuing the command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">sudo | + | <ol><li value="3">Using elevated privileges, install the virtualization software by issuing the command:<br><b><code><span style="color:#3366CC;font-size:1.2em;">sudo dnf install libvirt virt-manager python3-libvirt virt-viewer</span></code></b> <br><br></li> |
− | <li>'''Restart your | + | <li>'''Restart your r9host virtual machine'''. If you fail to do this, you may experience virtualization network problems. |
{| width="40%" align="right" cellpadding="10" | {| width="40%" align="right" cellpadding="10" | ||
|- valign="top" | |- valign="top" | ||
| | | | ||
− | {{Admon/note|About KVM|There are actually several key programs installed for virtualization using KVM:<ul><li>'''kvm/qemu''' - the hypervisor and other hardware emulation systems.</li><li>A system service named ''' | + | {{Admon/note|About KVM|There are actually several key programs installed for virtualization using KVM:<ul><li>'''kvm/qemu''' - the hypervisor and other hardware emulation systems.</li><li>A system service named '''libvirt''' that manages the VMs.</li><li>A graphical tool for managing virtual machines ('''virt-manager''') and the '''virsh''' command-line tool.</li></ul>}} |
|} | |} | ||
− | </li><li>Start the virtualization service: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl start libvirtd</span></code></b><br><br>'''NOTE:''' The most recent variants of | + | </li><li>Start the virtualization service: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl start libvirtd</span></code></b><br><br>'''NOTE:''' The most recent variants of RHEL a service called '''nftables''' that replaces '''firewalld''', however the ''firewalld'' is still active by default. Firewalld rules are translated by the kernel into nftables rules. Therefore, it makes sense to learn nftables. In this course we will concentrate on ''nftables''.<br><br></li> |
<li>To disable and remove firewalld, issue the following commands:<br> | <li>To disable and remove firewalld, issue the following commands:<br> | ||
<b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl disable firewalld</span></code></b><br> | <b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl disable firewalld</span></code></b><br> | ||
<b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl stop firewalld</span></code></b><br> | <b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl stop firewalld</span></code></b><br> | ||
− | |||
<br></li> | <br></li> | ||
− | <li>To | + | <li>To start and enable the nftables services, issue the following commands:<br> |
− | <b><code><span style="color:#3366CC;font-size:1.2em;">sudo | + | <b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl enable nftables</span></code></b><br> |
− | <b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl | + | <b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl start nftables</span></code></b><br><br> |
− | <b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl | + | </li> |
+ | <li>Issue the following command to confirm the nftables service is running:<br> | ||
+ | <b><code><span style="color:#3366CC;font-size:1.2em;">sudo systemctl status nftables</span></code></b><br> | ||
</li> | </li> | ||
</ol> | </ol> | ||
Line 99: | Line 100: | ||
<ol> | <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 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 | + | <li>You will be learning in the next investigation to perform several different types of Red Hat Linux installs.</li> |
</ol> | </ol> | ||
===Part 2: Configure VMware Workstation for Nested VMs === | ===Part 2: Configure VMware Workstation for Nested VMs === | ||
− | Although we are using VMware Workstation to run our | + | Although we are using VMware Workstation to run our r9host VM, we will now install and configure another virtualization package called KVM in order to install the remaining VMs for this course. |
− | Since we are "nesting" VMs (i.e. running a VM inside another VM) we need to configure our | + | Since we are "nesting" VMs (i.e. running a VM inside another VM) we need to configure our r9host's Linux boot-up parameters in order to allow these VMs to run efficiently. |
:'''Perform the following steps:''' | :'''Perform the following steps:''' | ||
− | # In a terminal use | + | # In a terminal use elevated privileges to edit the file called: '''/etc/modprobe.d/kvm.conf'''<ul><li>'''If this file doesn't exist, double-check your UEFI settings in VMWare Workstation for r9host. 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! | # Search for the <b>first occurrence</b> of the Linux Kernel boot command. Do not make the following changes on more than one entry! | ||
− | # | + | # Uncomment (remove the #) the boot option: '''options kvm_intel nested=1''' (for AMD processors '''options kvm_amd nested=1'''). See sample configuration below: |
<ol> | <ol> | ||
{{Admon/important|About the reference settings shown below| | {{Admon/important|About the reference settings shown below| | ||
− | * Only '''ONE''' of these settings | + | * Only '''ONE''' of these settings is applicable depending on your processor |
− | * | + | * If you are unsure whether you are using an AMD or Intel processor, run the command: '''sudo lscpu'''. This will also confirm if you have enabled virtualization or not. |
+ | }} | ||
</ol> | </ol> | ||
− | <blockquote>< | + | <blockquote> |
− | + | <br> | |
− | + | <pre style="font-family:courier;font-size:1.2em;margin-left:20px;"> | |
− | </ | + | # Setting modprobe kvm_intel/kvm_amd nested = 1 |
+ | # only enables Nested Virtualization until the next reboot or | ||
+ | # module reload. Uncomment the option applicable | ||
+ | # to your system below to enable the feature permanently. | ||
+ | # | ||
+ | # User changes in this file are preserved across upgrades. | ||
+ | # | ||
+ | # For Intel | ||
+ | options kvm_intel nested=1 | ||
+ | # | ||
+ | # For AMD | ||
+ | #options kvm_amd nested=1 | ||
+ | </pre> | ||
+ | </blockquote> | ||
<span style="color:red;font-weight:bold">OR</span> | <span style="color:red;font-weight:bold">OR</span> | ||
− | <blockquote | + | <blockquote> |
<br> | <br> | ||
− | + | <pre style="font-family:courier;font-size:1.2em;margin-left:20px;"> | |
− | </ | + | # Setting modprobe kvm_intel/kvm_amd nested = 1 |
+ | # only enables Nested Virtualization until the next reboot or | ||
+ | # module reload. Uncomment the option applicable | ||
+ | # to your system below to enable the feature permanently. | ||
+ | # | ||
+ | # User changes in this file are preserved across upgrades. | ||
+ | # | ||
+ | # For Intel | ||
+ | #options kvm_intel nested=1 | ||
+ | # | ||
+ | # For AMD | ||
+ | options kvm_amd nested=1 | ||
+ | </pre> | ||
+ | </blockquote> | ||
− | <ol><li value="4">Save your editing changes, close the virtual machine application, and <u>'''reboot'''</u> your | + | <ol><li value="4">Save your editing changes, close the virtual machine application, and <u>'''reboot'''</u> your r9host VM.</li> |
− | <li>If you configured your | + | <li>If you configured your r9host 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> | <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> | </ol> | ||
Line 145: | Line 173: | ||
|- valign="top" | |- valign="top" | ||
− | |{{Admon/important|Keep the root password the same for Host and VMs|In order to simplify running the lab checking scripts in future labs, using the same root password for ALL machines ( | + | |{{Admon/important|Keep the root password the same for Host and VMs|In order to simplify running the lab checking scripts in future labs, using the same root password for ALL machines (r9host and virtual machines). Also use the same username and passwords for all of your machines (r9host and virtual machines).}}<br><br> |
|} | |} | ||
=== Part 1: Installing VM from a Network (Graphical)=== | === Part 1: Installing VM from a Network (Graphical)=== | ||
Line 151: | Line 179: | ||
:'''VM Details:''' | :'''VM Details:''' | ||
− | :: '''VM Name (and hostname):''' | + | :: '''VM Name (and hostname):''' rhel1 |
− | :: '''Boot media:''' | + | :: '''Boot media:''' Local installation |
− | :: ''' | + | :: '''RHEL Boot ISO:''' Download from [https://access.redhat.com/ Red Hat customer portal] (instructions below) |
− | + | :: '''VM Image Pathname:''' /var/lib/libvirt/images/rhel1.qcow2 | |
− | |||
− | :: '''VM Image Pathname:''' /var/lib/libvirt/images/ | ||
:: '''Memory:''' 2048MB | :: '''Memory:''' 2048MB | ||
:: '''Disk space:''' 15GB | :: '''Disk space:''' 15GB | ||
:: '''CPUs:''' 2 | :: '''CPUs:''' 2 | ||
− | [[Image:Kvm-warning.jpg|thumb|right|400px|You may see this warning when creating your first VM inside | + | [[Image:Kvm-warning.jpg|thumb|right|400px|You may see this warning when creating your first VM inside RHEL. Select''' ''Don't ask me about these directories again'' '''and click''' ''Yes'''''.]] |
− | |||
− | |||
+ | :'''Perform the following steps on r9host:''' | ||
+ | # Note the time (you will need this after you have finished installing rhel1). | ||
+ | # Open Firefox. | ||
+ | # Login to the [https://access.redhat.com/ Red Hat customer portal] using the credentials you created in Lab 1 and download the Boot ISO (located under additional installation images). | ||
# Launch the ''KVM virtual machine manager'' by clicking '''Applications''' -> '''System Tools''' -> '''Virtual Machine Manager'''. | # Launch the ''KVM virtual machine manager'' by clicking '''Applications''' -> '''System Tools''' -> '''Virtual Machine Manager'''. | ||
# When prompted, enter your password. | # When prompted, enter your password. | ||
# Click the '''create a new VM icon''' located near the top left-corner of the application window. | # Click the '''create a new VM icon''' located near the top left-corner of the application window. | ||
− | # Select the ''' | + | # Select the '''Local Install media''' option and click '''Forward'''. |
− | |||
# Set RAM size to 2048 MB and CPUs to 2, then click '''Forward'''. | # Set RAM size to 2048 MB and CPUs to 2, then click '''Forward'''. | ||
# Set Hard Disk size to 15GB and click '''Forward'''. | # Set Hard Disk size to 15GB and click '''Forward'''. | ||
− | # <span style="background-color:yellow;">Enter the name: ''' | + | # <span style="background-color:yellow;">Enter the name: '''rhel1''', <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;">Another dialog will appear. Click '''CPUs''' (or "processors") and on right-side under Configuration confirm '''Copy Host CPU Configuration''' is selected. If it not, select '''Copy Host CPU Configuration''', click '''Apply''', and then click '''Begin Installation''' at the top left-hand side.</span> |
− | #<span style="background-color:yellow;"> | + | # <span style="background-color:yellow;">Under software select the following</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'''. For hostname, enter: ''' | + | ## Click on "Connect to Red Hat" |
− | + | ### Ensure "Account" is selected beside '''Authentication''' and enter the User name and Password for your Red Hat account. | |
− | # <span style="background-color:yellow;">Complete the installation. Login to your regular user account, and perform a '''sudo | + | ### Check '''Set System Purpose''' and select the following |
+ | #### Role: Red Hat Enterprise Linux Server | ||
+ | #### SLA: Self-Suppport | ||
+ | #### Usage: Production | ||
+ | #### Ensure '''Connect to Red Hat Insights''' is selected. | ||
+ | ### Click '''Register''' | ||
+ | # <span style="background-color:yellow;">Go to software selection and select '''Server with GUI'''. Do not select any additional software.</span> | ||
+ | # <span style="background-color:yellow;">Click on '''Installation Destination''', ensure '''Automatic''' is selected under '''Storage Configuration''' and click '''Done'''</span> | ||
+ | # <span style="background-color:yellow;">Click on '''Root Password''' (note it shows '''Root account is disabled''' in red and set the root password.</span> | ||
+ | # <span style="background-color:yellow;">Click on '''User Creation''' and create your regular user account. Make sure you check the box to make them an administrator.</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'''. For hostname, enter: '''rhel1''' and then click '''Done'''.</span> | ||
+ | # <span style="background-color:yellow;">Complete the installation. Login to your regular user account, and perform a '''sudo dnf update''' for the rhel1 VM (reboot if required). Make certain to adjust your screen-saver settings if desired.</span> | ||
<br> | <br> | ||
− | {{Admon/important|Use same root password / regular username / regular user passwords for | + | {{Admon/important|Use same root password / regular username / regular user passwords for r9host 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 r9host machine in lab1.<br><br>}} |
<br> | <br> | ||
− | <ol><li value="14"><span style="background-color:yellow;">Repeat the steps as you did in the previous investigation ([https://wiki.cdot.senecacollege.ca/wiki/OPS245_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop | + | <ol><li value="14"><span style="background-color:yellow;">Repeat the steps as you did in the previous investigation ([https://wiki.cdot.senecacollege.ca/wiki/OPS245_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop and disable firewalld, start and enable nftables''' for this newly-created VM.</span></li> |
− | <li><span style="background-color:yellow;">Repeat the steps as you did with | + | <li><span style="background-color:yellow;">Repeat the steps as you did with r9host post-install to '''turn off (permissive) SELinux''' and perform a '''dnf update'''.</span></li> |
− | <li>Issue the following command to obtain the IPADDR for your | + | <li>Issue the following command to obtain the IPADDR for your rhel1 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> | <li>Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook.</li> | ||
</ol> | </ol> | ||
Line 191: | Line 229: | ||
:'''VM Details:''' | :'''VM Details:''' | ||
− | :: '''VM Name (and hostname):''' | + | :: '''VM Name (and hostname):''' rhel2 |
− | :: '''Boot media:''' | + | :: '''Boot media:''' Local installation |
− | :: ''' | + | :: '''RHEL Boot ISO:''' Download from [https://access.redhat.com/ Red Hat customer portal] (downloaded in Part 1) |
− | + | :: '''VM Image Pathname:''' /var/lib/libvirt/images/rhel2.qcow2 | |
− | |||
− | :: '''VM Image Pathname:''' /var/lib/libvirt/images/ | ||
:: '''Memory:''' 2048MB | :: '''Memory:''' 2048MB | ||
:: '''Disk space:''' 20GB | :: '''Disk space:''' 20GB | ||
Line 203: | Line 239: | ||
:'''Perform the following steps:''' | :'''Perform the following steps:''' | ||
− | # Create the VM (called ''' | + | # Note the time (you will need this after you have finished installing rhel2). |
− | # Make certain to enter the name: ''' | + | # Create the VM (called '''rhel2''') as you did with the ''rhel1'' machine. |
− | #When selecting the install options for | + | # Make certain to enter the name: '''rhel2''', <u>AND</u> then select the option: '''Customize configuration before install''', and check to ensure '''Copy Host CPU Configuration''' is selected. If it is not, click '''Apply'''. Then click '''Begin Installation'''. |
+ | #When selecting the install options for rhel2, do the same operation that you did in rhel1 (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;">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/OPS245_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop and disable firewalld | + | # <span style="background-color:yellow;">Repeat the steps as you did in the previous investigation ([https://wiki.cdot.senecacollege.ca/wiki/OPS245_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop and disable firewalld, start and enable nftables''' for this newly-created VM.</span> |
− | # <span style="background-color:yellow;">Repeat the steps as you did with | + | # <span style="background-color:yellow;">Repeat the steps as you did with r9host post-install to '''turn off (permissive) SELinux''' (using the command 'vi' instead of 'vim') and perform a '''dnf update'''.</span> |
− | # Issue the following command to obtain and record your | + | # Issue the following command to obtain and record your rhel2 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. | # Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook. | ||
+ | # When you're ready to shutdown your VM, issue the command <b><code><span style="color:#3366CC;font-size:1.2em;">sudo poweroff</span></code></b>. | ||
=== Part 3: Installing from a Network using a Kickstart File === | === Part 3: Installing from a Network using a Kickstart File === | ||
{| width="40%" align="right" cellpadding="10" | {| width="40%" align="right" cellpadding="10" | ||
|- valign="top" | |- 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 | + | |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 rhel3. <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 Red Hat Enterprise Linux 9' or 'Test this media & install Red Hat Enterprise Linux 9', highlight 'Install Red Hat Enterprise Linux 9' and press '''<tab>'''. This will open a prompt at the bottom of the window for you to enter grub configuration options. Type '''inst.ks=https://raw.githubusercontent.com/OPS245/labs/main/centos7-kickstart.cfg''' and hit '''<enter>'''.}} |
|} | |} | ||
Line 221: | Line 259: | ||
:'''VM Details:''' | :'''VM Details:''' | ||
− | :: '''VM Name (and hostname):''' | + | :: '''VM Name (and hostname):''' rhel3 |
:: '''Boot media:''' Network installation | :: '''Boot media:''' Network installation | ||
− | :: ''' | + | :: '''RHEL Boot ISO:''' Download from [https://access.redhat.com/ Red Hat customer portal] (downloaded in Part 1) |
− | |||
− | |||
:: '''Kickstart File URL (Kernel options): ''' | :: '''Kickstart File URL (Kernel options): ''' | ||
− | :::* Home:''' <span style="color:green;font-weight:bold">ks=</span>https://raw.githubusercontent.com/OPS245/labs/main/ | + | :::* Home:''' <span style="color:green;font-weight:bold">ks=</span>https://raw.githubusercontent.com/OPS245/labs/main/rhel9-ks.cfg |
− | :: '''VM Image Pathname:''' /var/lib/libvirt/images/ | + | :: '''VM Image Pathname:''' /var/lib/libvirt/images/rhel3.qcow2 |
:: '''Memory:''' 2048MB ('''IMPORTANT''' Do not use less than 2048MB during installation.) | :: '''Memory:''' 2048MB ('''IMPORTANT''' Do not use less than 2048MB during installation.) | ||
:: '''Disk space:''' 15GB | :: '''Disk space:''' 15GB | ||
:: '''CPUs:''' 2 | :: '''CPUs:''' 2 | ||
− | <br> | + | <br><br><br><br> |
{{Admon/important|Include ''ks='' in the URL options field!|When using a kickstart file, make sure you include the''' ''ks='' '''portion of the link. If done correctly, you should not be able to select partitions or any other settings.}} | {{Admon/important|Include ''ks='' in the URL options field!|When using a kickstart file, make sure you include the''' ''ks='' '''portion of the link. If done correctly, you should not be able to select partitions or any other settings.}} | ||
<br> | <br> | ||
:'''Perform the following steps:''' | :'''Perform the following steps:''' | ||
− | + | # Note the time (you will need this after you have finished installing rhel3). | |
− | # Create the VM (called ''' | + | # Create the VM (called '''rhel3''') |
− | # 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://raw.githubusercontent.com/OPS245/labs/main/ | + | # 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://raw.githubusercontent.com/OPS245/labs/main/rhel9-ks.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 | # 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: ''' | + | # Make certain to enter the name: '''rhel3''', <u>AND</u> then select the option: '''Customize configuration before install''', and select '''Copy Host CPU Configuration''', click '''Apply''', and then click '''Begin Installation'''. |
# Observe the installation. How is it different from booting from a downloaded image? | # Observe the installation. How is it different from booting from a downloaded image? | ||
− | # Record the time taken to install, and compare this to the time taken by the previous installations.<br><br>If during the installation, you see the message at the bottom '''Pane is Dead''', click the '''Virtual Machine''' menu at the top, select '''Shut Down''' -> '''Force Off''', '''right-click''' on ''' | + | # Record the time taken to install, and compare this to the time taken by the previous installations.<br><br>If during the installation, you see the message at the bottom '''Pane is Dead''', click the '''Virtual Machine''' menu at the top, select '''Shut Down''' -> '''Force Off''', '''right-click''' on '''rhel3''' in the ''virtual manager'' window and select '''Delete'''. Redo the VM setup for a new instance of the ''rhel3'' VM.<br><br> |
# What happens when the installation is finished? | # What happens when the installation is finished? | ||
# '''In a web browser''', click the kickstart (KS) link above. This link is a text file. Read through it to find the following information (pay attention to lines starting with #) and record it in your Lab Logbook:<ul><li>'''Regular-user account name'''</li><li>'''Regular-user account password'''</li><li>'''Root Password'''</li></ul> | # '''In a web browser''', click the kickstart (KS) link above. This link is a text file. Read through it to find the following information (pay attention to lines starting with #) and record it in your Lab Logbook:<ul><li>'''Regular-user account name'''</li><li>'''Regular-user account password'''</li><li>'''Root Password'''</li></ul> | ||
+ | # '''Note:''' the Regular-user account password and Root Passwords are encrypted in the kickstart (ks) file. They are both the same as the Regular-user account name (ops245). | ||
# Boot the virtual machine and log in (use the user ID and password information from the previous step to gain access to this VM). | # 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. | # 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/OPS245_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop and disable firewalld | + | # <span style="background-color:yellow;">Repeat the steps as you did in the previous investigation ([https://wiki.cdot.senecacollege.ca/wiki/OPS245_Lab_2#Part_1:_Install_KVM_Virtualization_Application Investigation1 Part 1]) to '''stop and disable firewalld, start and enable nftables''' for this newly-created VM.</span> |
− | # <span style="background-color:yellow;">Repeat the steps as you did with | + | # <span style="background-color:yellow;">Repeat the steps as you did with r9host post-install to '''turn off SELinux'''</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 | + | :::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 nftables for you (but it didn't). |
− | # Issue the following command to obtain and record your | + | # Remember that rhel3 is text-based interface only (no graphics). To recover from a blank screen, press a key (like the SPACE key) to return to the screen display. |
− | # | + | # Issue the following command to obtain and record your rhel3 IPADDR in your lab2 logbook: <code><span style="color:#3366CC;font-size:1.2em;">ip address show</span></code> |
+ | # Perform a <code><span style="color:#3366CC;font-size:1.2em;">'''dnf update'''</span></code>. Notice you receive a message telling you the system is not registered with an entitlement server. That is because the kickstart file did not attach a subscription for you. | ||
+ | # Attach a subscription using the subscription-manager cli tool. This will register your system with Red Hat (using your Red Hat account) like we did in the installation for r9host, rhel1 and rhel2; just as a post installation task. Issue the following commands to set the system purpose (just like we did graphically through the installer): | ||
+ | ## <code><span style="color:#3366CC;font-size:1.2em;">sudo subscription-manager syspurpose role --set "Red Hat Enterprise Linux Server"</span></code> | ||
+ | ## <code><span style="color:#3366CC;font-size:1.2em;">sudo subscription-manager syspurpose service-level --set Self-Support</span></code> | ||
+ | ## <code><span style="color:#3366CC;font-size:1.2em;">sudo subscription-manager syspurpose usage --set Development/Test</span></code> | ||
+ | # Now use the following command to register your system and attach your subscription. Enter your Red Hat account credentials (which you created in Lab 1) when prompted: | ||
+ | ## <code><span style="color:#3366CC;font-size:1.2em;">sudo subscription-manager register</span></code> | ||
+ | ## <code><span style="color:#3366CC;font-size:1.2em;">sudo subscription-manager attach</span></code> | ||
+ | # Try updating your system again with dnf. This time it should succeed. | ||
# Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook. | # Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook. | ||
Line 269: | Line 315: | ||
:'''Perform the following steps:''' | :'''Perform the following steps:''' | ||
− | # Shut down your ''' | + | # Shut down your '''rhel1''', '''rhel2''', and '''rhel3''' VMs. For ''rhel2'' and ''rhel3'', which are CLI-only, you can issue the following command to shutdown: <b><code><span style="color:#3366CC;font-size:1.2em;">poweroff</span></code></b>. Please be patient, the VMs will shut down! |
− | # In your ''' | + | # In your '''r9host''' VM, open a new Terminal window. |
+ | # Create the backups directory in your regular user's home directory. | ||
# Use elevated privileges 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 elevated privileges 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 '''exit''' to return to your normal user account. | # 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 '''exit''' 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. | # 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 ''' | + | # Make a compressed backup of your '''rhel1.qcow2''', '''rhel2.qcow2''', and '''rhel3.qcow2''' files to your regular user's home directory by issuing each command - one at a time :<br><b><code><span style="color:#3366CC;font-size:1.2em;">gzip < rhel1.qcow2 > ~YourRegularUsername/backups/rhel1.qcow2.gz</span></code></b><br><b><code><span style="color:#3366CC;font-size:1.2em;">gzip < rhel2.qcow2 > ~YourRegularUsername/backups/rhel2.qcow2.gz</span></code></b><br><b><code><span style="color:#3366CC;font-size:1.2em;">gzip < rhel3.qcow2 > ~YourRegularUsername/backups/rhel3.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 '''<ctrl>c''' to cancel this process. If you do, your archive will become incomplete and your recovery will be corrupt.}} | {{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 '''<ctrl>c''' to cancel this process. If you do, your archive will become incomplete and your recovery will be corrupt.}} | ||
<ol><li value="7"> 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> | <ol><li value="7"> 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>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 ''''' | + | <li> Start the '''''rhel3''''' VM.</li> |
<li> '''Make certain that you are in your VM and <u>not</u> in your main system!''' </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 | + | <li> Wreck <u>only</u> your rhel3 system! Try this command inside the rhel3 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 | + | <li> Shut down and restart the rhel3 VM (you may need to use the '''Force Reset''' option to do so).</lI> |
<li> When the machine restarts it will not boot since all system files have been removed!</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 | + | <li> Use the '''Force Off''' option to turn rhel3 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;">gunzip < ~YourRegularUsername/backups/ | + | <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;">gunzip < ~YourRegularUsername/backups/rhel3.qcow2.gz > /var/lib/libvirt/images/rhel3.qcow2'''</span></code></b></li> |
<li> Restart the VM. Is it working normally?</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 | + | <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 rhel3 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 | + | <li> Execute the following command: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo virsh dumpxml rhel3 > rhel3.xml</span></code></b></li> |
− | <li> Examine the file <b><code><span style="color:#3366CC;font-size:1.2em;"> | + | <li> Examine the file <b><code><span style="color:#3366CC;font-size:1.2em;">rhel3.xml</span></code></b>. What does it contain? What format is it in?<br></li></ol> |
=== Part 2: Restoring Virtual Machines === | === Part 2: Restoring Virtual Machines === | ||
Line 320: | Line 367: | ||
:'''Perform the following steps:''' | :'''Perform the following steps:''' | ||
− | # Start the ''' | + | # Start the '''rhel1''' virtual machine, and stop the '''rhel2''' and '''rhel3''' virtual machines. |
− | # Switch to the ''' | + | # Switch to the '''r9host''' machine, and open a shell terminal. |
− | # Enter these admin commands into your ''' | + | # Enter these admin commands into your '''r9host''' 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</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 --all</span></code></b> | ||
:: <b><code><span style="color:#3366CC;font-size:1.2em;">sudo virsh list --inactive</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 | + | <ol><li value="4">Now, shut-down your rhel1 VM normally, and close the rhel1 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 rhel1</span></code></b></li><li>Using the appropriate command check to see if your rhel1 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!|}} | {{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!|}} | ||
<br/> | <br/> | ||
Line 368: | Line 415: | ||
exit()<br /> | exit()<br /> | ||
else:<br /> | else:<br /> | ||
− | print('Backing up | + | print('Backing up rhel1')<br /> |
− | os.system('gzip < /var/lib/libvirt/images/ | + | os.system('gzip < /var/lib/libvirt/images/rhel1.qcow2 > ~YourRegularUsername/backups/rhel1.qcow2.gz')<br /> |
− | print('Backing up | + | print('Backing up rhel2')<br /> |
− | os.system('gzip < /var/lib/libvirt/images/ | + | os.system('gzip < /var/lib/libvirt/images/rhel2.qcow2 > ~YourRegularUsername/backups/rhel2.qcow2.gz')<br /> |
− | print('Backing up | + | print('Backing up rhel3')<br /> |
− | os.system('gzip < /var/lib/libvirt/images/ | + | os.system('gzip < /var/lib/libvirt/images/rhel3.qcow2 > ~YourRegularUsername/backups/rhel3.qcow2.gz')<br /> |
</code> | </code> | ||
Line 407: | Line 454: | ||
#Step A: Find out if user wants to back up all VMs<br /> | #Step A: Find out if user wants to back up all VMs<br /> | ||
#Step B-1:use the existing loop to back up all the VMs<br /> | #Step B-1:use the existing loop to back up all the VMs<br /> | ||
− | print('Backing up | + | print('Backing up rhel1')<br /> |
− | os.system('gzip < /var/lib/libvirt/images/ | + | os.system('gzip < /var/lib/libvirt/images/rhel1.qcow2 > ~YourRegularUsername/backups/rhel1.qcow2.gz')<br /> |
− | print('Backing up | + | print('Backing up rhel2')<br /> |
− | os.system('gzip < /var/lib/libvirt/images/ | + | os.system('gzip < /var/lib/libvirt/images/rhel2.qcow2 > ~YourRegularUsername/backups/rhel2.qcow2.gz')<br /> |
− | print('Backing up | + | print('Backing up rhel3')<br /> |
− | os.system('gzip < /var/lib/libvirt/images/ | + | os.system('gzip < /var/lib/libvirt/images/rhel3.qcow2 > ~YourRegularUsername/backups/rhel3.qcow2.gz')<br /> |
#Step B-2: They don't want to back up all VMs, prompt them for which VM they want to back up<br /> | #Step B-2: They don't want to back up all VMs, prompt them for which VM they want to back up<br /> | ||
#Step C: Prompt the user for the name of the VM they want to back up<br /> | #Step C: Prompt the user for the name of the VM they want to back up<br /> | ||
− | #Step C-1: If the user chose | + | #Step C-1: If the user chose rhel1, back up that machine.<br /> |
− | #Step C-2: If the user chose | + | #Step C-2: If the user chose rhel2, back up that machine.<br /> |
− | #Step C-3: If the user chose | + | #Step C-3: If the user chose rhel3, back up that machine.<br /> |
</code></li> | </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. Use an if statement to check if they said yes (See comment 'Step A'). | <li>Before the block that backs up each machine add a prompt to ask the user if they want to back up all machines. Use an if statement to check if they said yes (See comment 'Step A'). | ||
Line 423: | Line 470: | ||
<li>Test your script to make sure it works. Check what happens if you say 'yes' to the prompt, and check what happens if you say things other than 'yes'.</li> | <li>Test your script to make sure it works. Check what happens if you say 'yes' to the 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 back up every VM, it currently does nothing.</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 back up every VM, it currently does nothing.</li> | ||
− | <li>Add an else statement at comment Step B-2 to handle the user not wanting to back up every VM. Inside that else clause (Comment step C) ask the user which VM they would like to back up (you can even give them the names of available VMs ( | + | <li>Add an else statement at comment Step B-2 to handle the user not wanting to back up every VM. Inside that else clause (Comment step C) ask the user which VM they would like to back up (you can even give them the names of available VMs (rhel1, rhel2, rhel3).</li> |
− | <li>Now nest an if statement inside that else (Comments C-1, C-2, and C-3) so that your script can handle what your user just responded with. If they asked for | + | <li>Now nest an if statement inside that else (Comments C-1, C-2, and C-3) so that your script can handle what your user just responded with. If they asked for rhel1, back up rhel1. If they want to back up rhel2, only back up rhel2, etc. Hint: You might want to use elif for this.</li> |
<li>Test your script again. You should now have a script 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, it backs up every VM.</li><li>If the user does not want to back up every VM, the script asks them which VM they do want to back up.</li><li>If the user selected a single VM, the script will back up that one VM.</li> | <li>Test your script again. You should now have a script 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, it backs up every VM.</li><li>If the user does not want to back up every VM, the script asks them which VM they do want to back up.</li><li>If the user selected a single VM, the script will back up that one VM.</li> | ||
<li>Now you may notice another issue with the script: The gzip lines are almost identical. The only difference in them is the name of the VM file being backed up. In the portion of code where you back up each machine individually (comment steps C-1, C-2, 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 us of string concatenation for this to work correctly.</li></ul></li> | <li>Now you may notice another issue with the script: The gzip lines are almost identical. The only difference in them is the name of the VM file being backed up. In the portion of code where you back up each machine individually (comment steps C-1, C-2, 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 us of string concatenation for this to work correctly.</li></ul></li> | ||
Line 434: | Line 481: | ||
:'''Perform the Following Steps:''' | :'''Perform the Following Steps:''' | ||
− | # Use the '''virsh start''' command to launch all the VMs (''' | + | # Use the '''virsh start''' command to launch all the VMs ('''rhel1''', '''rhel2''', and '''rhel3'''). |
− | # Inside each virtual machine, run <b><code>ip a</code></b> on the command line. Open a Terminal window in | + | # Inside each virtual machine, run <b><code>ip a</code></b> on the command line. Open a Terminal window in rhel1 to do so. You'll need the IP address of each machine for the next steps. |
− | # Switch to your ''' | + | # Switch to your '''r9host''' 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://raw.githubusercontent.com/OPS245/labs/main/lab2-check.bash</span></code></b> | # Issue the Linux command: <b><code><span style="color:#3366CC;font-size:1.2em;">wget https://raw.githubusercontent.com/OPS245/labs/main/lab2-check.bash</span></code></b> | ||
# Give the '''lab2-check.bash''' file execute permissions (for the file owner). | # 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. | # 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: | + | # Arrange proof of the following on the screen: |
::✓ '''<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> | ::✓ '''<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> | ||
Line 450: | Line 497: | ||
= Practice For Quizzes, Tests, Midterm & Final Exam = | = Practice For Quizzes, Tests, Midterm & Final Exam = | ||
− | # What is the name of the | + | # What is the name of the Red Hat Enterprise Linux installation program? |
− | # What is the name of the file created by the | + | # What is the name of the file created by the Red Hat Enterprise Linux installation program? |
# Which type of installation works best for confirming compatibility with hardware before installation? Why? | # Which type of installation works best for confirming compatibility with hardware before installation? Why? | ||
# Which type of installation works best for installing large numbers of computers? Why? | # Which type of installation works best for installing large numbers of computers? Why? | ||
Line 461: | Line 508: | ||
# How to start and stop VMs using the virsh command? | # How to start and stop VMs using the virsh command? | ||
# List the steps to correctly backup your VMs to a USB disk | # List the steps to correctly backup your VMs to a USB disk | ||
− | # List the steps to correctly restore your VMs from a USB disk to your | + | # List the steps to correctly restore your VMs from a USB disk to your r9host VM. |
# How can you prompt the user for data and store into a variable? | # How can you prompt the user for data and store into a variable? | ||
# Show a few examples how loops can be used to error-check when prompting the user for data. | # Show a few examples how loops can be used to error-check when prompting the user for data. | ||
− | # What does the command '''rpm -qi | + | # What does the command '''rpm -qi redhat-release''' do and why is it important? |
− | # What is the difference between '''rpm -q | + | # What is the difference between '''rpm -q redhat-release''' and '''uname -a'''? |
Latest revision as of 22:54, 14 February 2023
Contents
- 1 LAB PREPARATION
- 2 INVESTIGATION 1: SETUP FOR NESTED VIRTUAL MACHINES
- 3 INVESTIGATION 2: INSTALL NESTED VIRTUAL MACHINES (KVM)
- 4 INVESTIGATION 3: MANAGING VIRTUAL MACHINES (KVM)
- 5 INVESTIGATION 4: USING PYTHON TO AUTOMATE MANAGING VIRTUAL MACHINES
- 6 LAB 2 SIGN-OFF (SHOW INSTRUCTOR)
- 7 Practice For Quizzes, Tests, Midterm & Final Exam
LAB PREPARATION
Purpose / Objectives of Lab 2
In this lab, you will create 3 remaining virtual machines using another virtualization program called KVM that will run in your r9host VM. These VMs will be used throughout the remainder of this course to learn how to administer them (installing software, managing services, networking, etc).
While you are performing this lab, it is recommended to generally note the major differences in the different installation methods, and which method you prefer to use if you were a Linux system administrator in charge of installing many Linux distributions for an organization.
Main Objectives
- Installing additional Virtualization Software on your r9host machine (KVM)
- Create 3 separate VMs (virtual machines) using different installation methods:
- rhel1: Network Red Hat Enterprise Linux Installation (Graphical)
- rhel2: Network Red Hat Enterprise Linux Installation (minimal install - CLI only)
- rhel3: Network Red Hat Enterprise Linux Installation with Kickstart configuration file (CLI only)
- Manipulate virtual machines by CLI (virsh)
- Properly backup VM images and backup VM configuration files
- Create and run Bash Shell scripts to automatically create a post-install report for an installed VM.
Minimum Required Materials |
Linux Command Reference | ||||
Virtualization |
Miscellaneous |
Matrix Online Tutorials:
|
INVESTIGATION 1: SETUP FOR NESTED VIRTUAL MACHINES
Part 1: Install KVM Virtualization Application
We will now install the KVM package in order to create our remaining "nested" VMs. We will also be starting several services (including nftables) and disabling the firewalld service. We will learn more about managing firewalls using nftables in lab6.
- Perform the following steps:
- Log into your r9host machine.
- perform a software update on your r9host VM by issuing the following command:
sudo dnf update
- Using elevated privileges, install the virtualization software by issuing the command:
sudo dnf install libvirt virt-manager python3-libvirt virt-viewer
- Restart your r9host virtual machine. If you fail to do this, you may experience virtualization network problems.
- Start the virtualization service:
sudo systemctl start libvirtd
NOTE: The most recent variants of RHEL a service called nftables that replaces firewalld, however the firewalld is still active by default. Firewalld rules are translated by the kernel into nftables rules. Therefore, it makes sense to learn nftables. In this course we will concentrate on nftables. - To disable and remove firewalld, issue the following commands:
sudo systemctl disable firewalld
sudo systemctl stop firewalld
- To start and enable the nftables services, issue the following commands:
sudo systemctl enable nftables
sudo systemctl start nftables
- Issue the following command to confirm the nftables service is running:
sudo systemctl status nftables
- Start the graphical tool by selecting the menu options Applications>System Tools>Virtual Machine Manager or by typing the command
virt-manager
(without sudo!) - You will be learning in the next investigation to perform several different types of Red Hat Linux installs.
Part 2: Configure VMware Workstation for Nested VMs
Although we are using VMware Workstation to run our r9host VM, we will now install and configure another virtualization package called KVM in order to install the remaining VMs for this course. Since we are "nesting" VMs (i.e. running a VM inside another VM) we need to configure our r9host's Linux boot-up parameters in order to allow these VMs to run efficiently.
- Perform the following steps:
- In a terminal use elevated privileges to edit the file called: /etc/modprobe.d/kvm.conf
- If this file doesn't exist, double-check your UEFI settings in VMWare Workstation for r9host. If BIOS is selected, you MUST redo Lab 1.
- Search for the first occurrence of the Linux Kernel boot command. Do not make the following changes on more than one entry!
- Uncomment (remove the #) the boot option: options kvm_intel nested=1 (for AMD processors options kvm_amd nested=1). See sample configuration below:
# Setting modprobe kvm_intel/kvm_amd nested = 1 # only enables Nested Virtualization until the next reboot or # module reload. Uncomment the option applicable # to your system below to enable the feature permanently. # # User changes in this file are preserved across upgrades. # # For Intel options kvm_intel nested=1 # # For AMD #options kvm_amd nested=1
OR
# Setting modprobe kvm_intel/kvm_amd nested = 1 # only enables Nested Virtualization until the next reboot or # module reload. Uncomment the option applicable # to your system below to enable the feature permanently. # # User changes in this file are preserved across upgrades. # # For Intel #options kvm_intel nested=1 # # For AMD options kvm_amd nested=1
- Save your editing changes, close the virtual machine application, and reboot your r9host VM.
- If you configured your r9host VM for nested VMs, then you should get the output
Y
when you issue the following command:cat /sys/module/kvm_intel/parameters/nested
- For AMD processors, check the /sys/module/kvm_amd/parameters/nested file. You should get the output
1
- And if kvm_intel directory doesn't exist, double-check your Processors => Virtualization Engine (Intel VT-x/EPT...) settings in VMWare Workstation.
Answer the INVESTIGATION 1 observations / questions in your lab log book.
INVESTIGATION 2: INSTALL NESTED VIRTUAL MACHINES (KVM)
Part 1: Installing VM from a Network (Graphical)
- VM Details:
- VM Name (and hostname): rhel1
- Boot media: Local installation
- RHEL Boot ISO: Download from Red Hat customer portal (instructions below)
- VM Image Pathname: /var/lib/libvirt/images/rhel1.qcow2
- Memory: 2048MB
- Disk space: 15GB
- CPUs: 2
- Perform the following steps on r9host:
- Note the time (you will need this after you have finished installing rhel1).
- Open Firefox.
- Login to the Red Hat customer portal using the credentials you created in Lab 1 and download the Boot ISO (located under additional installation images).
- Launch the KVM virtual machine manager by clicking Applications -> System Tools -> Virtual Machine Manager.
- When prompted, enter your password.
- Click the create a new VM icon located near the top left-corner of the application window.
- Select the Local Install media option 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.
- Enter the name: rhel1, AND then select the option: Customize configuration before install, and click Finish.
- Another dialog will appear. Click CPUs (or "processors") and on right-side under Configuration confirm Copy Host CPU Configuration is selected. If it not, select Copy Host CPU Configuration, click Apply, and then click Begin Installation at the top left-hand side.
- Under software select the following
- Click on "Connect to Red Hat"
- Ensure "Account" is selected beside Authentication and enter the User name and Password for your Red Hat account.
- Check Set System Purpose and select the following
- Role: Red Hat Enterprise Linux Server
- SLA: Self-Suppport
- Usage: Production
- Ensure Connect to Red Hat Insights is selected.
- Click Register
- Click on "Connect to Red Hat"
- Go to software selection and select Server with GUI. Do not select any additional software.
- Click on Installation Destination, ensure Automatic is selected under Storage Configuration and click Done
- Click on Root Password (note it shows Root account is disabled in red and set the root password.
- Click on User Creation and create your regular user account. Make sure you check the box to make them an administrator.
- Set the correct Date and Time Zone, and then click on Network and Hostname. The network should be turned ON. For hostname, enter: rhel1 and then click Done.
- Complete the installation. Login to your regular user account, and perform a sudo dnf update for the rhel1 VM (reboot if required). Make certain to adjust your screen-saver settings if desired.
- Repeat the steps as you did in the previous investigation (Investigation1 Part 1) to stop and disable firewalld, start and enable nftables for this newly-created VM.
- Repeat the steps as you did with r9host post-install to turn off (permissive) SELinux and perform a dnf update.
- Issue the following command to obtain the IPADDR for your rhel1 VM to record in your lab2 logbook:
ip address show
- Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook.
Part 2: Installing from a Network (Minimal install - CLI)
- VM Details:
- VM Name (and hostname): rhel2
- Boot media: Local installation
- RHEL Boot ISO: Download from Red Hat customer portal (downloaded in Part 1)
- VM Image Pathname: /var/lib/libvirt/images/rhel2.qcow2
- Memory: 2048MB
- Disk space: 20GB
- CPUs: 1
- Perform the following steps:
- Note the time (you will need this after you have finished installing rhel2).
- Create the VM (called rhel2) as you did with the rhel1 machine.
- Make certain to enter the name: rhel2, AND then select the option: Customize configuration before install, and check to ensure Copy Host CPU Configuration is selected. If it is not, click Apply. Then click Begin Installation.
- When selecting the install options for rhel2, do the same operation that you did in rhel1 (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).
- Complete the installation. Login to your regular user account.
- Repeat the steps as you did in the previous investigation (Investigation1 Part 1) to stop and disable firewalld, start and enable nftables for this newly-created VM.
- Repeat the steps as you did with r9host post-install to turn off (permissive) SELinux (using the command 'vi' instead of 'vim') and perform a dnf update.
- Issue the following command to obtain and record your rhel2 IPADDR in your lab2 logbook:
ip address show
- Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook.
- When you're ready to shutdown your VM, issue the command
sudo poweroff
.
Part 3: Installing from a Network using a Kickstart File
- VM Details:
- VM Name (and hostname): rhel3
- Boot media: Network installation
- RHEL Boot ISO: Download from Red Hat customer portal (downloaded in Part 1)
- Kickstart File URL (Kernel options):
- VM Image Pathname: /var/lib/libvirt/images/rhel3.qcow2
- Memory: 2048MB (IMPORTANT Do not use less than 2048MB during installation.)
- Disk space: 15GB
- CPUs: 2
- Perform the following steps:
- Note the time (you will need this after you have finished installing rhel3).
- Create the VM (called rhel3)
- 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:
- 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: rhel3, AND then select the option: Customize configuration before install, and select Copy Host CPU Configuration, click Apply, and then click Begin Installation.
- Observe the installation. How is it different from booting from a downloaded image?
- Record the time taken to install, and compare this to the time taken by the previous installations.
If during the installation, you see the message at the bottom Pane is Dead, click the Virtual Machine menu at the top, select Shut Down -> Force Off, right-click on rhel3 in the virtual manager window and select Delete. Redo the VM setup for a new instance of the rhel3 VM. - What happens when the installation is finished?
- In a web browser, click the kickstart (KS) link above. This link is a text file. Read through it to find the following information (pay attention to lines starting with #) and record it in your Lab Logbook:
- Regular-user account name
- Regular-user account password
- Root Password
- Note: the Regular-user account password and Root Passwords are encrypted in the kickstart (ks) file. They are both the same as the Regular-user account name (ops245).
- 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.
- Repeat the steps as you did in the previous investigation (Investigation1 Part 1) to stop and disable firewalld, start and enable nftables for this newly-created VM.
- Repeat the steps as you did with r9host post-install to turn off SELinux
- 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 nftables for you (but it didn't).
- Remember that rhel3 is text-based interface only (no graphics). To recover from a blank screen, press a key (like the SPACE key) to return to the screen display.
- Issue the following command to obtain and record your rhel3 IPADDR in your lab2 logbook:
ip address show
- Perform a
dnf update
. Notice you receive a message telling you the system is not registered with an entitlement server. That is because the kickstart file did not attach a subscription for you. - Attach a subscription using the subscription-manager cli tool. This will register your system with Red Hat (using your Red Hat account) like we did in the installation for r9host, rhel1 and rhel2; just as a post installation task. Issue the following commands to set the system purpose (just like we did graphically through the installer):
-
sudo subscription-manager syspurpose role --set "Red Hat Enterprise Linux Server"
-
sudo subscription-manager syspurpose service-level --set Self-Support
-
sudo subscription-manager syspurpose usage --set Development/Test
-
- Now use the following command to register your system and attach your subscription. Enter your Red Hat account credentials (which you created in Lab 1) when prompted:
-
sudo subscription-manager register
-
sudo subscription-manager attach
-
- Try updating your system again with dnf. This time it should succeed.
- Record the time taken to install, and compare this to the time taken by the previous installations in your lab2 logbook.
Answer the INVESTIGATION 2 observations / questions in your lab log book.
INVESTIGATION 3: MANAGING VIRTUAL MACHINES (KVM)
Part 1: Backing Up Virtual Machines
- Perform the following steps:
- Shut down your rhel1, rhel2, and rhel3 VMs. For rhel2 and rhel3, which are CLI-only, you can issue the following command to shutdown:
poweroff
. Please be patient, the VMs will shut down! - In your r9host VM, open a new Terminal window.
- Create the backups directory in your regular user's home directory.
- Use elevated privileges to list the size and names of files in
/var/lib/libvirt/images/
- What do these files contain?
- Use the command
sudo -i
and enter your password if prompted. You are now root until you use the command exit to return to your normal user account. - Change to the images directory by issuing the following command:
cd /var/lib/libvirt/images/
. Note that you did not need to use sudo, as you are already using elevated permissions. - Make a compressed backup of your rhel1.qcow2, rhel2.qcow2, and rhel3.qcow2 files to your regular user's home directory by issuing each command - one at a time :
gzip < rhel1.qcow2 > ~YourRegularUsername/backups/rhel1.qcow2.gz
gzip < rhel2.qcow2 > ~YourRegularUsername/backups/rhel2.qcow2.gz
gzip < rhel3.qcow2 > ~YourRegularUsername/backups/rhel3.qcow2.gz
- NOTE: Make certain to use the redirection signs "<" and ">" properly in the command!
- 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!
- Once you are sure you have all three VMs backed up, use the
exit
command to revert back to your normal user. - Start the rhel3 VM.
- Make certain that you are in your VM and not in your main system!
- Wreck only your rhel3 system! Try this command inside the rhel3 virtual machine:
sudo rm -rf /*
(ignore error messages). - Shut down and restart the rhel3 VM (you may need to use the Force Reset option to do so).
- When the machine restarts it will not boot since all system files have been removed!
- Use the Force Off option to turn rhel3 back off.
- Restore the original image from the backup from your home directory to your images directory by typing
sudo -i
command first [do not forget to exit when you are done], then this command:gunzip < ~YourRegularUsername/backups/rhel3.qcow2.gz > /var/lib/libvirt/images/rhel3.qcow2
- Restart the VM. Is it working normally?
- 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 rhel3 XML configuration file, and prove that a "clone" can be added to your list.Please perform the following step:
- Execute the following command:
sudo virsh dumpxml rhel3 > rhel3.xml
- Examine the file
rhel3.xml
. What does it contain? What format is it in?
Part 2: Restoring Virtual Machines
- 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:
- Use gunzip with elevated privileges to decompress the qcow2 image file into the /var/lib/libvirt/images directory.
- Issue the command:
sudo virsh define centos4.xml
- What happened in the virtual manager window? In order to remove a VM entry in the Virtual Manager window, simply issue the command virsh undefine VM_name without the .xml file extension
- Start up your new centos4 VM.
- Click on the user OPS245, and click the cog icon.
- Notice Cinnamon (Software Rendering) 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 ops245. 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.
- For the remainder of these labs, it is assumed that you will backup both the images and XML configuration files for all 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...
- Answer this question in your log book:
- In order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?
Part 3: Using the Command Line for VM State Management
You will continue our use of the Bash Shell by examining commands will allow the Linux sysadmin to gather information about and manage their Virtual Machines.
- Perform the following steps:
- Start the rhel1 virtual machine, and stop the rhel2 and rhel3 virtual machines.
- Switch to the r9host machine, and open a shell terminal.
- Enter these admin commands into your r9host machine and note the result:
-
sudo virsh list
-
sudo virsh list --all
-
sudo virsh list --inactive
-
- Now, shut-down your rhel1 VM normally, and close the rhel1 VM window.
- Switch to your terminal and issue the command:
sudo virsh start rhel1
- Using the appropriate command check to see if your rhel1 VM is now running.
- 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?
Answer INVESTIGATION 3 observations / questions in your lab log book.
INVESTIGATION 4: USING PYTHON TO AUTOMATE MANAGING VIRTUAL MACHINES
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 specify which VMs they want backed up.
- In your bin directory, create the file backupVM.py, and populate with our standard beginning
#!/usr/bin/env python3
# backupVM.py
# Purpose: Backs up virtual machines
#
# USAGE: ./backupVM.py
#
# Author: *** INSERT YOUR NAME ***
# Date: *** CURRENT DATE ***
import os
currentuser = os.popen('whoami')
if currentuser.read() != 'root':
print("You must be root")
exit()
else:
print('Backing up rhel1')
os.system('gzip < /var/lib/libvirt/images/rhel1.qcow2 > ~YourRegularUsername/backups/rhel1.qcow2.gz')
print('Backing up rhel2')
os.system('gzip < /var/lib/libvirt/images/rhel2.qcow2 > ~YourRegularUsername/backups/rhel2.qcow2.gz')
print('Backing up rhel3')
os.system('gzip < /var/lib/libvirt/images/rhel3.qcow2 > ~YourRegularUsername/backups/rhel3.qcow2.gz')
- Try to run that script. You'll notice it does not work. No matter what you do, it always says you are not root.
- Modify the print statement that tells the user they must be root to also include the current username, then run the program again.
- 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.
- 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.
- 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.
- 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.
#!/usr/bin/env python3
# backupVM.py
# Purpose: Backs up virtual machines
#
# USAGE: ./backupVM.py
#
# Author: *** INSERT YOUR NAME ***
# Date: *** CURRENT DATE ***
import os
#Make sure script is being run with elevated permissions
currentuser = os.popen('whoami').read().strip()
if currentuser != 'root':
print("You must be root")
exit()
else
#The rest of this script identifies steps with comments 'Step <something>'.
#This is not a normal standard for commenting, it has been done here to link the script
# to the instructions on the wiki.
#Step A: Find out if user wants to back up all VMs
#Step B-1:use the existing loop to back up all the VMs
print('Backing up rhel1')
os.system('gzip < /var/lib/libvirt/images/rhel1.qcow2 > ~YourRegularUsername/backups/rhel1.qcow2.gz')
print('Backing up rhel2')
os.system('gzip < /var/lib/libvirt/images/rhel2.qcow2 > ~YourRegularUsername/backups/rhel2.qcow2.gz')
print('Backing up rhel3')
os.system('gzip < /var/lib/libvirt/images/rhel3.qcow2 > ~YourRegularUsername/backups/rhel3.qcow2.gz')
#Step B-2: They don't want to back up all VMs, prompt them for which VM they want to back up
#Step C: Prompt the user for the name of the VM they want to back up
#Step C-1: If the user chose rhel1, back up that machine.
#Step C-2: If the user chose rhel2, back up that machine.
#Step C-3: If the user chose rhel3, back up that machine.
- Before the block that backs up each machine add a prompt to ask the user if they want to back up all machines. Use an if statement to check if they said yes (See comment 'Step A').
- if they did say yes, back up all the VMs using your existing block (Comment step B-1).
- If they didn't say yes, do nothing for now (you could even use python's pass statement).
- Test your script to make sure it works. Check what happens if you say 'yes' to the prompt, and check what happens if you say things other than 'yes'.
- 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 back up every VM, it currently does nothing.
- Add an else statement at comment Step B-2 to handle the user not wanting to back up every VM. Inside that else clause (Comment step C) ask the user which VM they would like to back up (you can even give them the names of available VMs (rhel1, rhel2, rhel3).
- Now nest an if statement inside that else (Comments C-1, C-2, and C-3) so that your script can handle what your user just responded with. If they asked for rhel1, back up rhel1. If they want to back up rhel2, only back up rhel2, etc. Hint: You might want to use elif for this.
- Test your script again. You should now have a script that:
- Makes sure the user is running the script with elevated permissions.
- Asks the user if they want to back up every VM.
- If they want to back up every VM, it backs up every VM.
- If the user does not want to back up every VM, the script asks them which VM they do want to back up.
- If the user selected a single VM, the script will back up that one VM.
- Now you may notice another issue with the script: The gzip lines are almost identical. The only difference in them is the name of the VM file being backed up. In the portion of code where you back up each machine individually (comment steps C-1, C-2, 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 us of string concatenation for this to work correctly.
LAB 2 SIGN-OFF (SHOW INSTRUCTOR)
Follow the submission instructions for lab 2 on Blackboard.
- Perform the Following Steps:
- Use the virsh start command to launch all the VMs (rhel1, rhel2, and rhel3).
- Inside each virtual machine, run
ip a
on the command line. Open a Terminal window in rhel1 to do so. You'll need the IP address of each machine for the next steps. - Switch to your r9host VM, open a terminal, login as root, and change directory to /root/bin.
- Issue the Linux command:
wget https://raw.githubusercontent.com/OPS245/labs/main/lab2-check.bash
- 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:
- ✓ All VMs:
- All 4 nested VMs created and running
- Proof of yum updates on ALL VMs (i.e. results from yum update command)
- ✓c7host VM:
- Run the lab2-check.bash script in front of your instructor (must have all
OK
messages)
- Run the lab2-check.bash script in front of your instructor (must have all
- ✓ Lab2 logbook notes completed.
- ✓ All VMs:
- 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 & Final Exam
- What is the name of the Red Hat Enterprise Linux installation program?
- What is the name of the file created by the Red Hat Enterprise Linux installation program?
- Which type of installation works best for confirming compatibility with hardware before installation? Why?
- Which type of installation works best for installing large numbers of computers? Why?
- How can you reduce the number of software updates required immediately after installation?
- How do you start and stop virtual machines?
- How do you SSH into your virtual machines?
- List the steps to install a VM from:
- Downloaded iso file
- Network install (without kickstart file)
- Network install (with kickstart file)
- What is the purpose of the virsh command?
- How to start and stop VMs using the virsh command?
- List the steps to correctly backup your VMs to a USB disk
- List the steps to correctly restore your VMs from a USB disk to your r9host VM.
- How can you prompt the user for data and store into a variable?
- Show a few examples how loops can be used to error-check when prompting the user for data.
- What does the command rpm -qi redhat-release do and why is it important?
- What is the difference between rpm -q redhat-release and uname -a?