[[Category:OPS235]][[Category:OPS235 Labs]]
={{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 12=course.'''}}
==Objectives=Fedora 17 Installation Methods (on Virtual Machines: fedora1, fedora2, fedora3) =
#To perform a GNU/Linux installation using the Fedora 12 distribution#To perform boot time customization and configuration#To obtain network configuration from a DHCP server#To secure the boot loader by adding password protection#To investigate GRUB boot loader configuration== Introduction ==
==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 12 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.
==Prerequisite==
* Completion of Lab 1You should already have both a '''Fedora installation DVD''' and a '''Fedora LIVE CD'''.
==Introduction==
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 a number of hard disk partitions/physical volumes for this installation: the /dev/sda1 |{|border="1" cellpadding="3" width="100%"|-! Method! Boot Media! Install. Source|-! CD or DVD! ✓! ✓|-! Hard Disk! ✓! ✓|-! USB Flash Drive! ✓! ✓|-! Network (300M), the /dev/sda2 extended partition, the /devhttp/sda5 (300Mnfs repository), all created in Lab 1, and 4 new physical volumes which you will create during this lab.! ✓! ✓|-! PXE Network Boot! ✓! X|} |} == Objectives ==
After the installation, you will collect baseline information about your * '''Understand Virtualization'''* '''Use KVM virtualization on Fedora GNU/Linux system, do some post '''* '''Use a variety of installation configuration to prepare your system for methods:'''** Live Image Installation** Network Installation** Kickstart Installation* '''Understand the remainder advantages and disadvantages of each type of the labs, manipulate the GRUB configurationinstallation, and start using be able to select the systembest installation method for a particular situation.'''
==Instructions==
# Insert and secure your SATA hard disk == Required Materials (Bring to the removable disk slot.# Power up the computer.# Insert the Fedora 12 x_64 Installation DVD into the DVD drive.# Reboot the system.All Labs) ==
===Investigation 1: How do you install * Fedora?===17 LIVE CD{{Admon/note | Please take note! | * Fedora uses a type of partition management called Logical Volume Management 17 x86_64 Installation DVD* SATA Hard Disk (LVM). In LVM, in removable disk partitions are called Physical Volumes (PVstray) 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.* USB Memory Stick* Lab Logbook
Please be careful to enter all LVM information accurately, including the VG and LV names. We will investigate and manipulate LVM in future labs.}}
At the Welcome Screen choose "Install or upgrade an existing system" to launch the Graphical installation program and select the following options (you can use the media test to verify that your DVD burned correctly; --It will take some time-- otherwise, skip it):==Prerequisites==
# Language - English# Keyboard Configuration - U.S. English# Set your hostname to - f12host (one word, no space, all lowercase)# Set your timezone to - America/Toronto * Completion and check that your system time is correct# Root Password: enter a password of your own choosing. Pick one that is really, 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, Instructor "To be or not to be, that is the question!" could become the password Sign-off"Tbontb,titq!").# Disk Partition Setup - Specify a Custom Layout, and then set up 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 partitions that are 20% of the remaining space on your disk (minimum 15000 MB) in size. Set the File System Type to Physical Volume (LVM). Should be /dev/sda6 to /dev/sda9.#* Use the LVM button to create a Volume Group. Set the Volume Group Name to '''vg_main''' and set the Physical Extent size to '''4MB'''.#* Click on the Add button to create a logical volume within that volume groupLab 1:#** Mount point / (root), filesystem type ext4, logical volume name root, size 50GB (50000MB).# Say yes to continue without a swap partition.# Say yes to format /dev/sda1.# Accept Boot Loader defaults.# Accept Office and Productivity and repository defaults.[[OPS235 Lab 1]]
{{Admon/note | Please take note! | The installation process will take about 15 minutes to complete on the P4 CPU system when using DVD. Click the Reboot button on the screen to reboot the system after the installation is complete. There is a post installation setup after boot.}}
# Reboot==Linux Command Online Reference==# Check the License AgreementEach Link below displays online manpages for each command (via [http://linuxmanpages. What license is used for the Fedora distribution? What activities do have restrictions and obligations?# Create a user account for yourself using the same name as your learn accountcom/ http://linuxmanpages.com]):# Set date and time. Normally, you would want :* '''virsh''' (Refer to enable Network Time Protocol, but since we will be experimenting with Fedora Virtualization Guide link in the networking turned off in later labs, leave it disabled"Resources on the Web" section):* [http://linuxmanpages.# Click on Do Not Send Hardware Profilecom/man1/gzip.# Finish the post-installation customization, wait for the login screen to appear, and then login to your Learn account1.php gzip / gunzip]
Answer the Investigation 1 question in your lab log book.
== Resources on the Web ==
{|cellpadding="8" width="100%"
|- valign="top"
| '''Virtualization''':
| '''Live Image Installation:'''
| '''Network Installation:'''
| '''Kickstart Installation:'''
|- valign===Investigation 2"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: How many files packages and files are installed on //docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/sn-automating-installation.html Automating the system?===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]
For the rest of the tasks in this lab, you must login to your system using your Learn account and execute all commands under your learn account. If you get a Permission Denied message when trying 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 executed, type "exit" to exit from the superuser account and return to your regular Learn account.|}
Record the commands used and the output generated in each of the following steps:=Performing Lab 2=== Preparation ==
# To find all {{Admon/tip|Performing this Lab off the mount points, enter the command: ''mount''#* Study the output and record all the mount points in your log bookSeneca network (eg.# The name of the installation log file is at home)|''/root/install.log'' -- It is an ASCII file (how can you be sure?) and can be viewed with the ''less'' command. # You can make use of recommended to perform this file to determine how many packages have been installed: complete the following command to count the number of packages listed lab in the installation log file:#* ''grep ________________ /root/install.log | wc -l''# Using the ''rpm'' command: you can also use the following commands to list all the installed packages, and the total number one of packages installed:#* Seneca College''rpm -q -a''#* s labs''rpm -q -a | wc -l''#* ''rpm -qa | wc -l'' # The -q option means query, and the -a 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 This lab uses servers which are on your system were installed with the software packages, Seneca network and some were created by system activity which are not available from other locations (for example, by creating such as your Learn account and by logging inhome). If you know the package name (attempt this lab from another location, adjust the installbelmont.senecac.log), you can list all the files that were installed from the package by using the following command:#* ''rpm -q -l package_name''# This combines the -q (query) option with the -l (list filenames) optionon.# You can pipe the outupt through wc -l ca URLs to point to count the number of linesanother [http:#* ''rpm //mirrors.fedoraproject.org/publiclist Fedora mirror server] -ql package_name| wc -l''# 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 note that you have assigned may need to your Linux system, enter change the command: ''hostname''# To find out directory name as well as the kernel version of your GNU/Linux workstation and the date it was created, enter the command: ''uname -r''# To find out all the system processes running on your GNU/Linux workstation, enter the command: ''ps -ef''# To capture the list server name. The installation of all the system processes to a file called ''ps.lst'fedora3', enter the command: ''ps -ef virtual machine <u> ps.lst''# Copy the installation log file must</root/install.log and the file ps.lst to a USB memory key, or scp to your matrix account as a backupu> be done at Seneca.}}
{{Admon/tip |Updating Fedora| You need to complete # '''Open a system update. Start the Firefox web -browser''', turn off popup window blocking (select and open the '''OPS235 Lab #2 WIKI'''. '''Edit<br />Preferences<br />NOTE:''' You need to enter your "MySeneca" username and password to obtain a "wired" Internet connection (otherwise, then select you will not be able to perform the Content tab and uncheck "groupinstall" command in the box to Block Popupsnext step), then login . Remember to SeneNET. Open perform a terminal "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>su -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 start a shell as root. Enter manage virtualization''', including the command <code>yum updatevirt-manager</code> This will download graphical tool and install all of the packages that have been updated since <code>virsh</code> command-line tool.:* The actual '''virtual machines''' themselves.<ol> <li value="3">Start the installation DVD image was created. virtualization service: <code>service libvirtd start</code></li> If you complete this command at Seneca it should run quite fast as Seneca College hosts a Fedora Repository mirror<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</code></li></ol>
<!-- {{Admon/tip caution|SELinuxReboot your fedora host now| The final task is to turn off SELinux. SELinux is a Linux feature that provides a variety of security policies, including U.S. Department of Defense style mandatory access controls, through the use of Linux Security Modules in the Linux kernel. While it is certainly something virt-manager may not work properly unless you would leave on in a real world environment, it is beyond reboot after installing the scope of this course and does interfere with some of our activities. To disable SELinux, click on '''System => Administration => SELinux Management'''. Set the "System Default Enforcing Mode" to Disabled. Quit and reboot your systemvirtualization software.}} -->
<ol> <li value=== Investigation 3: What is a runlevel? ==="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></ol>
After the kernel boots, it starts a single program, called <code>init<{{Admon/code>. A running instance of important|Run virt-manager as a program is called a '''process''' regular user|Running virt-- 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 initmanager as root may not work due to configuration issues.}}
Most current Linux systems use some variation of the init system originally developed for Unix System V (called "sysvinit") or == Investigation 1: Installing from a newer version called "upstart".Live Disc ==
These systems employ the concept {{Admon/tip|Using an Image instead of "runlevels" -- groups a Live Disc|It is recommended that you perform this installation from your Fedora LIVE CD. As a matter of software that can be selectedinterest (for future reference), so 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 system can be run in various modesindividual how to perform that task. In Fedora systems, these runlevels are used:}}
{|class="mediawiki" border="1"!Runlevel!Description|-|0|Halt (powers off the system)|-|1|Single-user maintenance mode== Introduction ====|-|3|Network runningIn this investigation, character-mode display only|-|5|Network runningyou will install Fedora from your live disc, graphical user interfaceand observe the differences between this type of installation and the DVD installation previously performed.|-|6|Reboot|}==== VM Details ====
{{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.}}* '''Name:''' fedora1* '''Boot media:''' Fedora Live CD* '''Installation source:''' Fedora Live CD* '''Memory:''' 768MB* '''Disk space:''' 10GB* '''CPUs:''' 1
In order to implement runlevels, init uses a configuration file and a number of script files:==== Screen-Shot Thumbnail Reference ====
* <code>{{Admon/etc/inittab</code> is note|Virtual Machine Screen Shots Thumbnails|While performing the configuration fileVirtual Machine setup, which sets click on the default runlevelthumbnails below to provide a '''"visual reference"''' while performing this section.* <code>/etc/rc.d/init.d</code> is a directory of scripts.}}
In order to determine which of the startup scripts should be executed in each runlevel, the directory{|cellpadding="8" width="100%"
** Note not all distributions use the same runlevel configurations|[[Image:Virt-manager1. Debian and Ubuntu based distropng|thumb|125px| 's are different''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 ]]|}
# To find out the value of the runlevel your GNU/Linux system goes into after boot, enter the command: <code>grep initdefault /etc/inittab</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'''X'''.d</code> where '''X''' is the runlevel. Do a directory listing of that directory and study what files are in there. Pay attention to the first three characters of each file name. They have special meaning to the system. Record your observation in your log book.# Make a backup of the file /etc/inittab with the command: <code>cp /etc/inittab /etc/inittab.original</code># Edit the file <code>/etc/inittab</code> and change the default runlevel to 3. Save the change and reboot your system.# After the reboot, you should get a "Text Login Screen". 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.==== Steps ====
# In the Virtual Machine Manger, click on the icon to ''Create a Virtual Machine'' in 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).
# '''Step 4 of 5:''' This next step creates a disk file that will 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 of 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).
Answer {{Admon/important|Removing and Recreating VMs|If for some reason the Investigation 3 questionuser wants to remove a Virtual Machine, they can right-click the VM, and select delete in the Virtual Machine Manager. It is recommended to '''"delete the image file" in the remove VM dialog box when removing and then recreating a VM'''. Note: If you fail to properly remove the VM image file, it may affect the hard disk size for the new VM (i.e. use the old smaller size. Make certain to remove that VM image file prior to recreating the VM.|'''}}
== Investigation 4: What is {{Admon/note|Fedora LIVE CD Install Screen Shots Thumbnails|While performing the network configuration?Fedora 17 LIVE CD install, click on the thumbnails below to provide a '''"visual reference"''' while performing this particular Fedora installation.}}
# To check the network configuration settings obtained from the DHCP server, run the following commands, describing the output in your log book:#* ifconfig#* route#* netstat -rn#* nslookup (at the > prompt, enter the word {|cellpadding="server8" width="100%" (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 nameserver
|[[Image:fedoralive1.png|thumb|100px| The Virtual Machine will now start.]]
|[[Image:failedtoload.png|thumb|140px| '''Ignore and close the "Failed To Load" dialog box'''. Search for the panel on the upper-left-hand side of the screen.]]
|[[Image:fedoralive2.png|thumb|140px|Login to the 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 boot process.]]
|}
<ol>
<li value="8">'''The virtual machine will now start'''. Select the default menu item labelled: '''Start Fedora 17'''. The virtual machine is running from the live disc at this point, and no software has been installed on the ''hard drive'' of the virtual machine.</li>
</ol>
Answer <ol> <li value="9">Login to the Investigation 4 questionVM and click: '''Applications'''>'''System Tools'''>'''Install to Hard Drive'''.The installation program, similar to the one used when installing Fedora in Lab 1, will appear. You will get a warning at one point during the installation process that the disk "May contain data" or "may need to be re-initialized" -- this is simply a warning that the virtual disk is completely blank, and it is safe to proceed with the installation.</li></ol>
{{Admon/note|Virtual Machine Screen Size|The virtual machine screen size will change resolution as it switches from text to graphics mode. Use the VM menu option View>Resize to VM to resize the window to show the entire VM display. If this is larger than your screen size, use View>Scale Display>Always to scale the image so it fits on your screen.
}}
<ol>
<li value="10">During the installation process, when prompted for a storage device, first select '''Specialized Storage Devices''', and then select the '''Virtio Block Device''' option.</li>
<li>When prompted for the hostname, enter '''fedora1''', and when prompted for the timezone, select '''Toronto - Eastern Time Ontario''', and when asked about storage, select '''Use All Space'''. '''Use the default values for all other fields.''' Notice that the installer does not ask you what software should be installed; compare the installation time to the amount of time it took to do your Lab 2 installation. Record this information in the '''table contained in Investigation 4'''.</li>
<li>When the installation is complete, click on the '''reboot''' button at the bottom right-hand corner of the screen.</li>
</ol>
<ol> <li value=== Investigation 5: How do "13">Start the 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 Secure will get the Grub Boot Loader? ===''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 Matrix account.</li> <li>Login using the new user account.</li></ol>
By default, {{Admon/note|Network / Service Considerations|Please perform the Grub boot loader allows anyone with access tasks below in order allow these Fedora systems to the computer at boot time to set the runlevel, or change the boot parameters, which can allow them be able to influence the init process and which kernel image is loaded. Anyone communicate with access to the boot prompt can therefore bypass security controls and control which software is loadedeach other. For example, rebooting '''Failure 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 properly perform these operations can be dangerous, and it is wise to protect the boot loader with a secure passwordcause problems in future labs'''. |}}
We will need <ol> <li value="15">Enable SSH access to choose a password, encrypt your virtual machine with the grub programs hash utilitythese commands (called md5crypt, and add semi-colon allows commands to be run in sequence):<br /> <code>service sshd start; chkconfig sshd on</code></li> <li>Find out the encrypted hash IP address of your password virtual machine: <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 grub configuration file, host (your main Fedora installation): <code>ssh ''IPaddress''</etccode></grub.confli>First, choose a suitable password. </ol>
Do not forget it, or you will not be able {{Admon/tip|Switch to change boot parameters when you boot your system! Virtual Machine Manager Window|If you need to write it down, put it are currently in a safe placeVirtual machine, where no one will be able but want to switch to tell what it is for. Open the grub program by typing Virtual Machine Manager Window, simply click '''Activities'''> '''Select the command: grubVirtual Machine manager window'''.}}
At '''Answer the grub prompt, type Investigation 1 observations / questions in the command: md5cryptWhen prompted for a password, carefully type in your password. The program will display the encrypted hash of your password. Carefully write this downlab log book.'''
Type the command== Investigation 2: quit to exit Installing from the grub program.Network ==
Open {{Admon/tip|Authenticate to the grub configuration file, /etc/grubnetwork|The rest of this lab uses network access.conf , for editing. This file is actually linked ''' Be sure to authenticate to /boot/grub/grub.confthe network using your browser before proceeding'''.}}
Carefully add the line === Introduction ===
password --md5 password-hash (note: password-hash It is possible to install Fedora entirely from the hash network. In this investigation, you generated with md5crypt)will install Fedora from a webserver on Seneca's LAN.
to the file between the splashimage line and the title line. If there are other lines there, there is no need to remove them. Just insert your password line as a new line.==== VM details ====
It should look something like this* '''Name: ''' fedora2* '''Boot media:''' Network installation* '''Installation source:''' http://belmont.senecac.on.ca/fedora/releases/17/Fedora/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/splashimage=(hd0#* In '''step 2 of 5''',0)/set the ''OS Type'' to '''Linux''' and ''Version'' to '''Fedora 17'''. # Observe the bootprocess. How is it different from booting from an optical disc (CD/grub/splashDVD)?# 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.xpmOn the next screen, change the logical volumes as follows:#* Reduce the size of the root LV to '''8000 MB'''.gzpassword #* '''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--md5 $1$jxcdN0$hVHViq1aiPf8FziuGJGZp0system type).hiddenmenu# On the software selection screen, select '''Graphical Desktop'''.title # '''On the same screen, select the "Fedora17 - 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'''.
You can find a more complete sample of this file here'''Answer the Investigation 2 observations / questions in your lab log book. '''
Make sure you have not made a mistake. What you type in must match exactly the output == Investigation 3: Installing from the md5crypt command.Network using Kickstart ==
While you are editing the file you should also increase the timeout for grub to automatically boot the default OS. Edit the line timeout=0 to timeout=5 to give us more time to interrupt the process.= Introduction ===
Save 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 and exitrather than answer them individually. Your Grub boot loader This type of file is now password protectedcalled a ''kickstart'' file.
Make sure the configuration In this investigation, a kickstart file is owned by root, and set the permissions so only root provided for you. You can read and writealso create or modify a kickstart file using a regular text editor or a graphical tool.
Find the section of this article that explains how to change the runlevel at boot time, and read it. Reboot your system, trying to change to runlevel 1 from the boot prompt, and see if the password protection worked. From now on, when you want to change boot parameters when you boot, you must type lowercase==== VM details ====
p* '''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 boot prompt kickstart file (using the URL you entered) to <u>determine</u> the root password as well as the name and enter password for the required first user account'''.# Boot the virtual machine and log in (use the user ID and passwordinformation 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'''.
Completing '''Answer the LabInvestigation 3 observations / questions in your lab log book.'''
Check off the following items == Investigation 4: Updating and sign your name before asking your instructor to check your lab:I have completed Comparing the following tasks in full:VMs ==
[ ] Task 1 - Install GNU# In each VM, run this command: <code>yum update</Linux Workstation using Fedora 10code># 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?
[ ] Task 2 Complete the following table (and transfer into your lab2 log- Collect system information after installation.book notes):
[ ] Task 3 {|border="1" width="100%" cellpadding="5"|- Customize and configure ! ||f17host||fedora1||fedora2||fedora3|-|'''Installation Method'''||Installation Disc||Live Disc||Network Installation||Network Installation + Kickstart|-|'''Packages Installed'''|| || || |||-|'''Updates Installed immediately after installation'''|| || || |||-|'''Software could be selected during installation'''|| || || |||-|'''Disk layout could be selected during installation'''|| || || |||-|'''No questions asked during installation'''|| || || |||-|'''Total installation time''' (after installation questions)|| || || |||-|'''Amount of disk space used'''|| || || |||-|'''Questions asked during first boot time environment'''|| || || |||-|'''Advantages of this type of installation'''|| || || |||-|'''Disadvantages of this type of installation'''|| || || |||-|'''This type of installation is recommended for...'''|| || || |||}
[ ] Task 4 - Collect network information[ ] Task == Investigation 5 - Password protect Grub Bootloader: Managing Virtual Machines from the Command Line ==
Student Signature: _____________________ Date: ________________Arrange evidence for each of these items {{Admon/note|Manage virtual machines from the host|The commands used to manage virtual machines must be executed on the host (your screen, then ask your instructor each item:disk pack) and not inside a virtual machine.}}
[ ] Grub # Start the ''fedora1'' virtual machine, and stop the ''fedora2'' and ''fedora3'' virtual machines.# Switch to the f19host machine, and open a shell terminal.# Enter these commands into your f19host machine and note the result:#* <code>'''virsh list'''</code>#* <code>'''virsh list --all'''</code>#* <code>'''virsh list --inactive'''</code># Now, shut-down your fedora1 VM normally, and close the fedora1 VM window. Make certain NOT to close the Virtual Machine Manager main window.# Switch to your terminal and issue the command: <code>'''virsh start fedora1'''</code># Check to see if your fedora1 VM is password protectednow running.# Switch to the terminal and issue<code>'''virsh list --all'''</code> and confirm the status of the fedora1 VM.# There are other commands that can be used (such as suspend, or shutdown). The "shutdown" command may not always work since it sends a request to "shutdown virtual machine gracefully", but may not always work.Why do you think it is useful to have commands to manipulate VMs?
[ {{Admon/note|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 ] Can login with student's "learn" account''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 cord out of the wall on a physical machine!|}}
[ ] Has all the mount points
[ ] Has '''Answer the package countInvestigation 5 observations / questions in your lab log book.'''
[ ] Has edited the default runlevel== Investigation 6: How do I backup a virtual machine? ==
[ ] Has {{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 correct IP address '''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 MAC addressre-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> ] Find out <li>Start the default route '''''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="a"><li>Verify that you are in the directory: <code>/var/lib/libvirt/images/</code>.</li> <li>Execute the following command: <code>virsh dumpxml fedora3 >fedora3.xml</code></li> <li>Examine the file <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 (gatewayeg. 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?
[ ] IP {{Admon/important|Backing up VMs|It is essential to back up your VMs at the end of each lab, so you can easily restore them if something goes wrong in the DNS name server next lab.}}
Instructor Signature: _____________________ Date: ________________{{Admon/tip|Shutting Down the Host while Virtual Machines are Running|If you shut down your host system while virtual machines are running, they will be suspended, and will resume the next time you boot your host system.}}
Preparing for '''Answer the QuizzesInvestigation 6 observations / questions in your lab log book.'''
How many packages were installed?== Investigation 7: Kickstart Files ==
How many {{Admon/tip|SSHD and Firewall|If you have restarted your virtual machine ''fedora1'', the sshd server you started in investigation 1 (step 15) will no longer be running. In addition, the firewall will have reverted to its original state. In order to use '''scp''', below, you will need to restart ssh and adjust the firewall again.<br /><br />If students cannot backup their kickstart files using the '''scp''' command, they can use a web-browser to access their Seneca e-mail with attachment (copy kickstart file to their home directory first!). For the text-based Linux system "fedora3", students can use the '''mail''' command (correct refer to the nearest hundredman command to learn how to send e-mail attachments) were installed?. }}
How many mount points were used?When you perform a non-Kickstart installation, the installation program creates a Kickstart file in the <code>/root</code> directory for reference.
How many users were created automatically on # Obtain the kickstart files for all four of your 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 your f17host system (do not count your learn accounttip: 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?
What is '''Answer the Investigation 7 observations / questions in your learn accountlab log book.'''s UID and GID?
What is your learn account's home directory?= Completing the Lab =
What is the home directory '''Arrange evidence for each of these items on your screen, then ask your instructor to review them and sign off on the user "root"?lab's completion:'''
How do you determine the host name of your GNU/Linux workstation?# Three working virtual machines created.# Four kickstart files.# All virtual machines fully updated.# All virtual machines backed up.# Installation comparison table filled in.# Lab Logbook (lab2) notes filled-in.
What command can display the NIC's MAC address?= Preparing for Quizzes =
# What is the name of the Fedora installation program?# Which file contains factors recorded in your table (above) were due to the type of installation performed, and which factors were due to the default "runlevel" value 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, and how is it created?# How do you start and stop virtual machines?# How do you SSH into your GNU/Linux workstationvirtual 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?)