OS Presentation
Description
The purpose of this assignment is to present an OS topic with a corresponding software implementation related to material we covered in class. This has mostly been related to DevOps / Linux Administration. The presentation must be around 15 minutes in length. We will have around 5 minutes for questions after each presentation.
Here is a general outline for the presentation:
Description of the general topic and what problem it solves.
Detailed description of the specific software related to the topic.
Demonstration.
Here are some potential topics with specific examples in parentheses:
- Container orchestration (
Kubernetes) - Continuous Integration / Continuous Deployment (Jenkins, TravisCI)
- File systems (ZFS)
- Infrastructure as code (
Ansible, Puppet, Chef, Salt) - Linux distributions trying new ideas (Fedora SilverBlue, NixOS)
- Network applications (setting up a DNS server, setting up an email server with sendmail)
Secret management- Security (
general server hardening) - VPN (Wireguard,
NordVPN) - Virtualization (VMWare, Xen)
- Compare and Contrast (Linux package managers, container systems,
version control)
Turning in the Presentation
To submit your assignment, create a zip file named presentation.zip of a
DIRECTORY named presentation containing any relevant files for your
presentation; at a minimum, the presentation slides must be included. Then
submit that file to the appropriate folder on D2L.
Turning in the Rubrics
After all presentations are concluded, create a zip file named rubrics.zip of
a DIRECTORY named rubrics containing a completed rubric for every
presenter excluding yourself. Each rubric must be named with the following
convention: <last name>_<first_name>.<file extension>. Note that a completed
rubric must include comments. Then submit the zip file to the appropriate
folder on D2L.
Grading Rubric
| Presenter Name | 4 | 3 | 2 | 1 |
| Delivery | Presenter’s voice is clear and speaks at a good pace. Does not read off slides | Presenter’s voice is clear, but the pace is a little slow or fast at times. | Presenter’s voice is low or the pace is too rapid or slow. | Presenter’s delivery makes it difficult to understand the presentation. |
| Length | Within two minutes of the allotted time. | Within four minutes of the allotted time. | Within six minutes of the allotted time. | Too long or too short; more than six minutes above or below allotted time. |
| Content | There is an abundance of material related to the topic. Points are clearly made and evidence is used to support claims. | There is sufficient material related to the topic. Many good points made, but uneven balance and little consistency. | There is an obvious lack of material related to the topic. | There is material included that does not support the topic in any way. |
| Organization | The information is presented in a logical and interesting sequence which the audience can follow. | The information is presented in a logical sequence which the audience can follow. | The information is presented in a way that lacks logical transitions making it difficult to for the audience to follow. | The information is presented in a chaotic manner which the audience cannot understand. |
| Demo Quality | The demo is strongly cohesive and includes the most salient features of the software. | The demo is relatively cohesive and/or includes many salient features of the software. | The demo is weakly cohesive and/or include few salient features of the software. | The demo is incoherent and/or lacks any salient features of the software. |
| Comments | ||||
Note: all students must complete this rubric for every other student’s presentation; an overly unobjective evaluation will result in a grade penalty.