OPS235 Short-Term

From CDOT Wiki
Revision as of 15:57, 21 March 2016 by Msaul (talk | contribs)
Jump to: navigation, search

Current Semester (Winter 2016)

  1. 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.

  2. (FIXED) LAB 1 - Investigation 2 - Questions 6 & 7 - Looks like the name and content of the files have changed a little bit from "/var/log/anaconda/anaconda.packaging.log" to "/var/log/anaconda/packaging.log". The content also changed the words "installing" to "packaging".

  3. LAB 1 - Investigation 3 - Part 2 - Questions 21 - Not important but, report3.bash script uses the command "cat /root/install.log >> installation_report.html", the file /root/install.log does not exist on centos7 install.

  4. Wish List: "tweak" lab2check2.bash to provide additional checks including xml dumps to home directory for all VMs and reminder from script to back those items to USB key. Also should check if centos2 has / for 8 GB and /home for 2GB.

  5. qcow is used in ops335 not ops235. It wouldn't allow students to run the automated scripts. I read somewhere that xfs can mess up with LVM which we talk about in lab5. For next time, I will add in requirement in lab2 signoff that students show for all VMs the /etc/fstab to ensure ext4 fs. Perhaps checking script can be modified next time to check for that...

  6. It would be nice to rearrange the content for lab5 to discuss df -h and space concerns first, then flow into LVM. This would provide a better "flow" to reinforce student understanding. Shell script at end would remain at end to show how to use crontab to automate (flag) space issues.

  7. Good idea to expand shell script check for ALL labs. Student would be required to show same information PLUS the results from running the checking shell script.

  8. Good idea to review study questions at end of each lab to see if they are applicable to each lab.

  9. Would be neat to create prezi slide shows for each lab preparation (for class). This would be in sync with OPS335 course. Online slides can be exported to PDF files as well.

  10. Would be helpful for a script or program to check all links in all OPS235 (OPS335, etc) WIKIs to check for non-working links. This would allow course overseer to run just prior to the start of the semester and be incorporated into the startup checklist.

  11. Some students note different vg name (like centos instead of centos_centos2). Solution is to get students to issue vgs to obtain vg name. Should investigate why this is happening to prevent (eg. shell script check at end of a lab).

  12. Check mailx command (lab5 example) for OPS235 to see why not sending mail.

Previous Semesters

Summer 2015

  1. 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.

  2. LAB2 - Backup Script demo: Current VM backup script should also allow for backing up xml configuration files.

  3. 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.

  4. The wget http://belmont.senecac.on.ca/centos/7/isos/x86_64/CentOS-7-x86_64-LiveGNOME-1503.iso command is still not working

  5. 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?

  6. 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.

  7. 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


Additional Resources / Navigation