๐Ÿ“ Ottawa, Ontario, Canada   |   Engineering the Future. Exploring the Unknown.Online education initiative in development

Course description and requirements

This proposed course develops practical knowledge of proxmox virtualization through guided instruction, supervised technical exercises, troubleshooting and documented projects.

Course code: VRT-101 | Duration: 12 weeks | Workload: approximately 8โ€“10 hours/week | Total: approximately 96โ€“120 hours

Prerequisites: Linux and networking fundamentals

Delivery: Planned online lessons, virtual laboratories, graded assessments and instructor feedback.

Status: In development; not open for enrollment.

Learning outcomes

  • Explain the technical principles covered in the course
  • Configure and troubleshoot relevant systems in an authorized lab
  • Apply safe operational practices and document results
  • Evaluate a working implementation against defined requirements
  • Communicate findings in a professional technical report

Detailed 12-week teaching plan

Week 1: Virtualization concepts

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 2: Hardware planning

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 3: Proxmox installation

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 4: Web administration

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 5: Storage configuration

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 6: Linux VMs

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 7: Virtual networks

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 8: Containers

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 9: Snapshots

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 10: Backups

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 11: Recovery testing

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Week 12: Virtual infrastructure project

Lesson: Study the concepts, terminology, configuration steps, common failure modes and operational considerations for this topic.

Practical lab: Build or configure a relevant component in an isolated test environment; capture configuration details and verify the result.

Evidence: Submit a lab record containing the objective, steps, results, troubleshooting notes and a short reflection.

Five graded practical assignments

Assignment 1 โ€” Week 2: Hardware planning

Task: Complete a practical implementation or investigation related to hardware planning. Document the requirements, approach, evidence of operation, test results and any problems encountered.

Submission: Technical report, configuration evidence and supporting files where applicable.

Marking: Technical accuracy 40%, verification 25%, documentation 25%, safe practice 10%.

Assignment 2 โ€” Week 4: Web administration

Task: Complete a practical implementation or investigation related to web administration. Document the requirements, approach, evidence of operation, test results and any problems encountered.

Submission: Technical report, configuration evidence and supporting files where applicable.

Marking: Technical accuracy 40%, verification 25%, documentation 25%, safe practice 10%.

Assignment 3 โ€” Week 5: Storage configuration

Task: Complete a practical implementation or investigation related to storage configuration. Document the requirements, approach, evidence of operation, test results and any problems encountered.

Submission: Technical report, configuration evidence and supporting files where applicable.

Marking: Technical accuracy 40%, verification 25%, documentation 25%, safe practice 10%.

Assignment 4 โ€” Week 8: Containers

Task: Complete a practical implementation or investigation related to containers. Document the requirements, approach, evidence of operation, test results and any problems encountered.

Submission: Technical report, configuration evidence and supporting files where applicable.

Marking: Technical accuracy 40%, verification 25%, documentation 25%, safe practice 10%.

Assignment 5 โ€” Week 10: Backups

Task: Complete a practical implementation or investigation related to backups. Document the requirements, approach, evidence of operation, test results and any problems encountered.

Submission: Technical report, configuration evidence and supporting files where applicable.

Marking: Technical accuracy 40%, verification 25%, documentation 25%, safe practice 10%.

Midterm examination โ€” Week 6

Proposed format: 90 minutes; multiple-choice, short-answer and scenario questions based on Weeks 1โ€“5.

Skills assessed: Technical terminology, configuration decisions, troubleshooting and safe practice.

Actual exam questions, answer keys and marking guidance will be prepared in the instructor-only Moodle question bank.

Final examination โ€” Week 12

Proposed format: 120 minutes; cumulative knowledge questions, troubleshooting scenarios and technical interpretation covering the full course.

Exam delivery, identity verification, accessibility accommodations and academic integrity procedures must be finalized before student assessment begins.

Capstone project

Project brief: Deploy a Proxmox test host with two VMs, virtual networking and a verified recovery.

Deliverables: Design plan, implementation evidence, testing checklist, results, troubleshooting record and final technical report.

Rubric: Design 20%, implementation 35%, testing 25%, documentation 20%.

Proposed grading

  • Weekly quizzes โ€” 10%
  • Five practical assignments and labs โ€” 25%
  • Midterm examination โ€” 20%
  • Final examination โ€” 20%
  • Capstone project โ€” 25%

Student preparation

A computer capable of running virtual machines or accessing an approved remote lab is recommended. Some courses may require additional RAM, storage, networking equipment or licensed software. Course-specific minimum requirements and accessible alternatives will be published before delivery.

All security testing must be limited to systems owned by the student or explicitly authorized for testing.

Academic status

This page describes a proposed curriculum. Instructors, tuition, assessment dates, enrollment and any required regulatory approvals are not yet established. No academic credit or professional certification is promised.