OPS235 - Curriculum Discussion

OPS235 Course Discussion

Course Overview (Purpose)

This project-based subject will teach students how to install and configure a Linux server. Further, students will learn how to connect to and communicate over a network in a controlled environment. They will learn how to manage their files on their system and how to set-up file and directory permissions. Students will manage basic system security and firewall settings. In order to configure their system, students will gain knowledge of a few basic Unix/Linux commands and be exposed to 'Shell' basics. Finally students will work with both text and graphical user interfaces.

Course Linkages

Direct:

• ULI101 (Prerequisite)
• OPS335 (Upon successful completion of OPS235)

Influence for Success:

• NDD430 (CNS)
• OPS435 (CTY)
• OPS535 (CTY)
• SEC520 (CTY)

Common Concerns (Professor Observation)

• ULI101

• OPS235

1. Consistency Among Course Instruction. Need for consistency in following rules in case other OPS235 professors teach course when main OPS235 profs are on vacation (Consistent Cover-off)

• OPS335

1. Linux Commands. Students are not intuitively using the commands that they were exposed to in ULI101 and used in OPS235.
   
   
2. AODA Accomodation. Two issues worth noting: student access to locked rooms (TEL Building) and accommodation to Linux OS (various distributions) for students with special needs (like Braille devices).
   
   

• OPS435
• OPS535
• Other (Previous Meetings - Discussion)

1. Discrepancy Between College and Industry. Many of the CNS/CTY graduates in CDOT that move into industry notice "delta" between course concepts and "real world" practice of Linux admin in terms of Enterprise computing (clusters as opposed to single machines).
   
   
2. Setting up in the Cloud. More emphasis should be placed on administering / setting up in the cloud (paradigm shift) . This concern was also mentioned and addressed in the CNS/CTY PAC committee meeting held in the previous week.
   
   
3. Clusters vs Single Machines. Many of the CNS/CTY graduates in CDOT that move into industry notice "delta" between course concepts and "real world" practice of Linux admin in terms of Enterprise computing (clusters as opposed to single machines).
   
   
4. Taxonomy. Importance to design courses using a taxonomy (i.e. a ladder or "steps") whereby complexity builds so students develop and understand how to administer or perform an operation, but are then required to apply skills (especially "think" / self actualization to better cement concepts or purpose of labs). Perhaps over time (due to other instructors not involved with planning of course) made improvements that may have made students "perform steps" (path clearing) as opposed to being challenged with a purpose in mind.
   
   
5. Online Collaboration. Discussion of the importance of collaboration. For example, more instructors are starting to use the WIKI, but should there be "best-practices" for WIKI use? Also, mention of need possibly for instructors to use technology to help all keep "in sync" in a way to keep consistent, but also prevent impeding on instructor's flexibility or freedom of delivery...
   
   

Course Improvement Suggestions

• Short-Term

1. Linux Commands. Try to bridge the gap of Linux commands throughout the OPS235 / OPS335 / OPS435 / OPS535 stream. Recommended for Winter 2015 semester to allow students to add previous reference sheets and/or lab log-books to existing material.
   (For example, allow ULI101 reference sheet to be added to OPS235 lab logbook, OPS335 contains OPS235 lab logbook notes plus ULI101 reference sheet, etc). Would it be worthwhile to print empty ULI101 reference sheet with already created section headers so they can place commands in required area (students associate the type of tool to refer to get the job done). Action taken: Murray Saul notified Mark Fernandes of idea, Mark had a discussion with some of ULI101 faculty. The decision to not have reference sheets for ULI101 course was due to prevention of students cheating if answers to final exam obtained. Suggestion was made that a template Linux command reference sheet will be made to help students study prior to ULI101 final exam, and this standardized sheet can be added to the OPS235 lab log-book.
   
   
2. YUM Command for Local Installs. The rpm command in lab3 relating to local installs appears to be deprecated (favoring yum local install). OPS235 team to meet to discuss implementation (Status: WIP).
   
   
3. Checklist for semester startup. There is a considerable amount of work to do to ensure items are updated for OPS235 prior to semester startup. I think it would be a good idea to have a check-list for all items such as: Covering off with OPS335 for version of CENTOS to use, update lab-book semester info, update instructors and photos, testing and update links for media install, update weekly dates for notes, update professor names and sections in both main WIKI and Weekly Schedule, submit Weekly schedule to Dianna, etc.
   
   Sample OPS235 Semester Startup Checklist using GoogleDocs Forms: [ OPS235 Semester Startup Checklist ]
   View Status of OPS235 Semester Startup Checklist: [ OPS235 Semester Startup Status ]
   
   
4. AODA Accomodation.
   
   Issue #1:
   
   It is recommended to make available for each lab or classroom a method to safely keep a door open while class is in session without propping the door open with a chair - If door is not opened, door is locked which can be a distraction for professors when delivering course material. It has been noted there is no consistency in the TEL building wrt many of the labs: Some have door stops, many do not. If door stops are not somehow attached to lab, they go missing or are used for other labs. If door is opened with propping chair, can be unsafe for students with special needs (for example blind students) and problems in the event of an emergency (for example: fire). Also, it has been noted challenges in providing Linux drivers to communicate with devices for individuals with special needs. These issues when solved should be shared in a central repository with support and suggestions to allow better access through a student's duration and with different instructors, staff.
   
   Issue #2:
   
   A program called brltty.service. The file brltty.service is the application which going to make the braille device work. A bash file can be used to start the service brltty.service. A Seneca professor knowledge in Linux (Chris Tyler) stated, "that you cannot get the service to run without the script on Fedora." NOTE: It would be worthwhile to see if this works for other Linux distributions for Linux or Linux influenced courses in the CNS/CTY stream. NOTE: This service is that it cannot run in the graphical environment, it has to run on the terminal/console/command line. Whenever you switch to the GUI it says screen not in text mode and it stops working from there after. One example of a Baille device that this service works for is called: Optelec ALVA BC640 braille display. As for the model number I am not certain as to where you can find that information on it. The only thing I know is that it says it is running firmware 2.10. If you google the name there are not really any different ALVA BC640 or ALVA BC6 series braille displays by Optelec. Therefore, the model number may not be a necessary requirement to work in Linux.
   
   Also, would be nice to establish connection with Special Needs office with Linux support for assistance devices for students with special needs, and a link for each course (within resource support). Perhaps good idea to encourage faculty to visit and experience these devices.
   
   

   Braille Reader application: brltty
   
   Files for Braille Reader in Linux (Fedora):

   • Application to Run britty service: [ britty.service ]
   • bash shell script to start britty service: [ go.bash ]

   
   
   

• Long-Term

1. Scripting for Lab1. Lab 1 could be modified to have students generate a report regarding the collection of Linux information after an install. Certainly command substitution could be taught and to reinforce redirection >> to add content to a filename (i.e. not over-ride). It would be interesting to expose students to the zenity command to allow a menu to give user choice of report elements to include in the generated report. Perhaps a link to a "fancy" Bash shell script to generate a web-page so students can view the contents in a nice format. This scripting element could easily be added to assignment #1.
   
   [ Scripting Compatibility for Current OPS235 labs: (Week-by-week) ]
   
   

• Wish List

Additional Resources

• OPS Stream Discussion