Difference between revisions of "OPS235 Short-Term"
(→Current Semester (Winter 2016)) |
|||
Line 1: | Line 1: | ||
=Current Semester (Winter 2016)= | =Current Semester (Winter 2016)= | ||
− | # '''LAB 1 - Picture under part 2''' The picture called "Partition Verification" shows a LVM setup, but the instructions ask specifically for a standard partition setup. | + | # '''LAB 1 - Picture under part 2''' - The picture called "Partition Verification" shows a LVM setup, but the instructions ask specifically for a standard partition setup. |
− | |||
=Previous Semesters= | =Previous Semesters= |
Revision as of 18:08, 10 January 2016
Contents
Current Semester (Winter 2016)
- LAB 1 - Picture under part 2 - The picture called "Partition Verification" shows a LVM setup, but the instructions ask specifically for a standard partition setup.
Previous Semesters
Summer 2015
- LAB 1 - Installing NON-GUI version of Linux OS: A lot of students ran into the same problem with lab 1, that is they didn't pay close enough attention to the instructions and installed the OS without a GUI. But that is no flaw in your wiki, just the tendency of students to rush through things. I have done my best to enforce that they should read all the instructions carefully BEFORE they start on the labs.
- LAB2 - Backup Script demo: Current VM backup script should also allow for backing up xml configuration files.
- LAB - LVM: Current VM backup script does not factor in virtual hard drive images. May be a good idea to add this to the backup script, so students can be encouraged to run backup scripts.
- The wget http://belmont.senecac.on.ca/centos/7/isos/x86_64/CentOS-7-x86_64-LiveGNOME-1503.iso command is still not working
- When students issue the “service iptables restart” command it returns a message that says the service is dead and not running. Yet, I’ve tested the iptables themselves by adding a few rules and they are certainly still working. I’m really not sure what exactly is going on. Perhaps it’s just a glitch in CentOS7?
- The virtualization software also seems to need a system reboot before the virtual network will come into effect. Simply restarting the virt-manager or the libvirtd service doesn’t seem to do it. So, again, rebooting the system is the way to go to make sure the virtual default NAT network becomes visible for new VMs.
- Some students in lab2 may not be performing the correct steps in creating VMS (image paths and types). A shell script to be run to check this would be useful, but may need release time to create a comprehensive and user-friendly shell script.
Winter 2015
- Winter 2015: OPS235 - Short-term - Older Issues