CSIS-3383 Cloud SDN
Michael MacLeod
Credit Spring 2024
Section(s)
CSIS-3383-001 (74661)
LEC DIL ONL DIL
LAB DIL ONL DIL
Course Requirements
Course Description: Software Defined Networking (SDN) is an emerging networking technology that has been rapidly changing the networking industry and networking research. By separating the network control from the underlying packet forwarding hardware, SDN lowers the entry-point for innovation in network control and enables a global approach to specify complex networking tasks in one single control framework, which promises significant simplification of network management, control, and monitoring. SDN has gained significant traction among major industrial players including Cisco, Broadcom, Google, IBM, and Intel, and has been deployed in wide area networks, campus networks, and data centers. In this class, you will learn the fundamentals of SDN and gain hands-on experience.
Pre-requisite: ITNW 1335 or department approval
Course Rationale: This course will introduce students to software-defined networks (SDN) from the aspects of code, physical hardware, and cloud infrastructure. The course is designed to analyze the proven and mature technologies and practices through the study of industry standards that have defined the concepts, models, technology mechanisms, and architectures that support various business requirements. The course incorporates vendor-neutral terms and descriptions, developed in a manner to ensure alignment with software-defined networks used in the industry as a whole.
Instructional Methodology: This course will have 50% lecture and 50% laboratory.
The CIS open labs are available for students for work outside of scheduled lab time.
Grade Policy:
Grades will be assigned based both on concepts and practical application.
|
2340-2600 points |
A |
|
2080-2339 points |
B |
|
1820-2079 points |
C |
|
1560-1819 points |
D |
|
1559 points or less |
F |
Basis for Grades
|
Type |
Number |
Points Each |
Total Points |
|
Orientation Review |
1 Each |
100 |
100 |
|
Labs |
10 Labs |
100 |
1000 |
|
Project |
1 Each |
200 |
200 |
|
Lecture Review Exercise |
4 Each |
100 |
400 |
|
Lecture Exam |
4 Each |
100 |
400 |
|
Final Review Exercise |
1 Each |
200 |
200 |
|
Final Exam (in 3 parts) |
1 Each x3 |
100 |
300 |
|
|
|
|
|
|
|
|
Total |
2600 |
Orientation Review (See Schedule)
1 in number
Total Points 100
Students should fill out the student form and submit via Blackboard to receive credit for this assignment. The student form can be electronically signed for this class. The form will be returned during the first week of class.
The Orientation Review will not be re-opened after the scheduled due date.
Lab Assignments (see schedule)
10 in number
Total Points 1000
Application oriented
Will cover specific programs and can be cumulative.
Open book.
If you complete a lab assignment up to one week after the due date, there is a deduction of 10% from your grade. If you complete a lab assignment between one week and two weeks late, then there will be a deduction of 50% from your grade. You may not turn in a lab assignment after two weeks from the due date; you will receive a grade of zero (0%) for the assignment.
To prevent the 10% or 50% grade reduction, you must meet the following conditions:
- You must have experienced an unforeseen and sudden emergency. Note: getting behind
in the course is not an unforeseen emergency. - You must present Dr. MacLeod with documented proof of your emergency.
- You must contact Dr. MacLeod by ACC e-mail of your emergency on or before
the assignment deadline date.
Project (see schedule)
1 in number
Total Points 200
Application oriented
Will cover specific programs and can be cumulative.
Open book.
Projects turned in up to one week after the due date will receive a 10% grade deduction. Projects turned in between one and two weeks late will receive a 50% grade deduction. You may not turn in an assignment after two weeks from the due date; you will receive a grade of zero (0%) for the assignment.
To prevent the 10% or 50% grade reduction, you must meet the following conditions:
- You must have experienced an unforeseen and sudden emergency. Note: getting behind
in the course is not an unforeseen emergency. - You must present Dr. MacLeod with documented proof of your emergency.
- You must contact Dr. MacLeod by ACC e-mail of your emergency on or before
the assignment deadline date.
Review Exercise (see schedule)
4 in number
Total points 400
Will cover specific chapters and appendices
Open book
Lecture Review Exercises are designed to appraise the student’s coursework knowledge during the given period. The review exercise will be open for one day (24-hour period).
The Review Exercise will not be re-opened after the scheduled due date.
Lecture Exams (see schedule)
4 in number
Total Points 400
Will cover specific chapters and appendices
Closed book
Lecture Exams are designed to appraise the student’s coursework knowledge during the given period. The review exercise will be open for one day (24-hour period).
The Lecture Exams will not be re-opened after the scheduled due date.
Final Review Exercise (see schedule)
1 in number
Total points 200
Will cover specific chapters and appendices
Open book
The Final Review Exercise is designed to appraise the student’s knowledge of the topics presented in the course. The final review will be open for one day (24-hour period).
The Final Review Exercise will not be re-opened after the scheduled due date.
Final Exam (see schedule)
1 in number in 3 parts
Total Points 300
Will cover specific chapters and appendices
Closed book
The Final Exam is designed to appraise the student’s knowledge of the topics presented in the course. Each part of the final exam will be open for one day (24-hour period).
The Final Exam will not be re-opened after the scheduled due date.
Testing Policy
All exams, including final exam parts, have a scheduled date on which the exam is to be completed. Exams are open for one day only. Exams will be taken during the scheduled time based on the course schedule and times as identified by the instructor.
If a student cannot take the exam on the scheduled date, due to documented unforeseen circumstances (i.e.: illness, which requires a doctor’s statement, family emergency, or emergency call out), the student is required to notify the instructor in writing as soon as possible.
The circumstance must meet the following conditions:
- You must have experienced an unforeseen and sudden emergency. Note: getting behind
in the course is not an unforeseen emergency. - You must present Dr. MacLeod with documented proof of your emergency.
- You must contact Dr. MacLeod by ACC e-mail of your emergency on or before
the exam deadline date or the exam administration date and time.
The circumstance will be evaluated to determine whether it allows for an exception.
If a student fails to take an exam without an approved exception, the student will receive a grade of zero for that exam, and it will be final. The student will also be required to take all remaining Exams at the Highland Campus testing center.
Retesting & Extra Credit
Dr. MacLeod does not allow retesting or extra credit.
Important Grading Notes
Grades will be posted as they are earned throughout the semester. You must report (in writing) all grading issues within seven calendar days of the grade being posted. The grade will be final if you have not reported a grading issue within seven calendar days.
Grades are based on achievement, not effort.
Grade of Zero During Course
During the course, a grade of zero will be given for any assignment not turned in by the due date. The zero is a placeholder to remind the student of what assignments are not completed. Assigned work may not be turned in more than two weeks after the due date; the assignment will receive a final grade of zero (0%). Exceptions: time-sensitive assignments (orientation review, exam reviews, and exams) and assignments whose due dates are within the last two weeks of the semester.
Request for assistance on coursework
When assistance is required on assignments, send an email with the following information to the instructor: The course number and “Request for Assistance” in the subject line. The body of the email will include what troubleshooting steps have been taken and what research has been done by the student.
Readings
| Wk. | Cl. | Day | Date | Lecture | Readings |
| 1 | 1 | M | 15-Jan | Orientation Big Picture of Network Topology Review of course goals, class policies, etc., i.e. the Syllabus. What is SDN |
Syllabus VMWare Ciena Cisco Juniper Networks ONF |
| 2 | 2 | M | 22-Jan | How Does SDN Work | How Does SDN Work? How SDN Works Difference Between SDN and Traditional Networks |
| 3 | 3 | M | 29-Jan | SDN Challenges | SDN Challenges SDN Challenges & Direction SDN Challenges & Effects |
| 4 | 4 | M | 5-Feb | Chapter 1 What is Infrastructure as Code |
Chapter 1 |
| W | 7-Feb | ||||
| 5 | 5 | M | 12-Feb | Chapter 2 Principles of Cloud Age Infrastructure |
Chapter 2 |
| 6 | 6 | M | 19-Feb | Chapter 3 Infrastructure Platforms |
Chapter 3 |
| 7 | 7 | M | 26-Feb | Chapter 4 Core Practices: Define Everything as Code |
Chapter 4 |
| 8 | 8 | M | 4-Mar | ||
| M | 4-Mar | ||||
| W | 7-Mar | ||||
| 11-Mar | Spring Break - No Classes | ||||
| 9 | 9 | M | 18-Mar | Chapter 11 Building Servers as Code |
Chapter 11 |
| 10 | 10 | M | 25-Mar | Chapter 12 Managing Changes to Servers |
Chapter 12 |
| W | 27-Mar | ||||
| 11 | 11 | M | 1-Apr | Chapter 13 Server Image as Code |
Chapter 13 |
| M | 1-Apr | ||||
| 12 | 12 | M | 8-Apr | Chapter 14 Building Clusters as code |
Chapter 14 |
| 13 | 13 | M | 15-Apr | ||
| M | 15-Apr | ||||
| Th | 18-Apr | ||||
| 14 | 14 | M | 22-Apr | ||
| 15 | 15 | M | 29-Apr | ||
| W | 1-May | ||||
| 16 | 16 | M | 6-May | ||
| 16 | W | 8-May |
Course Subjects
| Wk. | Cl. | Day | Date | Lecture | Readings | Lab | Due Dates | Points |
| 1 | 1 | M | 15-Jan | Orientation Big Picture of Network Topology Review of course goals, class policies, etc., i.e. the Syllabus. What is SDN |
Syllabus VMWare Ciena Cisco Juniper Networks ONF |
Assignment 1 | 1/21/2024 | 100 |
| 2 | 2 | M | 22-Jan | How Does SDN Work | How Does SDN Work? How SDN Works Difference Between SDN and Traditional Networks |
Assignment 2 | 1/28/2024 | 100 |
| 3 | 3 | M | 29-Jan | SDN Challenges | SDN Challenges SDN Challenges & Direction SDN Challenges & Effects |
Assignment 3 | 2/4/2024 | 100 |
| 4 | 4 | M | 5-Feb | Chapter 1 What is Infrastructure as Code |
Chapter 1 | Assignment 4 | 2/11/2024 | 100 |
| W | 7-Feb | Review Exercise | 2/8/2024 | 100 | ||||
| 5 | 5 | M | 12-Feb | Chapter 2 Principles of Cloud Age Infrastructure |
Chapter 2 | Exam 1 | 2/13/2024 | 100 |
| 6 | 6 | M | 19-Feb | Chapter 3 Infrastructure Platforms |
Chapter 3 | Assignment 5 | 2/25/2024 | 100 |
| 7 | 7 | M | 26-Feb | Chapter 4 Core Practices: Define Everything as Code |
Chapter 4 | Assignment 6 | 3/3/2024 | 100 |
| 8 | 8 | M | 4-Mar | Assignment 7 | 3/10/2024 | 100 | ||
| M | 4-Mar | Review Exercise | 3/5/2024 | 100 | ||||
| W | 7-Mar | Exam 2 | 3/8/2024 | 100 | ||||
| 11-Mar | Spring Break - No Classes | |||||||
| 9 | 9 | M | 18-Mar | Chapter 11 Building Servers as Code |
Chapter 11 | Assignment 8 | 3/24/2024 | 100 |
| 10 | 10 | M | 25-Mar | Chapter 12 Managing Changes to Servers |
Chapter 12 | |||
| W | 27-Mar | Review Exercise | 3/28/2024 | 100 | ||||
| 11 | 11 | M | 1-Apr | Chapter 13 Server Image as Code |
Chapter 13 | |||
| M | 1-Apr | Exam 3 | 4/2/2024 | 100 | ||||
| 12 | 12 | M | 8-Apr | Chapter 14 Building Clusters as code |
Chapter 14 | Assignment 9 | 4/14/2024 | 100 |
| 13 | 13 | M | 15-Apr | Assignment 10 | 4/21/2024 | 100 | ||
| M | 15-Apr | Review Exercise | 4/16/2024 | 100 | ||||
| Th | 18-Apr | Exam 4 | 4/19/2024 | 100 | ||||
| 14 | 14 | M | 22-Apr | Project | 4/30/2024 | 200 | ||
| 15 | 15 | M | 29-Apr | Final Review | 4/30/2024 | 200 | ||
| W | 1-May | Final | 5/2/2024 | 100 | ||||
| 16 | 16 | M | 6-May | Final | 5/7/2024 | 100 | ||
| 16 | W | 8-May | Final | 5/9/2024 | 100 |
Student Learning Outcomes/Learning Objectives
- Explain the process of converting physical to virtual environments.
- Describe the hardware and software components of a software-defined network.
- Explain the use of code in the infrastructure of the network environment.
- Perform basic configuration of a software-defined network.
- Compare code and physical network environment.
- Plan and configure a software-defined network.
- Implement a software-defined network.
Office Hours
Published: 01/12/2024 21:22:54