Current Semester (Winter 2016)
- The number of topics in the current form of the course is impossible for the students. I haven't had a single one excell at all of them and I've had some very talented students. We need to pick some topics we feel would be crucial and drop the rest or reduce the rest to study-only-no-labs (the latter seems useless to me) --Andrew
- I've found the number of labs is reasonable, provided the labs:
- work (which I found was the biggest issue, and thus modified all the labs the first semester I taught the course (in some cases had to do a complete rewrite)
- Post-iptables lab Issues. I have my students flush the rules, set the default policies to accept and save them as such (and disable firewalld). This way when they troubleshoot problems, at least it's not iptables getting in the way. --Jason </ul>
- Eleven labs seems to be a lot of labs for this course. Can't students simply use c7host that they created in OPS235 (with tweaks) in order to streamline labs 0 and 1? Can students use their existing OPS235 removable hard drives to reduce re-installing CENTOS7?
- I don't think there should be a lab0. That setup should be done on their own time in advance, all needed to do the setup was learned in OPS235. If the students don't remember - that's a good reason for them to spend extra time getting a refresher on OPS235. -- Andrew
- Same for networking. All the students had trouble with basic network setup. They need to be told to go back on their own and remember how to configure an interface. And they have to be tested on it for the first 2-3 weeks to make sure they know it's a serious requirement. --Andrew
- Can't use c7host from 235 because a good number of students don't have it any more, it's not unusual for students to go to coop between 235 and 335. -- Andrew
- Would be preferable to have sub-WIKIs discussing the concepts of why students are doing lab[01] (purpose/overview) prior to complete (that|those) lab(s)
- [ OPS335-Lab1 Overview ]
- [ OPS335-Lab2 Overview ]
- [ OPS335-Lab3 Overview ]
- [ OPS335-Lab4 Overview ]
- [ OPS335-Lab5 Overview ]
- [ OPS335-Lab6 Overview ]
- [ OPS335-Lab7 Overview ]
- [ OPS335-Lab8 Overview ]
- [ OPS335-Lab9 Overview ]
- [ OPS335-Lab10 Overview ]
- Labs need to be worth more, 2% per lab in OPS235 seems to work well. --Andrew
Fully agree, my breakdown at night (that I largely inherited) is differently weighted, copy/pasted the breakdown as follows
- Quizzes (1 per lab, staggered a week after the lab is introduced as in uli101 & ops235) - 10%
- Tests (mid term) - 30%
- Assignments (1 - broken down into several parts)- 10%
- Lab work - 20%
- Final Exam -30%
I'm planning on dropping the weighting of the mid term to 25%, and upping the assignment to 15% as I find at 10% a good portion of the students don't even bother doing it. The above breakdown addresses Andrew's point about quizzes as well -- Jason
- Need lots of small quizzes. Perhaps one per week unless nothing new's been taught that week. --Andrew
- Need two tests, preferably practical - especially since the exam is written. -- Andrew
I have one written mid-term currently. There's pros and cons to a practical test, I try to cover more troubleshooting and questions directly from the labs in my written tests. The downside to a practical is having to rely on Seneca's network working (which is unreliable at best). Instead I have 1 assignment, research and implement something not covered in the course, and provide detailed documentation as to how to do it (similar level of detail as given in the labs). -- Jason
- Use CentOS on the virtal machines. Using Fedora has been no more successful in OPS335 than in OPS235. CentOS has problems but it's consistent and reliable. Fedora will do some random crap you won't believe. All the tools and services used in the course are equivalent between CentOS and Fedora (except yum/dnf which are the same anyway). --Andrew
I use centos 6.7 on the host (because 7 caused issues with portabity - crashes completely if there's a significant change in hardware and won't boot again. centos 7 on all 3 virtual machines -- Jason
- Iptables is really complex but still the industry standard for firewalls. Firewalld may or may not (probably not) replace it. There's no time to teach both, should get rid of Firewalld completely. --Andrew
Fully agree - I've been trying to figure out how to mix Firewalld into the course, presently I only cover iptables. I apologize if I messed up the wiki formatting. -- Jason