Preparation for O’Reilly Online Learning Course More Effective DevOps Testing

Taught by Cliff Berg

1. Configure Your Computer As a “Developer Machine”

This does not need to be done prior to training, as training will consist of demos; but if the user wishes to replicate what is done during training, then these configurations will be very useful. You do not lose any functionality or compromise your system’s security by doing this - these changes merely make visible features that are present but hidden.

Mac

Tell Finder to show all files

  1. Open a Finder window.

  2. Select Finder -> Preferences

  3. In the “Advanced” tab, select “Show all filename extensions”.

  4. In the menu bar at the top left of the screen, click on the Apple symbol, “select Force Quit”, select “Finder”, and click “Relaunch”.

Note: The Finder will still not show files that it thinks are “system” files - those beginning with a dot (period). If you cannot see those files but need to, press and hold the Shift and Command (⌘) keys, and then press the period key.

Add your drive and your “home” to the Finder sidebar

  1. Open a Finder window.

  2. Select “View”, and then select these:

    1. “Show Path Bar”

    2. “Show Status Bar”

  3. Select “Desktop” on the left (in the Sidebar).

  4. Double click on “Macintosh HD” at the bottom of the Finder (but not in the Sidebar).

  5. On the keyboard, enter “⌘↑” - that is, hold down the “command” key and press the up arrow.

  6. In the Finder list on the right, select “Macintosh HD” and drag it into the Sidebar under “Favorites”.

  7. In the Finder list on the right, double-click on “Macintosh HD”; then double-click on “Users”; then select your user ID and drag it into the Sidebar under “Favorites”. That is your “home” directory.

Install Apple developer command line tools

  1. Find the Terminal app. (The Terminal app is in /Applications/Utilities.) Pin it to your dock.

  2. Double click on the Terminal app: a Terminal window, will open. This is a “Unix shell”. In the window, type,

git

and hit return. A popup should appear, asking, “...Would you like to install the tools now?” - Click “Install”.

  1. Wait for the installation to finish.

  2. Close your Terminal window. (Any open Terminal windows will not have the settings that the tool installation made.)

Windows

Tell File Explorer to show all files

  1. Open File Explorer from the taskbar. 

  2. Select View > Options > Change folder and search options.

  3. Select the View tab and, in Advanced settings, select Show hidden files, folders, and drives and OK.

Install gitbash tools

Instructions here: https://www.techoism.com/how-to-install-git-bash-on-windows/

After these have installed, locate “gitbash” and pin it to your tray for quick access.

2. Installations

These do not need to be installed prior to training, as training will consist of demos; but if the user wishes to replicate what is done in the training demos, these are the tools that are needed.

VirtualBox

Mac

1. Install VirtualBox: https://www.virtualbox.org/wiki/Downloads

This will download a .dmg file, which you then must open, which will unpack into a .pkg installation file, which you then must open to install VirtualBox.

The OS might deny the installation. If it does, open System Preferences and select “Security & Privacy”, and select the “General” tab. Then click on the little lock at the bottom left - it will then ask for your Mac’s password. You should then see something like the following: click “Open Anyway”.

Mac security
        popup - open anyway

Now go back and try again to open the .pkg file.

2. Install VirtualBox “Extension Pack” (same URL from #1)

Windows

Windows 7, Windows 10 Home:

  1. Install VirtualBox: https://www.virtualbox.org/wiki/Downloads

  2. Install VirtualBox “Extension Pack” (same page)

Windows 10 Pro:

Make sure you have “HyperV” enabled, by following these instructions: https://www.vagrantup.com/docs/hyperv/


If your Machine has virtualization disabled:

Some organizations that use Windows machines disable virtualization in the machine’s BIOS settings. If that is the case, you will receive an error when performing the above steps. Unfortunately, the way to configure this depends on the system. Here is an article that might help:

https://www.howtogeek.com/213795/how-to-enable-intel-vt-x-in-your-computers-bios-or-uefi-firmware/

Text Editor

You need a programmer’s text editor. Don’t try to use Wordpad or something meant for editing documents, as they insert hidden characters that will corrupt the files. I recommend Atom: https://atom.io/

Vagrant

https://www.vagrantup.com/downloads.html

Gitlab account

Create a gitlab account: https://about.gitlab.com/

(Note: a basic free account is fine - they try to trick you into creating a paid account)

3. Suggested Preparatory Reading

These are not required, but reading these ahead of time will give the attendee an edge.

Java basics: https://www.tutorialspoint.com/java/java_basic_syntax.htm

For more in-depth coverage: https://learning.oreilly.com/videos/java-programming-basics/9780133975154

Maven overview: https://www.youtube.com/watch?v=bmyOiz2Jjak (an O’Reilly video)

Unix/Linux shell overview: https://docstore.mik.ua/orelly/linux/lnut/ch06_01.htm (chapter 6 of the O’Reilly book Linux In a Nutshell)

Virtualization overview: https://www.tutorialspoint.com/virtualization2.0/virtualization2.0_overview.htm

Containers: https://www.docker.com/resources/what-container

Git overview: https://www.liquidlight.co.uk/blog/git-for-beginners-an-overview-and-basic-workflow/

Cucumber overview: https://en.wikipedia.org/wiki/Cucumber_(software)

DevOps overview: https://en.wikipedia.org/wiki/DevOps