1,576
edits
Changes
no edit summary
[[Category:OPS235]]
{{Admon/caution|Draft LabTHIS IS AN OLD VERSION OF THE LAB|'''This lab has NOT been released for regular distributionis an archived version. When the lab is ready to be released, Do not use this caution banner will disappearin your OPS235 course.'''}}
= CentOS Installation Methods (on Virtual Machines: centos1, centos2, centos3) =
== Using the Virtual Machine Manager ==
<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 '''centos1''', and when prompted for the timezone, select '''Toronto - Eastern Time Ontario''', and when </li> <li>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="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 will get the ''Firstboot'' configuration questions during the boot process (asking you to create a user, set the date and time, and ignore the kdump out-of-memory warning). Make certain that the VM has a network interface connection (i.e. look at network applet on the top panel). Create a user with the same name as your Matrix account.</li>
<li>Login using the new user account.</li>
</ol>
==== Steps ====
# Create the VM (called '''centos2''') as you did with the ''centos1'' virtual machine, except:#* In '''step 1 of 5''', set select network installation using 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/centos/6url displayed above.5/os/x86_64/
# Observe the boot process. How is it different from booting from an optical disc (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 <u>logical volume </u> 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'''.
# 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'''.
==== Steps ====
# Create the VM as you did with the ''centos2'' virtual machine, specifying a network install as before, except:#* In step 2 of 5, after entering but specify the kickstart location under the URL "options section" for the installation source, click on the '''URL Options''' controlnetwork install.#* Enter What do you think is the Kickstart URL locationpurpose of this kickstart file?
# Observe the installation. How is it different from booting from an optical disc?
# 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 (eg. view url in a webj-browser) to determine 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'''.
== Investigation 4: Updating the VMs ==
{{Admon/important|Check that your graphical VMs are connected to Network|It is recommended when starting a graphical VM, check the network icon to see if the system is connected. If it is NOT connected, select auto eth.}}
# In each VM, run this command: <code>yum update</code>
#* Why does it take longer in some VMs than others?
{{Admon/caution|Never Shutdown Computer During Upgrade|Your computer (host, vms) are at their most vulnerable when you perform an update. Always plan ahead for appropriate time prior to performing an update. Shutting down your computer while performing an update may cause your computer not to boot! You have been warned!!!}}
# Start the ''centos1'' virtual machine, and stop the ''centos2'' and ''centos3'' virtual machines.
# Switch to the c6host machine, and open a shell terminal.
# Enter these commands into your f19host c6host machine and note the result:
#* <code>'''virsh list'''</code>
#* <code>'''virsh list --all'''</code>
# Obtain the kickstart files for all four of your installations (your disk pack ''c6host'', plus the ''centos1'', ''centos2'', and ''centos3'' virtual machines).
# To prevent confusion, copy your kickstart files to kickstart filenames that describe their purpose (eg. kickstart_host, kickstart_centos1, kickstart_centos2, etc...)
# Copy them all to your c6host system (tip: use <code>scp</code>), webmail, or use the hint in the tip box above to send via ecommand-line mail. Refer to the manpages for help).
# 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?
# Three working virtual machines created.
# Disk layout and size correct on all virtual machines
# Use virsh to list the status of all vms.
# Four kickstart files.
# All virtual machines fully updated.
