KTH DevOps Course

This repository contains the material and content of the DevOps course at KTH Royal Institute of Technology

Registration: You must register to this course through the Swedish registration system https://antagning.se.

Next course start: March 2021 (Academic Period 4).

Past edition:

• KTH DevOps Course 2020
• KTH DevOps Course 2019

Schedule

The schedule is at https://www.kth.se/social/course/DD2482/calendar/

If you can't see any schedule events on the HTML page
Change course rounds/groups in My settings or change the time period above so that it conforms to the course round.

Program

Week 1: Introduction https://kth-se.zoom.us/j/62331342060

• Preparatory reading: "DevOps principles" in https://www.atlassian.com/devops/what-is-devops
• Course introduction Martin Monperrus
  • Your/our expectations
  • Teaching philosophy, teaching values, flipped classroom
  • Team
  • Agenda
  • Grading
  • Communication
  • Infrastructure
  • Relation to Research in Testing & DevOps
• Testimonial from last year's student: Julius Colliander Celik (github) (linkedin) (twitter)
  • How to survive the KTH DevOps course
• Goals: watch the repo, find a first teammate, register one first task as a pull request on this repo.

Week 2 https://kth-se.zoom.us/j/67189910023

• Technical Briefing (B. Baudry)
  • Preparatory material Testing at scale
• Guest Lecture: Continuous Integration Mats Skoglund (Scania). Slides for the guest lecture
• Student presentations

Week 3

• Technical Briefing (M. Monperrus)
• Guest Lecture: Containers Julien Bisconti
  • Preparatory material: Docker tutorial and Awesome Docker
• Student presentations

Week 4

• Technical Briefing (B. Baudry)
• Guest Lecture: MLOps Alex Nodet (King)
  • Preparatory material: IaaS Explained and SaaS Vs PaaS Vs IaaS
• Student presentations

Week 5

• Technical Briefing (M. Monperrus)
• Guest Lecture: Supply-chain security Rhys Arkins (Whitesource)
  • Preparatory material: A 'Worst Nightmare' Cyberattack: The Untold Story Of The SolarWinds Hack
• Student presentations

Week 6

• Technical Briefing (B. Baudry)
• Guest Lecture: Resilient Software Heidi Waterhouse
• Student presentations

Week 7: Michelin Devops Demo Day

• Technical Briefing (M. Monperrus)
• Guest lecture: Devops in Sweden Jörgen Damberg (Zington)
• Browsing and Highlights of Demos

Week 8: Wrap-up, feedback and potluck

• Technical Briefing (B. Baudry)
• 10h15 Lecture: Devops at EA/Dice Cristian Deri, Vidir Reynisson
  • Preparatory material: https://www.youtube.com/watch?v=iIIxgv6CtGs
• 11h15 Proposal and improvement festival for next year
• 12h15 Personalized feedback, final clarifications

Rules

To pass the course, the student has to collect 4 grades:

• The grades are in category: "presentation", "essay", "video demo", "executable tutorial", "contribution to open-source", "course automation", "feedback" (choose four out of them, at most one in the same category, it is not necessary to cover everything).
• The grading criteria page is the unique reference which explains how to pass / pass with distinction.
• The strict deadline for essays, tutorials, contributions to open-source, course automation is April 30, 23h59 Stockholm time; and "demo"; the strict deadline for repeated tasks (all) is May 31, 23h59 Stockholm time.
• The student proposes a category and a topic, which is discussed and accepted by the TA. The proposal is made as a pull-request on this repository. The four graded contributions must have little overlap.
• The same student cannot choose the same topic for two different tasks. The four tasks should cover different aspects of DevOps.
• 4 Pass means a final E, 3 Pass / 1 Distinction means a final D, 2 Pass / 2 Distinction means a final C, 1 Pass / 3 Distinction means a final B, 4 Distinction means a final A
• Group work is encouraged (max 3 persons) but you cannot be with the same persons for more than 2 projects. You can do a work alone for one or at most two projects.
• A failed task requires to pass it again at the end of the course, based on the feedback from the failure. A repeated task cannot be passed with distinction. A task can only be repeated once.
• If the whole course is failed, no grades are kept if the student registers again to the course the year after.
• After a proposal has been merged, the topic of that proposal cannot be changed.

Group Rules

• When you send a pull request for registration, please follow the name convention of using email addresses of two members to create the folder: email-email.
• We recommend 2 students. Three is also possible for ambitious essays, demos or contribution to open-source.

Communication

• All communication for the course DD2482 should be sent to dd2482@eecs.kth.se.
• you create issues here if you think the question is good to be discussed publicly, the rules of netiquette fully apply.

Remote participation

Lectures:

• the lectures will be streamed, the URLs will be posted on KTH#316
• the recording and sharing of streamed lectures (full or fragments) is not allowed without explicit permission of the course professor and lecturer
• the lectures are recorded by the TA team, and privately shared over KTH Box
• questions are asked on shared gdoc (one TA is following the gdoc), no audio remote interruptions are allowed, the Zoom chat is not used.

Lab sessions:

• Lab slots do not require mandatory presence. They are designed for students to meet TA and discuss all questions in person
• During the planned lab time slot, please use this Queue for booking online meetings
• Specify your zoom meeting link when you register the queue
• Our TAs will reach you ASAP

Team

• Prof. Martin Monperrus
• Prof. Benoit Baudry
• He Ye (TA)
• César Soto (TA)
• Deepika Tiwari (TA)
• Khashayar Etemadi (TA)

See also

• KTH Social URL: https://www.kth.se/social/course/DD2482/
• Kopps URL: https://www.kth.se/student/kurser/kurs/DD2482?l=en

Prerequisites

• A software engineering course (eg DD2480)
• A networking course (eg IK2218)