Changes

={{Admon/caution|THIS IS AN OLD VERSION OF THE LAB|'''This is an archived version. Do not use this in your OPS235 Lab 2 GNU/Linux Installation - Fedora 13=course.'''}}

==Objectives=Fedora 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3) =

==Reference==* [httpA '''virtual machine''' is a software simulation of a computer which can be used as though it were actual hardware. It's possible to run multiple virtual machines on one computer, reducing hardware requirements and introducing flexibility. Some common uses of virtualization include://linuxmanpages.com/ man pages]** mount** rpm** hostname** uname** ps** ifconfig** netstat** route** nslookup** wc** grub

:* Resources '''Software testing''' -- Using multiple operating systems simultaneously on the weba single computer for testing and experimentation.:** [http://fedora.redhat'''Network simulation''' -- Testing network services, protocols, and security scenarios with a small number of computers.com/docs/release-notes/ Fedora Release Notes]:** [http://docs'''Isolation''' -- Protecting multiple sets of data by storing them on multiple virtual machines.fedoraprojectIf one of the virtual machines is compromised, the data on other virtual machines is still protected.org/install-guide/ Fedora Installation Guide]:** [http://www'''Server consolidation''' -- Reducing the number of physical servers in a network by moving physical machines to virtual machines.gnuThis saves hardware, administration, cooling, and electricity costs, and it can increase the utilization of hardware (by ensuring that the hardware is not under-loaded).org/software/grub/manual/html_node/Security.html#Security Protecting Grub]:** [http://opensource.sgi.com/LDP/HOWTO/Kernel'''Load-HOWTO/grubconf.html Grub Details balancing and Sample Config]** [http://www.aspencrypt.com/crypto101_hash.html Onedisaster recovery''' --way Hash Function]** [http://www.dedoimedo.com/It is possible to migrate virtual machines between different physical machines, to ensure that a workload is balanced across multiple computers/grub.html GRUB Tutorial]** [http://www.securitystats.com/tools/password, to allow routine hardware maintenance and upgrading, and to compensate for hardware failure or other disasters.php Password Security]

{|cellpadding="8" width=Required Material="100%"|- valign="top"|

* '''In this lab, you will create three virtual machines'''. This also gives you an opportunity to experiment with different ways of installing Fedora 13 x_64 Installation DVD - You can burn . Later in this onto course you will install another operating system distribution in a DVD-R in the Open Lab* SATA Hard Disk (the same one used for Lab 1)* USB Memory Stick (minimum 64M)virtual machine.

In this labboth cases, the boot media (which you are going used to install load the installation software) and the installation source (the software that got installed) were the same: your CD/DVD provides both. However, the Fedora (GNU/and most other Linux Distributiondistributions) permits you to your hard disk from DVD.use any combination of boot media and installation media:

You need |{|border="1" cellpadding="3" width="100%"|-! Method! Boot Media! Install. Source|-! CD or DVD! &#10003;! &#10003;|-! Hard Disk! &#10003;! &#10003;|-! USB Flash Drive! &#10003;! &#10003;|-! Network (http/nfs repository)! &#10003;! &#10003;|-! PXE Network Boot! &#10003;! X|} |} == Objectives == * '''Understand Virtualization'''* '''Use KVM virtualization on Fedora'''* '''Use a number variety of installation methods:'''** Live Image Installation** Network Installation** Kickstart Installation* '''Understand the advantages and disadvantages of each type of hard installation, and be able to select the best installation method for a particular situation.'''  == Required Materials (Bring to All Labs) == * Fedora 17 LIVE CD* Fedora 17 x86_64 Installation DVD* SATA Hard Disk (in removable disk partitionstray)* USB Memory Stick* Lab Logbook  ==Prerequisites== * Completion and Instructor "Sign-off" of Lab 1: [[OPS235 Lab 1]]  ==Linux Command Online Reference==Each Link below displays online manpages for each command (via [http://linuxmanpages.com/physical volumes http://linuxmanpages.com])::* '''virsh''' (Refer to Fedora Virtualization Guide link in the "Resources on the Web" section):* [http://linuxmanpages.com/man1/gzip.1.php gzip / gunzip]  == Resources on the Web =={|cellpadding="8" width="100%"|- valign="top"| '''Virtualization''':| '''Live Image Installation:'''| '''Network Installation:'''| '''Kickstart Installation:''' |- valign="top"|[http://docs.fedoraproject.org/virtualization-guide/f13/en-US/html/ Fedora Virtualization Guide]|* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Fedora_Live_Images/ Fedora 17 Live Image Guide]* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Quick_Start_Guide/ Fedora 17 Installation Quick Start Guide]|[http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ Fedora 17 Installation Guide]* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86/ Preparing for a Network Installation]* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ch-Preparing-x86.html#s1-steps-network-installs-x86 Performing a Network Installation]|[http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ Fedora 17 Installation Guide]* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/sn-automating-installation.html Automating the Installation with Kickstart]* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ch-kickstart2.html Kickstart Installations]* [http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ch-redhat-config-kickstart.html Kickstart Configurator] |} =Performing Lab 2=== Preparation == {{Admon/tip|Performing this Lab off the Seneca network (eg. at home)|'''It is recommended to perform this lab in one of Seneca College's labs'''. This lab uses servers which are on the Seneca network and which are not available from other locations (such as your home). If you attempt this lab from another location, adjust the belmont.senecac.on.ca URLs to point to another [http://mirrors.fedoraproject.org/publiclist Fedora mirror server] -- note that you may need to change the directory name as well as the server name. The installation: of the '''fedora3''' virtual machine <u>must</u> be done at Seneca.}} # '''Open a web-browser''', and open the '''OPS235 Lab #2 WIKI'''. '''<br /dev><br /sda1 >NOTE:''' You need to enter your "MySeneca" username and password to obtain a "wired" Internet connection (300Motherwise, you will not be able to perform the "groupinstall" command in the next step). Remember to perform a "wired-connection" (logging in with your MySeneca username and password via a web-browser) every time you boot-up your host machine...<br /><br /># Install the Fedora virtualization software: <code>yum groupinstall "Virtualization"</code> or <code>pkcon install @virtualization</code> The virtualization software installed is in three parts::* '''A system service named ''libvirtd''''' that manages the VMs.:* '''Tools to manage virtualization''', including the <code>virt-manager</code> graphical tool and the <code>virsh</code> command-line tool.:* The actual '''virtual machines''' themselves.<ol> <li value="3">Start the virtualization service: <code>service libvirtd start</code></li> <li>The firewall configuration is altered by the addition of the virtualization software. Restart the firewall so that these changes become active: <code>service iptables restart</devcode></sda2 extended partitionli></ol> {{Admon/caution|Reboot your fedora host now|virt-manager may not work properly unless you reboot after installing the virtualization software.}} <ol> <li value="5">After rebooting your computer system, and logging back into your account, start the graphical tool by selecting the menu options '''Activities'''>'''Applications'''>'''System Tools'''>'''Virtual Machine Manager''' or by typing the command <code>virt-manager</code></li></devol> {{Admon/important|Run virt-manager as a regular user|Running virt-manager as root may not work due to configuration issues.}} == Investigation 1: Installing from a Live Disc == {{Admon/sda5 tip|Using an Image instead of a Live Disc|It is recommended that you perform this installation from your Fedora LIVE CD. As a matter of interest (300Mfor future reference), all created it is possible to install directly from the ISO file you used to burn your Live CD. There are many Internet tutorials that show the individual how to perform that task.}} ==== Introduction ==== In this investigation, you will install Fedora from your live disc, and observe the differences between this type of installation and the DVD installation previously performed. ==== VM Details ==== * '''Name:''' fedora1* '''Boot media:''' Fedora Live CD* '''Installation source:''' Fedora Live CD* '''Memory:''' 768MB* '''Disk space:''' 10GB* '''CPUs:''' 1 ==== Screen-Shot Thumbnail Reference ==== {{Admon/note|Virtual Machine Screen Shots Thumbnails|While performing the Virtual Machine setup, click on the thumbnails below to provide a '''"visual reference"''' while performing this section.}} {|cellpadding="8" width="100%" |[[Image:Virt-manager1.png|thumb|125px| '''Virtual Machine Manager:''' Create a New Virtual Machine]]|[[Image:Virt-manager2.png|thumb|100px|'''Step 1 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager3.png|thumb|100px|'''Step 2 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager4.png|thumb|100px|'''Step 3 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager5.png|thumb|100px|'''Step 4 of 5:''' Create a New Virtual Machine ]]|[[Image:virtual-manager6.png|thumb|100px|'''Step 5 of 5:''' Create a New Virtual Machine ]]|} ==== Steps ==== # In the Virtual Machine Manger, click on the icon to ''Create a Virtual Machine'' in Lab the upper-left corner: <br />(refer to '''Virtual Machine Manager''' thumbnail above).# A window will appear with the title ''New VM''. There are five steps to be completed; click Forward after each step:# '''Step 1 of 5:''' Enter the virtual machine (called '''fedora1''') name and select '''Local install media''' (refer to ''Step 1 of 5'' thumbnail above).# '''Step 2 of 5:''' '''Insert the CDROM or DVD containing the Fedora Live Disc image. Wait a moment for the disc to be recognized''', then select '''Use CDROM or DVD''' as the install media. Set the ''OS type'' to '''Linux''' and the ''Version'' to '''Fedora 17''' (refer to ''Step 2 of 5'' thumbnail above).<!-- {{Admon/tip|Using an ISO image|Instead of using a physical CD or DVD, you can use an ISO image of a CD or DVD. The virtualization software will make this ISO image appear like an actual CD within the virtual machine. Because hard disks are faster then optical discs, this will work faster than an actual CD/DVD.}}{{Admon/note|Choosing the operating system type and version|The purpose of the ''OS type'' and ''Version'' fields is to fine-tune some of the virtual machine settings for best performance. The VM will work even if these are set incorrectly.}} --># '''Step 3 of 5:''' Set the memory to '''768 MB''' and the number of CPUs to '''1''' (refer to ''Step 3 of 5'' thumbnail above). You # '''Step 4 of 5:''' This next step creates a disk file that will create be used to simulate the virtual machine's disk drive. Select a size of '''10 GB''' and checkmark the box labeled '''Allocate entire disk now''' (refer to ''Step 4 new physical volumes during this labof 5'' thumbnail above).# '''Step 5 of 5:''' Review the options that you have selected. '''Make a note of the storage location.''' If anything needs to be changed, use the ''Back'' button to go back and edit it; otherwise, click '''Finish''' (refer to ''Step 5 of 5'' thumbnail above).

After {{Admon/important|Removing and Recreating VMs|If for some reason the installationuser wants to remove a Virtual Machine, you will collect baseline information about your Fedora GNU/Linux systemthey can right-click the VM, do some post installation configuration and select delete in the Virtual Machine Manager. It is recommended to prepare your system for '''"delete the image file" in the remainder of remove VM dialog box when removing and then recreating a VM'''. Note: If you fail to properly remove the labsVM image file, manipulate it may affect the hard disk size for the new VM (i.e. use the GRUB configuration, and start using old smaller size. Make certain to remove that VM image file prior to recreating the systemVM.|'''}}

# Insert and secure your SATA hard disk to {{Admon/note|Fedora LIVE CD Install Screen Shots Thumbnails|While performing the removable disk slot.# Power up the computer.# Insert Fedora 17 LIVE CD install, click on the thumbnails below to provide a '''"visual reference"''' while performing this particular Fedora 13 x86_64 Installation DVD into the DVD driveinstallation.# Reboot the system.}}

{|cellpadding="8" width==Investigation 1: How do you install Fedora?==={{Admon/important | Logical Volume Management | Fedora uses a type of storage management called Logical Volume Management (LVM). In LVM, disk partitions are called Physical Volumes (PVs) and provide storage to a Volume Group (VG). This storage is then split into various Logical Volumes (LVs). The advantage to this scheme is that you can change LV size and you can add and remove PVs after installation. For example, you can add a new disk to your system and then increase the size of your existing filesystems using that extra disk space. ''Please be careful to enter all LVM information accurately, including the VG and LV names.'' We will investigate and manipulate LVM in future labs.}}"100%"

{{Admon/note | Installation Time [[Image:fedoralive1.png|thumb|100px| The installation process Virtual Machine will take about 15 minutes to complete when using DVDnow start.]]|[[Image:failedtoload.png|thumb|140px| '''Ignore and close the "Failed To Load" dialog box'''. Click Search for the Reboot button panel on the upper-left-hand side of the screen .]]|[[Image:fedoralive2.png|thumb|140px|Login to reboot the system after VM and double-click:<br /> '''Applications'''<br />>'''System Tools'''<br />>'''Install to Hard Disk'''.]]|[[Image:selectstorage1.png|thumb|100px|Select '''Specialized Storage Devices''']]|[[Image:selectstorage2.png|thumb|100px|Select '''Virtio Block Device'''.]]|[[Image:finishcdinstall.png|thumb|100px|You will get the ''Firstboot'' configuration questions during the installation is completeboot process.]]|}<ol> <li value="8">'''The virtual machine will now start'''. Select the default menu item labelled: '''Start Fedora 17'''. There The virtual machine is a post installation setup after bootrunning from the live disc at this point, and no software has been installed on the ''hard drive'' of the virtual machine.}}</li></ol>

# After booting {{Admon/note|Virtual Machine Screen Size|The virtual machine screen size will change resolution as it switches from text to graphics mode. Use the Installation DVD, at VM menu option View>Resize to VM to resize the Welcome Screen choose "Install or upgrade an existing system" window to launch show the Graphical installation program and select the following options (you can entire VM display. If this is larger than your screen size, use View>Scale Display>Always to scale the media test to verify that image so it fits on your DVD burned correctly -- It will take some time -- otherwise, skip it):#* Language - English#* Keyboard Configuration - U.Sscreen. English#* Type of devices: Basic Storage Devices}}#* There should only be one storage drive listed - select it<ol>#* If you get a warning that the drive may need to be initialized, it is because your drive is new and contains no partitition table. Select <li value="Re-Initialize10"#* Set your hostname to - f13host (one word>During the installation process, no space, all lowercase)#* Root Password: enter when prompted for a password of your own choosing. Pick one that is reallystorage device, really hard to guess to protect your system. (Recommendation: use the first letter and all the punctuation from a favorite phrase or song verse. For example, "To be or not to be, that is the question!" could become the password "Tbontb,titq!").#* Disk Partition Setup - Specify a Custom Layoutselect '''Specialized Storage Devices''', and then set up select the installation with this configuration:#** Find your existing 300MB partition (/dev/sda1). Edit this entry so that the mountpoint is /boot and is formatted as an ext3 filesystem.#** Don't touch the other existing 300M partition (/dev/sda5).#** Create 4 new LVM Physical Volumes that are 25000 MB in size. Set the File System Type to Physical Volume (LVM)''Virtio Block Device''' option. Should be /dev/sda6 to /dev</sda9.li>#** Create an LVM Volume Group. Set <li>When prompted for the Volume Group Name to hostname, enter '''vg_mainfedora1''' , and set when prompted for the Physical Extent size to timezone, select '''4MBToronto - Eastern Time Ontario'''.#** Click on the Add button (within the "Make LVM Volume Group" window) to create a logical volume within that volume group:#*** Mount point / (root), filesystem type ext4and when asked about storage, logical volume name select '''rootUse All Space''', size 90GB (90000MB).#* Say yes to continue without a swap partition.#* Say yes to format /dev/sda1.#* Accept Boot Loader defaults.#* Accept Graphical Desktop and repository defaults.# Proceed with the installation. '''Note how long it takes to perform Use the installationdefault values for all other fields.'''# Reboot using Notice that the controls on the screen. When the system starts, it will installer does not ask you some final configuration questions.#* Check what software should be installed; compare the License Agreement. What license is used for installation time to the Fedora distribution? What activities amount of time it took to do have restrictions and obligations?#* Create a user account for yourself using the same name as your learn accountLab 2 installation.#* Set date and time. Normally, you would want to enable Network Time Protocol, but since we will be experimenting with Record this information in the networking turned off '''table contained in later labs, leave it disabledInvestigation 4'''.</li>#* Click <li>When the installation is complete, click on Do Not Send Hardware Profile.#* Finish the post'''reboot''' button at the bottom right-installation customization, wait for hand corner of the login screen to appear, and then login to your Learn account.</li></ol>

Answer <ol> <li value="13">Start the Investigation 1 question in VM from its disk image. This can be done graphically by selecting the Virual machine name, and then clicking on the '''Open''' button, and then click the '''play''' button when the next screen appears (or by selecting Virtual Machine>Run from the virtual machine menu). You will get the ''Firstboot'' configuration questions during the boot process (asking you to create a user, set the date and time, and optionally send the hardware profile to the Fedora Project). Create a user with the same name as your lab log bookMatrix account.</li> <li>Login using the new user account.</li></ol>

{{Admon/tipnote|Forcing the Resolution on Network / Service Considerations|Please perform the Projector|The podium computers tasks below in the lab rooms are connected order allow these Fedora systems to a video splitter. This splitter then connects be able to both the LCD screen on the podium and the projector at the front of the roomcommunicate with each other. However, the splitter prevents the computer from successfully querying the LCD or screen '''Failure to find the supported resolutions, and Fedora therefore selects a very low (safe) resolution. If you are using a podium system, you properly perform these operations can force the native 1680x1050 resolution of the LCD display using [http://matrix.senecac.on.ca/~chris.tyler/fedora-scripts/1680x1050 this script]cause problems in future labs'''.|}}

<ol> <li value===Investigation 2"15">Enable SSH access to your virtual machine with these commands (semi-colon allows commands to be run in sequence):<br /> <code>service sshd start; chkconfig sshd on</code></li> <li>Find out the IP address of your virtual machine: How many files packages and files are installed <code>ifconfig eth0</code> </li> <li>Enter the following command on your virtual machine to create a firewall exception to allow ssh traffic into the machine:<br /> <code>iptables -I INPUT -p tcp -s0/0 -d0/0 --dport 22 -j ACCEPT</code></li> <li>Confirm that you can ssh to your virtual machine from the system?===host (your main Fedora installation): <code>ssh ''IPaddress''</code></li></ol>

For the rest of the tasks in this lab, you must login {{Admon/tip|Switch to your system using your Learn account and execute all commands under your learn account. Virtual Machine Manager Window|If you get are currently in a Permission Denied message when trying Virtual machine, but want to execute a command, then switch to the superuser account by running the command su - and type in the password for "root". Once the intended command is executedVirtual Machine Manager Window, type "exit" to exit from simply click '''Activities'''> '''Select the superuser account and return to your regular Learn accountVirtual Machine manager window'''.}}

Record '''Answer the commands used and the output generated Investigation 1 observations / questions in each of the following steps:your lab log book.'''

# To find all the mount points, enter the command: <code>mount</code>#* Study the output and record all the mount points in your log book.# The name of the installation log file is <code>/root/install.log</code> -- It is an ASCII file (how can you be sure?) and can be viewed with the <code>less</code> command. # You can make use of this file to determine how many packages have been installed: complete the following command to count the number of packages listed in the installation log file:#* <code>grep ________________ /root/install.log | wc -l</code># Using the <code>rpm</code> command: you can also use the following commands to list all the installed packages, and the total number of packages installed== Investigation 2:#* <code>rpm -q -a</code>#* <code>rpm -q -a | wc -l</code>#* <code>rpm -qa | wc -l</code># The <code>-q</code> option means query, and the <code>-a</code> option means all (in other words, query all installed software packages). Did you get the same number of packages from the above two methods?# Some of the files on your system were installed with the software packages, and some were created by system activity (for example, by creating your Learn account and by logging in). If you know the package name (from the <code>install.log</code>), you can list all the files that were installed Installing from the package by using the following command:#* <code>rpm -q -l package_name</code># This combines the <code>-q</code> (query) option with the <code>-l</code> (list filenames) option.# You can pipe the outupt through <code>wc -l</code> to count the number of lines:#* <code>rpm -ql package_name| wc -l</code># Using what you learned in steps 3 and 4, get a count of the total number of files installed by all of the software packages on your system.# To find out the name that you have assigned to your Linux system, enter the command: <code>hostname</code># To find out the kernel version of your GNU/Linux workstation and the date it was created, enter the command: <code>uname -r</code># To find out all the system processes running on your GNU/Linux workstation, enter the command: <code>ps -ef</code># To capture the list of all the system processes to a file called <code>ps.lst</code>, enter the command: <code>ps -ef > ps.lst''</code># Copy the installation log file <code>/root/install.log</code> and the file ps.lst to a USB memory key, or scp to your matrix account as a backup.Network ==

{{Admon/tip |Updating FedoraAuthenticate to the network|The Fedora 13 software is updated frequently rest of this lab uses network access.''' Be sure to add features, fix bugs, and upgrade security. Perform a system update authenticate to get the latest versions of the packages installed in Fedora: Start the Firefox web network using your browser, turn off popup window blocking (select before proceeding''Edit>Preferences'', then select the Content tab and uncheck the box to Block Popups), then login to SeneNET. Open a terminal and type <code>su</code> to start a shell as root. Enter the command <code>yum update</code> This will download and install all of the packages that have been updated since the installation DVD image was created. If you complete this command at Seneca it should run quite fast as Seneca College hosts a Fedora Repository mirror (a copy of all of the current fedora packages, on a local web server).}}

=== Investigation 3: What is a runlevel? Introduction ===

After It is possible to install Fedora entirely from the kernel bootsnetwork. In this investigation, it starts a single program, called <code>init</code>. A running instance of a program is called you will install Fedora from a webserver on Seneca'''process''' -- the init process always has a process ID (PID) of 1. All other processes on the system are started by init, or they are started by processes started by inits LAN.

These systems employ the concept of "runlevels" -- groups of software that can be selected, so that the system can be run in various modes* '''Name:''' fedora2* '''Boot media:''' Network installation* '''Installation source:''' http://belmont.senecac.on. In ca/fedora/releases/17/Fedora systems, these runlevels are used/x86_64/os/* '''Memory:''' 1024MB* '''Disk space:''' 20GB* '''CPUs:''' 1

==== Steps ====# Create the VM (called '''fedora2''') as you did with the ''fedora1'' virtual machine, except:#* In '''step 1 of 5''', set the installation type to '''Network Install (HTTP, FTP, or NFS)'''.#* In '''step 2 of 5''', provide the location of the software source by providing the URL http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/#* In '''step 2 of 5''', set the ''OS Type'' to '''Linux''' and ''Version'' to '''Fedora 17'''. # Observe the boot process. How is it different from booting from an optical disc (CD/DVD)?# Start the installation process (make certain to use information in the ''VM Details'' section above).# When you get to the disk partitioning step, select '''Use All Space''' and enable the checkbox labelled '''Review and modify partition layout'''.If an dialog box displays a permissions problem, then click yes to proceed. On the next screen, change the logical volumes as follows:#* Reduce the size of the root LV to '''8000 MB'''.#* '''Add a logical volume with a size of 2000 MB and a mountpoint of /home''' (you can name it whatever you want, and use '''ext4''' as the file-system type).# On the software selection screen, select '''Graphical Desktop'''.# '''On the same screen, select the "Fedora 17 - x86_64" and the "Fedora 17 - x86_64 - Updates". Leave "Installation Repo" selected. ''DO NOT'' enable the "Test Updates" repository'''.# Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations.Record this information in the '''table contained in Investigation 4'''. '''Answer the Investigation 2 observations / questions in your lab log book.''' == Investigation 3: Installing from the Network using Kickstart == === Introduction === When Fedora is installed using the techniques you have used so far, the user is asked a number of questions. In some situations, it is better to provide the answers to these questions in a file rather than answer them individually. This type of file is called a ''kickstart'' file. In this investigation, a kickstart file is provided for you. You can also create or modify a kickstart file using a regular text editor or a graphical tool. ==== VM details ==== * '''Name:''' fedora3* '''Boot media:''' Network installation* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/17/Fedora/x86_64/os/* '''Kickstart location:''' http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora17-kickstart.cfg* '''Memory:''' 1024MB* '''Disk space:''' 15GB* '''CPUs:''' 1 ==== Steps ====# Create the VM as you did with the ''fedora2'' virtual machine, specifying a network install as before, except:#* In step 2 of 5, after entering the URL for the installation source, click on the '''URL Options''' control.#* Enter the Kickstart URL: http://www.drivehq.com/file/df.aspx/shareID10606286/fileID1269952040/Fedora17-kickstart.cfg # Observe the installation. How is it different from booting from an optical disc (CD/DVD)?# Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations. # What happens when the installation is finished?# '''Take a look at the kickstart file (using the URL you entered) to <u>determine</u> the root password as well as the name and password for the first user account'''.# Boot the virtual machine and log in (use the user ID and password information from the previous step). Compare the experience to the first time you booted the other virtual machines.Record this information in the '''table contained in Investigation 4'''. '''Answer the Investigation 3 observations / questions in your lab log book.''' == Investigation 4: Updating and Comparing the VMs == # In each VM, run this command: <code>yum update</code># Record the answers to these questions in your log book:#* How long did it take to run on each VM? How many packages were updated?#* Why does it take longer in some VMs than others? Complete the following table (and transfer into your lab2 log-book notes): {|classborder="1" width="mediawiki100%" bordercellpadding="15"!Runlevel!Description

! |0|Halt (powers off the system)f17host||fedora1||fedora2||fedora3

|1'''Installation Method'''|Single-user maintenance mode, network not running, character-mode display|Installation Disc||Live Disc||Network Installation||Network Installation + Kickstart

|2|''Not normally used - originally meant: Multi-user mode, network not running, character-mode display'Packages Installed'''|| || || ||

|3'''Updates Installed immediately after installation'''|| || || ||Multi-user mode, network running, character-mode display

|4|''Not normally used'Software could be selected during installation'''|| || || ||

|5'''Disk layout could be selected during installation'''|| || || ||Multi-user mode, network running, graphical user interface

|6'''No questions asked during installation'''|| || || |||-|'''Total installation time''' (after installation questions)|| || || |||-|'''Amount of disk space used'''|| || || |||-|'''Questions asked during first boot'''|| || || |||-|'''Advantages of this type of installation'''|| || || |||Reboot-|'''Disadvantages of this type of installation'''|| || || |||-|'''This type of installation is recommended for...'''|| || || ||

{{Admon/note|Different runlevel systems|Various Linux distributions may use the runlevel numbers differently. For example, on some Debian/Ubuntu systems, the default (standard) runlevel is 2.}} In order to implement runlevels, init uses a configuration file and a number of script files== Investigation 5: * <code>/etc/inittab</code> is the configuration file, which sets Managing Virtual Machines from the default runlevel.* <code>/etc/rc.d/init.d</code> is a directory of scripts.Command Line ==

In order {{Admon/note|Manage virtual machines from the host|The commands used to determine which of the startup scripts should manage virtual machines must be executed in each runlevel, on the one directory per runlevel is created host (<code>/etc/rc.d/rc'''X'''.d</code>, where '''X''' is the runlevelyour disk pack)and not inside a virtual machine. This directory is filled with symbolic links to the startup scripts in <code>/etc/rc.d/init.d</code>}}

# To find out Start the value of ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.# Switch to the runlevel f19host machine, and open a shell terminal.# Enter these commands into your GNU/Linux system goes into after boot, enter f19host machine and note the commandresult: #* <code>grep initdefault /etc/inittab'''virsh list'''</code># You should get a single line containing ":" as the field delimiter. The second field stores the value of the runlevel the init process will use after a reboot. Record the output in your log book.# A list of processes that should be running at a given runlevel can be found in the directory * <code>/etc/rc.d/rc'''Xvirsh list --all'''.d</code> where #* <code>'''Xvirsh list --inactive''' is the runlevel. Do a directory listing of that directory </code># Now, shut-down your fedora1 VM normally, and study what files are in there. Pay attention to close the first three characters of each file namefedora1 VM window. They have special meaning Make certain NOT to close the system. Record your observation in your log bookVirtual Machine Manager main window.# Make a backup of the file /etc/inittab with Switch to your terminal and issue the command: <code>cp /etc/inittab /etc/inittab.original'''virsh start fedora1'''</code># Edit Check to see if your fedora1 VM is now running.# Switch to the file terminal and issue<code>/etc/inittab'''virsh list --all'''</code> and change confirm the default runlevel to 3. Save status of the change and reboot your systemfedora1 VM.# After the rebootThere are other commands that can be used (such as suspend, you should get or shutdown). The "shutdown" command may not always work since it sends a request to "Text Login Screenshutdown virtual machine gracefully", but may not always work. Login with your Learn account and type startx at the command prompt. Describe what happens in your log book.# Enter the command: <code>runlevel</code> -- this shows the previous and current runlevel. Record the values in your book.Why do you think it is useful to have commands to manipulate VMs?

=== '''Answer the Investigation 4: What is the network configuration? ===5 observations / questions in your lab log book.'''

# To check the network configuration settings obtained from the DHCP server, run the following commands, describing the output in your log book== Investigation 6:#* ifconfig#* route#* netstat -rn#* nslookup (at the > prompt, enter the word "server" (How do not type the quotes) and record the output. Type exit to leave nslookup).# Find the following information in the output of the above commands:#* MAC address (physical or hardware address) of the ethernet network interface#* The IP address (logical address) assigned by the DHCP server#* The default route (gateway)#* The DNS nameserverI backup a virtual machine? ==

Answer {{Admon/important|Backing up VMs|There are two general processes in order to back up your images:<ol><li>'''Compressing your images''' (also recommended to backup up to external storage USB Key) using the Investigation 4 question'''gzip''' command.</li><li>'''Backup the VM xlm configuration file''' (preferably to USB key) using '''virsh''' shell command to add VM to virtual machine manager list (in the event that the HOST machine is "wiped" and re-installed, but VM images and xml configuration files have been backed up external storage).</li></ol><br />Taking the time to backup the image of the Operating System's file system allows the user to return to a '''"restoration point"''' using the '''gunzip''' command in case something bad occurs to the OS during a lab.<br />Failure to take the time to make and confirm backups can result in loss of lab work for the student!|}}

# Shut down all of the virtual machines.# Change to the directory <code>/var/lib/libvirt/images/</code>. Note the size of the files in this directory. What do these files contain?# Make a compressed backup of the <code>fedora3.img</code> file to your home directory with this command: <code>'''gzip < fedora3.img > ~YourUserId/fedora3.img.backup.gz'''</code><br />('''Note: Make certain to use the redirection signs "<" and ">" properly in the command!'''){{Admon/caution| Make sure the backup is successful!|If there are any error messages, '''DO NOT''' proceed past this point. You're going to destroy your fedora3 virtual machine and restore it using the backup you have created -- if there are any problems with the backup, you will not have a working virtual machine, and will have to re-install it.}}<ol> <li value="4">Compare the size of the compressed and original files.</li> <li>Start the '''''fedora3''''' VM.</li> <li>'''Make certain that you are in your fedora VM and <u>not</u> in your Fedora main system!'''</li> <li>Wreck <u>only</u> your fedora 3 system! Try this command inside the fedora3 virtual machine: <code>'''rm -rf /*'''</code></li> <li>Shut down the VM. If you tried to start the Fedora3 VM, it would not boot since all system files have been removed!</li> <li>Restore the original image from the backup in your home directory by typing this command: <code>'''gunzip < ~YourUserId/fedora3.img.backup.gz > fedora3.img'''</code></li> <li>Restart the VM. Is it working normally?</li> <li>Create compressed backups of your other virtual machines.</li></ol><ol><li value="12">You should make a copy of the xml configuration file in case you "wipe" and re-install the host machine, and want to add a restored VM backups to the virtual machine manager list. We will demonstrate using the fedora 3 xml configuration file, and prove that a "clone" can be added to your list.Please perform the following step:<ol type= Investigation 5"a"><li>Verify that you are in the directory: How do You Secure <code>/var/lib/libvirt/images/</code>.</li> <li>Execute the following command: <code>virsh dumpxml fedora3 >fedora3.xml</code></li> <li>Examine the Grub Boot Loaderfile <code>fedora3.xml</code>. What does it contain? What format is it in?</li> <li>Make a copy of <code>fedora3.xml</code> called <code>fedora3a.xml</code>.</li> <li>Edit the file <code>fedora3a.xml</code>, making the following changes:</li></ol>::* Change the name (in the file, not the file name) to <code>fedora3a</code>::* Change at least one of the hexadecimal characters in the UUID. Do not change the length of the UUID. Valid hexadecimal characters are 0-9 and a-f.<ol type="a" > <li value=="6">Issue this command: <code>virsh define fedora3a.xml</code> <li>Issue the command <code>virsh list --all</code> and record any changes. <li>Issue the command: <code>virsh undefine fedora3a</code> <li>List all of the virtual machines again, and note any changes. </li></ol> <li>For the remainder of these labs, it is assumed that you will backup <u>'''both'''</u> the images and xml configuration files for <u>'''all'''</u> Virtual machines, when asked to backup your virtual machines. It is also highly recommended to backup these files to an external storage device (eg. USB key) in case the host machine gets "wiped" and you need to rebuild your HOST machine and then restore your Virtual Machines...</li><li>Answer this question in your log book:</li></ol>::* In order to fully back up a virtual machine, what information should be saved in addition to the virtual machine image?

{{Admon/cautionimportant|Duplicate UUIDsBacking up VMs|Before proceeding, use the <code>mount</code> command It is essential to check to see which filesystem is mounted on back up your VMs at the mount point <code>/boot</code>. If it is <code>/dev/sda5</code>end of each lab, it is so you can easily restore them if something goes wrong in the wrong filesystemnext lab. This may be caused by a duplication of serial numbers which is the result of Lab 1; you can fix this problem with this series of commands: mkdir /media/sda5 /tmp/sda5-files umount /dev/sda5 mount /dev/sda5 /media/sda5 cp -v -R /media/sda5/* /tmp/sda5-files umount /dev/sda5 mkfs -t ext3 /dev/sda5 mount /dev/sda5 /media/sda5 cp -v -R /tmp/sda5-files/* /media/sda5 rm -rf /tmp/sda5-files mount -a}}

By default, the Grub boot loader allows anyone with access to the computer at boot time to set the runlevel, or change {{Admon/tip|Shutting Down the boot parametersHost while Virtual Machines are Running|If you shut down your host system while virtual machines are running, which can allow them to influence the init process and which kernel image is loaded. Anyone with access to the boot prompt can therefore bypass security controls and control which software is loaded. For example, rebooting to runlevel 1, known as single user mode, gives the user root priveleges without the need for a password! Obviously, giving a non-administrator this much control can they will be dangeroussuspended, and it is wise to protect will resume the next time you boot loader with a secure passwordyour host system. }}

We will need to choose a password, encrypt with '''Answer the grub programs hash utility (called md5crypt), and add the encrypted hash of Investigation 6 observations / questions in your password to the grub configuration file, /etc/grublab log book.conf'''

# Choose a suitable password. # Open the grub program by typing the command: <code>grub<{{Admon/code># At the grub prompttip|SSHD and Firewall|If you have restarted your virtual machine ''fedora1'', type in the command: <code>md5crypt</code># When prompted for a password, carefully type sshd server you started in your password. The program investigation 1 (step 15) will display the encrypted hash of your passwordno longer be running. Carefully write down In addition, the encrypted has.# Type the command: <code>quit</code> firewall will have reverted to exit the grub program.# Open the grub configuration file, <code>/etc/grubits original state.conf</code> for editing. (This file is actually linked In order to /boot/grub/grub.conf).# Carefully add the line: <code>password --md5 ''password-hashuse ''</code> (note: 'scp'password-hash'' is the hash , below, you generated with md5crypt) Place this line between the splashimage line and the title line. If there are other lines there, there is no will need to remove them. Just insert your password line as a new line.# Make sure you have not made a mistake. What you type in must match exactly the output from restart ssh and adjust the md5crypt commandfirewall again.# While you are editing the file you should also increase the timeout for grub to automatically boot the default OS. Edit the line <code>timeout=0<br /code> to <code>timeout=5<br /code> to give us more time to interrupt If students cannot backup their kickstart files using the process.# You should also ensure that the grub boot menu is not hidden. Add '''scp''' command, they can use a hash sign web-browser to access their Seneca e-mail with attachment (<code>#</code>copy kickstart file to their home directory first!) to the start of the line which reads: <code>hiddenmenu</code># Save the file and exit. Your Grub boot loader is now password protected.# Find For the section of [http://www.linux.com/archive/feature/53569 this article] that explains how to change the runlevel at boot time, and read it. Reboot your text-based Linux system"fedora3", trying students can use the '''mail''' command (refer to change the man command to runlevel 1 from the boot prompt, and see if the password protection worked.# From now on, when you want learn how to change boot parameters when you boot, you must type lowercase <code>p</code> at the boot prompt and enter the required passwordsend e-mail attachments).}}

== Completing When you perform a non-Kickstart installation, the Lab ==installation program creates a Kickstart file in the <code>/root</code> directory for reference.

Check off # Obtain the following items before asking kickstart files for all four of your instructor installations (your disk pack ''f17host'', plus the ''fedora1'', ''fedora2'', and ''fedora3'' virtual machines).# To prevent confusion, copy your kickstart files to kickstart filenames that describe their purpose (eg. kickstart_host, kickstart_fedora1, kickstart_fedora2, etc...)# Copy them all to check your labf17host system (tip:use <code>scp</code>), or use the hint in the tip box above to send via e-mail.# Compare these files. What are the differences? Similarities? (Tip: you may want to use tools such as <code>sdiff</code> to help with the comparison).# How could you use the kickstart file produced by the installation program to perform additional, identical installations?

* Task 1 - Install GNU'''Answer the Investigation 7 observations /Linux Workstation using Fedora * Task 2 - Collect system information after installationquestions in your lab log book.* Task 3 - Customize and configure boot time environment* Task 4 - Collect network information* Task 5 - Password protect Grub Bootloader'''

Arrange evidence for each of these items on your screen, then ask your instructor to review them and sign off on = Completing the lab's completion:Lab =

* Grub is password protected.* Can login with your "learn" account name* Has all the mount points* Has the package count* Has edited the default runlevel* Has the correct IP address and MAC address* Find out the default route (gateway)* IP of the DNS name server* '''Name Arrange evidence for each of these items on your screen, then ask your instructor to review them and contact information sign off on your disk packthe lab's completion:'''

# How many packages were installed?# How many files (correct to the nearest hundred) were installed?# How many mount points were used?# How many users were created automatically on your system (do not count your learn account)?# What is your learn account's UID and GID?# What is your learn account's home directory?# What is the home directory = Preparing for the user "root"?# How do you determine the host name of your GNU/Linux workstation?# What command can display the NIC's MAC address?# Which file contains the default "runlevel" value for your GNU/Linux workstation?Quizzes =

{{Admon/important|Unbind # What is the name of the Fedora installation program?# Which factors recorded in your MAC address|Before moving your disk pack table (above) were due to the type of installation performed, and which factors were due to another systemthe amount of software installed?# 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?# What factors affect installation time?# How can you reduce the number of software updates required immediately after installation?# Why would you enable additional repositories during installation?# What does the file <code>/root/anaconda-ks.cfg</code> contain, [[Unbinding MAC Addresses on Fedora|unbind and how is it created?# How do you start and stop virtual machines?# How do you SSH into your MAC address]]virtual machines?# What is the purpose of and relationship between these pieces of software?#* libvirt#* libvirtd#* virsh#* virt-manager#* virt-install#* kvm# The kickstart installation (fedora3) was a network installation. Can a kickstart file be used with a DVD installation?# The kickstart installation (fedora3) was fairly fast.}}Why? Under what circumstances would it take a long time, even on a fast network?# What other types of installation sources are possible (besides Live Disc, Installation Disc, and Network?)