Thomas F. Düllmann

Symposium on Software Performance 2017

Karlsruhe, 2017-11-09

Institute of Software Technology

Reliable Software Systems Group (RSS)

Don‘t just watch the Containers pass by:

How we (plan to) use Docker to Streamline the Kieker

Development Process and Infrastructure

[1]

[1] www.wallpapersdb.org/various/vehicles/container-ship-wallpaper-1654.htm

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

2

Why we are not done yet..

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

3

Why we are not done yet..

h

Continuous Delivery Pipeline

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

4

Checkout

• GitCheckout

Compile

• Compile Sources

• Compile Tests

Tests/Checks

• Junit Tests

• Static Analysis

Stages

Tasks

What to do next?

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

5

• Keep the ship afloat

• Find an alternative for SnapCI

• Improve infrastructure and processes based on our experiences

[1]

[1] https://latimesphoto.files.wordpress.com/2011/10/la-fg-new-zealand-spill01.jpg

• Jenkins with pipeline plugin (decision based on a student project)

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

6

What we came up with

Why (even more) Docker?

• General

• Fixed state/setup

• Independent from OS, IDE, configuration

• Users

• Provide prepared setups with low effort

• Developers

• Predefined/unified environment reproducibility

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

7

• Possible improvements:

• automate Ansible runs

• Tests for LiveDemo

What we did: Kieker LiveDemo

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

8

LiveDemo

docker run -ti -p 80:8080 kieker/livedemo:release

Open http://localhost/livedemo

http://demo.kieker-monitoring.net/livedemo

What we did: Kieker Building Process

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

9

• Possible improvements:

• replace automated build

• automate Ansible runs

Jenkins Worker

Lessons learned

• If you put things in a container, you need a way to get them out again

• Easier and more consistent configuration rollouts with

automation tools

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

10

[1]

[1] http://www.hausjournal.net/wp-content/uploads/Dose-ohne-Dosenoeffner-oeffnen.jpg

What we achieved already

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

11

LiveDemo

What we plan to do with Docker

• Integration tests

• Getting started with Kieker

• Docker local build tooling to provide more insight

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

12

Discussion

• Further ideas to use Docker in an open-source project

• Other technologies that could be helpful

17-11-14How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure

Thomas F. Düllmann, University of Stuttgart

13