Docker, DevOps, & Deployments

1. Course Description
2. Course Specifics
3. Prerequisites
4. Learning Outcomes
5. Schedule
6. Class Assignments
   1. Tutorials
   2. Projects
   3. Final Exam
7. Evaluation
8. Attendance
9. Make School Course Policies

Course Description

In this course students will learn the two main flavors of Developer Operations (DevOps), one that uses containers and one that does not. Students will learn the leading container pattern with Docker and explore the pros and cons of containers by implementing them. Students will also learn about DevOps without containers using AWS and S3 tools. The course will tie both these patterns together with generic patterns of operation, such as environmental design, development controls, and uptime management.

Course Specifics

Weeks to Completion: 7
Total Seat Hours: 37.5 hours
Total Out-of-Class Hours: 75 hours
Total Hours: 112.5 hours
Units: 3 units
Delivery Method: Residential
Class Sessions: 14 classes, 7 labs

Prerequisites

• BEW1.1
• BEW1.2

Learning Outcomes

Students by the end of the course will be able to ...

1. Identify & Describe
2. Explain
3. Compare & Contrast
4. Design & Implement
5. Practice

Schedule

Course Dates: Tuesday, April 2 – Thursday, May 16, 2019 (7 weeks)

Class Times: Tuesday and Thursday at 3:30–5:20pm (14 class sessions)

Class	Date	Topics
1	Tuesday, April 2	[Lesson 1]
2	Thursday, April 4	[Lesson 2]
3	Tuesday, April 9	[Lesson 3]
4	Thursday, April 11	[Lesson 4]
5	Tuesday, April 16	[Lesson 5]
6	Thursday, April 18	[Lesson 6]
7	Tuesday, April 23	[Lesson 7]
8	Thursday, April 25	[Lesson 8]
9	Tuesday, April 30	[Lesson 9]
10	Thursday, May 2	[Lesson 10]
11	Tuesday, May 7	[Lesson 11]
12	Thursday, May 9	[Lesson 12]
13	Tuesday, May 14	Final Class (presentations, etc)
14	Thursday, May 16	Final Exams/Presentations

Class Assignments

Tutorials

Tutorials are to help you get started in a topic. They are graded on completion only.

• MakeSwarm Tutorial

Projects

All projects will require a minimum of 10 commits, and must take place throughout the entirety of the course.

• Good Example: 40+ commits throughout the length of the course, looking for a healthy spattering of commits each week (such as 3-5 per day).
• Bad Example: 10 commits on one day during the course and no others. Students who do this will be at severe risk of not passing the class.
• Unacceptable Example: 2 commits the day before a project is due. Students who do this should not expect to pass the class.

Why Are We Doing This?

We want to encourage best practices that you will see working as a professional software engineer. Breaking up a project by doing a large amount of commits helps engineers in the following ways:

• It's much easier to retrace your steps if you break your project/product/code up into smaller pieces
• It helps with being able to comprehend the larger problem, and also will help with your debugging (i.e. finding exactly when you pushed that piece of broken code)
• It allows for more streamlined, iterative communication in your team, as it's much easier to hand off a small change to someone (updating a function) than a huge one (changed the architecture of the project)

Through this requirement, we hope to encourage you to think about projects with an iterative, modular mindset. Doing so will allow you to break projects down into smaller milestones that come together to make your fully-realized solution.

Final Exam

• Passing the exam is a requirement for passing the class.
• If you have a disability that needs an accommodation such as extended time or a different format, please take advantage of our accommodations program.

Evaluation

To pass this course you must meet the following requirements:

• Complete all required tutorials
• Pass all projects according to the associated project rubric
• Pass the final summative assessment >=75%
• Actively participate in class and abide by the attendance policy
• Make up all classwork from all absences

Attendance

Just like any job, attendance at Make School is required and a key component of your success. Attendance is being onsite from 9:30 to 5:30 each day, attending all scheduled sessions including classes, huddles, coaching and school meetings, and working in the study labs when not in a scheduled session. Working onsite allows you to learn with your peers, have access to support from TAs, instructors and others, and is vital to your learning.

Attendance requirements for scheduled sessions are:

• No more than two no call no shows per term in any scheduled session.
• No more than four excused absences per term in any scheduled session.

Failure to meet these requirements will result in a PIP (Participation Improvement Plan). Failure to improve after the PIP is cause for not being allowed to continue at Make School.

Make School Course Policies

Academic Honesty
Accommodations for Students
Attendance Policy Diversity and Inclusion Policy
Grading System
Title IX Policy
Program Learning Outcomes