Changes

Jump to: navigation, search

OPS335 Installation Lab

1,909 bytes added, 12:50, 11 August 2022
no edit summary
[[Category:OPS335]][[Category:OPS335 Labs]]
== Objectives OBJECTIVE & PREPARATION ==*Install your host machine (Centos 7)*Install 3 virtual machines (VMs) (Fedora 22 - Server)*Prepare for Lab Exercises / Exploration Questions
== Required materials ==*Centos 7 Installation DVD*One SATA hard disk in This lab is a repeat of a removable drive tray portion of lab1 (minimum 250GBand some of lab2) - It is strongly advised that you dedicate a drive for already performed in OPS235 plus some newer content that relates to this course onlyweek's notes.*Recommended You are expected to be able to complete all this using your existing skills and knowledge or refer back to your OPS235 lab- USB drive (8 GB+) for creating and storing backups (Virtual Machines, configuration files)book or OPS235 WIKI notes.
==Part A: Host Installation ==In this is lab, you will install your '''host machine''' (Centos7), '''install virtualization software''', and '''create and install 3 nested virtual machines'''.
=== Installation instructions for Centos 7 Required materials ===#Download a copy of the Centos 7 installation DVD (64 bit edition) from the Centos web site or belmont. Note: we'll be using the 64 bit version of Centos because all of our lab computers are equiped with Intel 64 bit mainboards and CPUs. We'll also be using a Fedora iso for installing the virtual machines, but you will not need to burn that to a disc. It is faster to download the ISO and install directly from it.#* '''Seneca's mirror of Centos:''' http://belmont.senecacollege.ca/pub/centos/7/isos/x86_64/CentOS-7-x86_64-Full Installation DVD-1511.iso<br />(This is very fast, but is only accessible from within Seneca's network - you can't access this from home. You can burn this disc on the machines in the Open Lab.)<br />#* '''Centos mirror list One Solid State Drive (available from any Internet connectionSSD), mininmum capacity:''' https://www.centos.org/download/mirrors/ 240 GB (version: '''7USB 3.2.1511'''0)<br />#Insert your HDD into the docking bay of a PC in the lab and boot the computer using your installation DVD. If possible try to use the same PC for this course for the rest of the semester. Some PCs may be configured with slight hardware variations from others which may cause problems when moving your HDD from one system to another. #Most modification It is now perform through strongly advised you dedicate a single summary screen. Use it to customize your installation following these guidelines:#*Set Date &amp; Time#*'''Turn on networking''' and use '''your Seneca ID''' as the '''hostname'''.#*Under software selection, choose '''Server with gui''', and ensure you enable the software package '''KDE''' (located on the right-hand-side).#*For installation destination, select your drive (not the one internal to the PC), and select the option to manually configure partitioning.#**Delete any old partitions.#**Click the link to '''create partitions automatically''' (for this will give a typical layout with /, /boot, /boot/efi, /home, etc).#**Free up space by shrinking the '''/home''' partition. Since your machine will have far fewer users and more virtual machines than a typical installation, we will need that space elsewhere.#**Create a new logical volume for '''/var/lib/libvirt/images''' and give it the space made available by shrinking /home (You will need enough space for 6 virtual machines at 8GB each). You may wish to keep some extra space left unassigned in case you need some space later, but the majority of the space you will need will be for ''/var/lib/libvirt/images''.#**Make certain that the existing partitions have the file system type '''ext4''' (not xfs).#During the installation process you will also have the opportunity to create users.#*set the root password#*create a '''user account''' named with '''your Seneca ID'''#After completing the installation, remove the DVD and reboot from your HDDcourse only.
=== Online Resources===
=== Booting your system ===*[https://wiki.centos.org/TipsAndTricks#head-4c9ee55a5c9dc051bd32e795b46a3856e41a0335 Centos7 Install Tips]<br>
==INVESTIGATION 1: HOST INSTALLATION== === Installation instructions for CentOS 7 ===#Login as It may be advisable to obtain the <u>latest version</u> of the CentOS 7 Full Installation DVD since there may be improvements since the user last version from when you created took OPS235.<br><br># Download and open burn on a DVD a terminal windowcopy of the CentOS 7 installation DVD (64 bit edition) from the CentOS web site or the Belmont server. Then use <br>'''Note:'''suwe' to become root ll be using the 64 bit version of CentOS because all of our lab computers are equipped with Intel 64 bit mainboards and CPUs, and run any computer you bought in the last few years for yourself will be 64bit as well.<br><br>#* '''Seneca's mirror of CentOS:''yum update' commandhttps://mirror.senecacollege. Reboot after all updates have completedca/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-2009. Now that your system iso <br>This is up to datevery fast, again login using your learnid and do but is only accessible from within Seneca's network - you can't access this from home. You can burn this disc on the machines in the following:Open Lab.)<br><br>#*Verify that your system date and time are correct'''Outside Seneca College link (available from any Internet connection):<br>''' https://mirror.netflash.net/centos/7.9. If not then set the correct system date and time2009/isos/x86_64/CentOS-7-x86_64-DVD-2009.iso<br /><br>#*Verify that You need to refer to your OPS235 notes in order to install your network host machine.<br>Here is functioninga direct link:<br> [https://wiki.cdot.senecacollege.ca/wiki/OPS245_Lab_1 OPS245 - Lab1] <ol><li value=4>Customize your installation following these guidelines:#**If <ul><li>'''Turn on networking''' and use '''host''' as the '''hostname'''.<li>Under software selection, choose '''Gnome desktop'''.<li>The partition setup is similar to what you do not have an ip address, edit had in OPS235:<ul><li>Delete any old partitions.<li>Select the line in either hard disk and indicate "I will configure partitions" and click done.<li>Click the file link to '''create them (partitions) automatically'''(this will give a typical layout with /, /boot, /boot/efi, /home, etc).<li>Free up at least '''100GB''' of disk space by shrinking the '''/sysconfighome''' partition (At least '''40 GB''' for root (/network-scripts) and '''40GB''' for /ifcfg-eno1home). Since your machine will have far fewer users and more virtual machines than a typical installation, we will need that space elsewhere.<li>Create a new logical volume for ''' or /var/lib/libvirt/images'''and give it the space made available by shrinking /home (You will need enough space for up to 10 virtual machines at 8GB each plus room to compress/etcextract images).<li>Make certain that the existing partitions '''except swap, /sysconfigboot and /network-scriptsboot/ifcfg-eth0efi''' have the file system type '''ext4''' (note this file name may differ between machinesnot xfs). onboot=no</ul></ul><li>After the installation starts you will also have the opportunity to create users.<ul>:should be:<li>Set the root password <li>Create a '''user account'''onboot=yesnamed with '''your MySeneca ID'''</ul></ol><br> === First boot === # In the current version of CentOS the first time you boot your system a graphical licence prompt comes up.<br><br><ol><li value="2">Log in and check that you have access to the internet. If you had don't - you need to get the network interface to change that, reboot come up on boot. Edit the appropriate config file and configure your machine before continuingmain network interface to come up at boot.</liul><li>Run and record You can then use the purpose and output after issuing the following '''ifup'''/'''ifdown''' commands:to reset your network configuration or you can just reboot.</li></olul></li><li> Make certain that '''df -hTSELinux''' is '''cat /etc/fstabenforcing'''for security reasons (this should be the default). To make it ''enforcing'', simply edit the '''cat /etc/issueselinux/config'''file and follow the instructions inside. {{Admon/important |SELinux in Andrew's sections|If you're in one of Andrew'uname s sections -aplease disable SELinux (i.e. do the opposite of the bullet above). This will give you some extra freedom in the rest of the course to learn and experiment without being bogged down by inexplicable permission denied errors.}}</li><li>Install all updates using the '''yum update'''command.</li></ol><br>
===Using iptables===
The most recent variants of Centos and Fedora are using a service called '''firewalld''' that is intended to replace '''iptables''', however the ''iptables'' service is still in relatively common usage. In this course we will keep running concentrate on ''iptables'' .<ol><li>Disable firewalld:<source>systemctl disable firewalldsystemctl stop firewalld</source></ol><ol><li value="2">Install and enable the IPTables services:<source>yum install iptables-servicessystemctl enable iptablessystemctl start iptables</source></ol>At this point you have a basic Centos system installed and updated. This will serve as a host for the virtual machines where you will do the majority of the work in this course. All the rest of our labs will assume you have this basic system running. If, for any reason, your system becomes corrupted during the semester, you'll have to redo this lab to be able to continue with the remaining uncompleted labs. You are responsible for YOUR system. If you do not perform back-ups you have taken this risk on yourself. Poor planning on your part does not constitute an emergency for anyone else. '''Record steps, commands, and your observations in INVESTIGATION 1 in your OPS235 lab log-book''' ==INVESTIGATION 2: VIRTUAL MACHINE INSTALLATION== ===Configuring a VM host=== # You will need to install some software to allow your machine to act as a host for virtual machines. We'll be using the same '''libvirt''' and '''virt-manager''' you used in [https://wiki.cdot.senecacollege.ca/wiki/OPS235_Lab_2 OPS235 - Lab2].<br>You may find it helpful to refer back to the '''OPS235 notes''' to perform the following operations:#* Install the required virtualization software#* Start and enable the virtualization service#* Reboot your host machine<br><br># Start the graphical virtual machine manager (''virt-manager''). Do this as you regular user, and don't run virt-manager from a terminal where you're logged in as root.# We will be creating our own virtual network. A default virtual network has been created for you, but you will be using a <u>custom</u> one in this course.#* Right click '''localhost (QEMU)''' and gain experience with select '''Details'''.#* Click on the '''Virtual Networks''' tab.#* Stop and delete the '''default''' network.#* Use the '''plus sign''' to add a new service virtual network using the following options:#:* Name your virtual network '''ops235'''#:* Use the '''last two digits of your student number for the third octet of network IP address''' (for example, if your student number is 000-000-0<b>90</b>, the network address would be 192.168.<b>90</b>.0/24.#:* Ensure the DHCP range will allow you to assign '''at least 10 static IP addresses outside it''' (firewalldnote: leave the low numbers available for static addresses) on .#:* Choose '''Forwarding to physical network''' radio button, '''Destination: Any physical device''' and '''Mode: NAT'''#:* Ensure the network is '''started at boot'''. <br> === VM Installation=== With the virtualization software installed and your personal network created, you are now ready to create your first virtual machinesmachine.First, It is a good idea to make certain that your host machine has been set up correctly prior to creating your first virtual machine: #install Open a separate terminal and issue the '''ip address show''' command on your host machine to know your physical network and enable iptablesyour virtual network. Note this information for the next few steps. #Issue the following command to download Bash shell script to check your host machine's set-up prior to proceeding with this lab:<br>'''yum install iptables-serviceswget http://ict.senecacollege.ca/~andrew.smith/ops335/labcheck_install.sh'''<br>#Assign execute permissions, and run the script to check your work:<br> '''systemctl enable iptableslabcheck_install.sh'''<ol><li value="24">disable firewalld by issuing Use the information from the '''ip address show''' command:<br>to correctly specify the '''physical network interface''' and the '''virtual network interface'''.</li></ol> '''NOTE:''' You will need an ISO file for CentOS 7 (the same one you burned your DVD from). It is recommended to use the command to download this image onto your host machine. In this way, you can keep it on your host machine for the remainder of this course in case you need it: '''systemctl disable firewalldwget http://mirror.csclub.uwaterloo.ca/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-2009.iso'''
<ol><li value="3">Note that Perform the machine will not switch over following steps to using ''iptables'' until you reboot, but you will be doing that shortly, so there is no need to do so right now.</li></ol>create your first VM on your Virtual Machine Manager application:
===Configuring # Create a Linux Gateway===At this point you have a basic Centos system installed and updated. This will serve as a host for the new virtual machines where you will do the majority of the work in this coursemachine named '''vm1'''. All # Accept the rest of our labs will assume you have this basic system running. If, for any reason, your system becomes corrupted during the semester, youdefault file type (which is '''qcow2'''ll have to redo this lab to be able to continue with the remaining uncompleted labs). You are responsible for YOUR system. If <u>NOT</u> required to specify the VM file pathname as you do not perform back-ups you have taken this risk on yourself. Poor planning on your part does not constitute an emergency for anyone elsedid in OPS235.
#You will need to install some software to allow your machine to act as a host for virtual machines. Issue the following command:
'''yum install virt-manager libvirt'''
<ol><li value="2">Start and enable the virtualization service:</li></ol>
'''systemctl start libvirtd'''
'''systemctl enable libvirtd'''
<ol><li value="3">Reboot your machine. If you do not, you will not be able to install any virtual machines.<{{Admon/li><li>Start the graphical virtual machine manager tip|VM File Types (''virt-manager'')<ul><li>You will need to enter your root password.</li></ul><li>We will be creating our own virtual network. A default virtual network has been created for you, but you will be using a <u>custom</u> one in this course.<ul type="a"><li>Right click qcow2'''localhost (QEMU)''' and select '''Detailsvs '''. Click on the img'''Virtual Networks''' tab.</li><li>Stop and delete the '''default''' network.</li><li>Run)|In OPS235, and record you selected the output of the following command:</li></ul></li></ol> VM images as a '''iptables -t nat -L'''<ol><li value="6raw">Use the '''plus sign''' to add a new virtual network using the following optionsimage.<ol type="a"><li>Name your virtual network '''ops335'''</li><li>Use the '''last two digits of your student number for the third octet of network IP address''' (for exampleIn OPS335, if your student number is 000-000-0<b>90</b>, the network address would you will be 192.168.<b>90</b>.0/24.</li><li>Ensure accepting the DHCP range will allow you to assign '''at least 3 static IP addresses outside itdefault image file '''".</li><li>Choose qcow2"'''Forwarding to physical network''' radio button, '''Destination: Any physical device''' and '''Mode: NAT'''</li><li>Ensure the network is '''started at boot'''.</li></ol></li><li>Once completed changing these settings, open a terminal and observe and record the output of the following command (noting the difference from the last time you ran itwhich stands for "QMENU Copy on Write version 2" ) that provides more features when manipulating stored VM images. We will discuss it in a few weeks):</li></ol> '''iptables -t nat -L'''}}
<ol><li value="3">Since you will be installing a Linux <u>server</u> (as opposed to a Gnome Desktop workstation), you can '''Record steps, commands, use the <u>default</u> memory and your observations in Part A in your OPS335 CPU options for use with lab log-bookcomputers'''.</li><li>Set the disk image size set to '''8GB'''<br><br>Note: Since you already setup your virtual network to OPS335, your VM will be automatically connected to your new ops335 virtual network.<br><br></li><li>Note the following installation steps when you install your created VM:</li></ol>
::* Select the correct ''location / Time Zone''.
::* For Software Selection: Accept the default '''minimum install'''. None of your VMs in this course will have a GUI since GUIs needlessly consume resources and image space. <ol><li>Click '''Installation Destination''', and then click '''Done''' to confirm that an '''automatic install''' will be performed.</li><li>Click Network & Hostname and set hostname to: '''vm1.localdomain''' and make certain the ''Ethernet connection'' is set to '''ON'''.</li><li>During installation you will be prompted to set the ''root password'' and an '''initial user account'''. For the ''initial user'', enter the same information you entered on your host machine.</li></ol>
==Part B: Virtual Machine Installation ==With the virtualization software installed and your personal network created, you are now ready to create your first virtual machine. If you have an installation DVD for Fedora you can use that, but it will be much faster to download the iso from belmont and install directly from it. '''wget http://belmont.senecacollege.ca/pub{{Admon/fedora/releases/21/Server/x86_64/iso/Fedora-Server-DVD-x86_64-21.iso''' If it has not been made available use the publicly available link: '''wget --no-check-certificate https://download.fedoraproject.org/pub/fedora/linux/releases/22/Server/x86_64/iso/Fedora-Server-DVD-x86_64-22.iso'''===Installation===#Click on the icon '''Create a new virtual machine''' to begin.#Name your machine '''f22-vm1''' and choose your installation method: '''Local install media'''. Choose the desired option to install from either the CD or iso.#Use the default memory and CPU options for use with lab computers (Depending on available hardware these settings can be adjusted). Then click on the '''Forward''' button to proceed.#Leave the disk image size set at '''8GB''' and click on the '''Forward''' button.<ol><li value="5">At the '''Ready to begin installation''' window click on '''Advanced options''' arrow to review available options.<ul><li>Select the Virtual Network named '''ops335'''. Make note of any other available options (you will need them again in the assignments).</li></ul></li></ol><ol><li value="6">Select '''Install to Hard Drive''' to begin your Fedora installation. Select the appropriate default options (You may wish to review your OPS235 notes to remind yourself what these are).</li><li>During installation you will be prompted to set the root password and an initial tip|First user account. created|For successful completion of the initial userlabs, enter please ensure the same information you entered on your host machine.</li><li>Set first user created is named using your hostname to '''vm1Seneca username.localdomain'''.</li></ol>}}
{{Admon/important|Firstboot - First user created|For successful completion of the labs, please ensure the first user created is named using your Seneca username.}}<br>
===First Boot===
#You will notice that the server installation defaults to a command-line interface. This is normal, and we will only be using this interface during this course.
#Ensure your machine has a network connection by running the command
'''host cbcssh your_seneca_id@matrix.senecacollege.ca'''<ol><li value="3">If that did not work, edit the line in the file '''/etc/sysconfig/network-scripts/ifcfg-eno1''' or '''/etc/sysconfigmake sure GlobalProtect VPN is installed on your Windows/Mac and connected. If it is, ensure your CentOS network-scripts/ifcfg-eth0''' interface is started automatically on boot.</li></ol> {{Admon/tip|Default for network config for onboot=no:should |If you've turned on your networking interface during installation - it will be '''onboot=yes''turned on by default. If you've left the network interface off during the installation - it will be off by default.}}<ol><li value="4">If you had to change that, reboot your machine.</li><li>Once you have a working connection - update your machine (this may take a while).</li></ol>
'''yum update'''
<ol><li value="65">Reboot Install the virtual machine once '''bind-utils''' package. The commands it is updatedprovides (e.g. nslookup) will be useful in troubleshooting your network connection.</li><li>If your virtual machine hangs on boot, you will need You may also want to change a graphics option:<ul><li>While install the VM is off, click on '''Viewnmap''' (from the menu at the top of the VM window), and select '''Detailstelnet'''.</li><li>From the menu on the left side, select and '''Displaynet-tools'''packages to help you troubleshoot connectivity issues.</li><li>Change the drop-down list for Type from Configure '''VNC''firewalld, iptables' to '''Spice''', and click apply.</li><li>Switch the view back to (if required) '''ConsoleSELinux''' and start the machine again.</li><li>Now run same way you did for the following commands and note the outputhost.</li><li>Issue Reboot the commands below and note in your lab logbook how they differ from the Centos installation on your hostvirtual machine once it is updated.</li></ul></li></ol> '''df -hT''' '''cat /etc/fstab''' '''cat /etc/issue''' '''uname -a'''
===Cloning a Virtual Machine===
#<ol><li> Now that you have one virtual machine working, you will create two more. If you struggled with the previous steps, repeat them to create two more virtual machines (naming them f22-vm2 and f22-vm3, with hostnames vm2.localdomain and vm3.localdomain respectively).<ol/li><li value="2">'''If you are confident with what you have done so far, you may clone your existing machine to create the others by performing the following there steps:'''</li><ulli><ol type="a"> <li>To quickly create additional VMMake certain that your '''vm1'''s virtual machine is shutdown .</li> <li>For your '''vm1''' machine, go to the details section and remove the <u>device</u> '''f22Channel qemu-vm1ga'''.</li> <li>In the virtual machine manager, '''right click''' on ''vm1'' and select '''Clone...'''.</li> <li>Set the Name to be: '''f22-vm2'''</li></ol></li><li>Once successfully created, boot the new VM and correct the host name. This can be done using the '''hostnamectl ''' command-line tool.</li><li>Record in your notes how each is donethe steps for cloning a vm.</li><li>Use the host command to check for connectivity</li><li>After creating f22-'''vm2 ''' repeat the above steps to create f22-'''vm3 ''' and correct the host namehostname ('''vm2.localdomain''' and '''vm3.localdomain''' respectively).</li></ulol{{Admon/important |Backup your VMs!|You MUST backup ALL of your VMs whenever you complete your '''OPS335 labs''' or when working on your '''OPS335 assignments''':<br>[ [https://wiki.cdot.senecacollege.ca/wiki/OPS235_Lab_2_-_CentOS7_-_HD2#Part_1:_Backing_Up_Virtual_Machines Backing up Your Virtual Machines] ]. Refer to OPS235 lab2 notes on how to backup your VMs. You should backup your VMs to a USB key in case something happens to your host machine. Note: VM files contained in the '''/var/lib/li><libvirt/ol>images''' directory have the extension in '''.qcow2''' and instead of '''.img''' (eg. for OPS235 courses prior to Fall 2016.}}  '''Record steps, commands, and your observations in INVESTIGATION 2 in your OPS335 lab log-book''' ==COMPLETING THE LAB ==Upon completion of this lab you should have 4 installed machines. One machine running Centos 7 and acting as a host and gateway for three virtual machines running minimal installations of Centos 7. Each machine must be fully updated and have access to the network (for example, to get further updates) and be able ping the others. Each machine must be using iptables for the firewall. ===Online Submission=== Follow the instructions for lab 0 on blackboard.
<!--
===Andrew's sections===
You may choose to:* Submit screenshots of your work on Blackboard, in which case you don'''Record stepst need to come to the lab.* Or come to the lab, commandsshow me your work, and your observations in Part B in your OPS335 lab log-book''talk to me about it. I want to hear what you've learned and answer any questions you have.
You'll get the same grade regardless of how you choose to submit your work.
== Completing the Lab ==[[Image:lab1_signoff.png|thumb|right|500px|Students should be prepared with '''all required commands (system information) displayed in a terminal (or multiple terminals) prior to calling the instructor for signoff'''.]]'''Arrange evidence (command output) for each Expected results of these items on your screen, then ask your instructor to review them and sign off on the this lab's completionare:'''
::<span style="color:green;font-size:1.5em;">&#x2713;</span> Host Machine installed
::<span style="color:green;font-size:1.5em;">&#x2713;</span> 3 virtual machines installed (running Fedora 22 Server)
::<span style="color:green;font-size:1.5em;">&#x2713;</span> Each machine (host and VM) has access to the network
::<span style="color:green;font-size:1.5em;">&#x2713;</span> Lab logbook completed
::<span style="color:green;font-size:1.5em;">&#x2713;</span> Run a shell script to submit your lab:<br><br> &nbsp; Steps: ::*Issue the following command to download the bash shell script:<br>'''wget http://matrix.senecac.on.ca/~peter.callaghan/files/OPS335/labcheck0labcheck_install.bashsh'''shell script on your host machine::*Run the command:<br--> '''labcheck0.bash > lab0host.txt'''::*Follow the instructions and press SEND for marking (only 1 submission permitted) 
== Exploration questions EXPLORATION QUESTIONS==
#What is the code name of your installed Fedora Linux system? How did you determine this?
#What kernel release is your host system running?
#What kernel release are your virtual machines running?
#What is the UUID (Universally Unique Identifier) of your root file system? What command was used to obtain this information?
#What is the size and type of the /boot file system on your host?
#What file was edited to change the host name on your VM's?#Explain Are there other ways to change the iptables rules displayed when you ran the command 'iptables -t nat -L'. How did they change after creating your personal network.hostname?
163
edits

Navigation menu