CPSC 489/589-010 DevOps Spring 2024

Week 6 Class 11 Thu Feb 22 Posted: Feb 22

Announcements

• Exercise Scores I am caught up with the exercise scores, except for the optional Entropy.

• Project 1

  I posted my current version of feedback for Project 1 in your GitHub repository. It is in the branch feedback in the file Report.md. Best to view it on GitHub.

  If you can use gh browse, then you can go directly to it:

    gh browse --branch feedback Report.md
  

  If you are using WSL and gh browse cannot open a browser, then you should try to fix that. You are in a DevOps course, and fixing stuff like that is common.

  I will post scores in Brightspace once I am done with them, and will update this page.

  The due date for Project 2 remains the same. However, I will allow changes to your Project 2 (based on feedback from Project 1) until Monday, Feb 26. The basics must be implemented by the original due date.

• Overall Feedback

  • When you are given a list of things to implement, you must take care to do all of them. E.g., Project 1. In many cases, all items in a list may have the same importance.
  • Following conventions and examples is important. Keywords in ssh_config are case insensitive, e.g., host devops, and indentation is not required. I did not know this before grading your exercise (and had to look it up) However, not using the given form, e.g., Host devops, and not indenting will lead to unnecessary confusion, and with some configuration files, the wrong result.
  • Documentation is important. Build and configuration code is often developed and then left for long periods of time, until changes are needed.
  • At every possible point during development of build files, you must check that the build works. Incremental steps with as much full testing as possible.

Agenda

• Exercise 23: DevOpsComplexity CMake III

  Follow along and duplicate my changes to the CMake for the DevOps Complexity program.

  DevOpsComplexityCMake

• Exercise 28: Docker: Build from Local Files

  In an asciinema screencast, show using Docker to build from a local file. This can be any code.

  Make sure to time how long the build takes (after a make clean).

• Exercise 29: Docker: Build Using Another Architecture

  In an asciinema screencast, show using Docker to build a local file from another architecture. So if you are on amd64 (x86), build on arm64, and if you are on arm64 (Apple Silicon), build on amd64.

  Make sure to time how long the build takes (after a make clean).

  In your screencast, echo how much longer it takes as a ration (10x longer, etc.)

All exercises are due by 4:30 pm on Monday, Feb 26