to Streamline the Kieker Development Process and Infrastructure - PowerPoint PPT Presentation

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] Thomas F. Düllmann Symposium on Software Performance 2017 Karlsruhe, 2017-11-09 [1] www.wallpapersdb.org/various/vehicles/container-ship-wallpaper-1654.htm

Why we are not done yet.. How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 2 Thomas F. Düllmann, University of Stuttgart

Why we are not done yet.. h How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 3 Thomas F. Düllmann, University of Stuttgart

Continuous Delivery Pipeline Stages Checkout Compile Tests/Checks • Git • Compile • Junit Tests Checkout Sources • Static Tasks • Compile Analysis Tests How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 4 Thomas F. Düllmann, University of Stuttgart

What to do next? • Keep the ship afloat [1] • Find an alternative for SnapCI • Improve infrastructure and processes based on our experiences [1] https://latimesphoto.files.wordpress.com/2011/10/la-fg-new-zealand-spill01.jpg How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 5 Thomas F. Düllmann, University of Stuttgart

What we came up with • Jenkins with pipeline plugin (decision based on a student project) How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 6 Thomas F. Düllmann, University of Stuttgart

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 How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 7 Thomas F. Düllmann, University of Stuttgart

What we did: Kieker LiveDemo LiveDemo • Possible improvements: • automate Ansible runs  docker run -ti -p 80:8080 kieker/livedemo:release • Tests for LiveDemo  Open http://localhost/livedemo  http://demo.kieker-monitoring.net/livedemo How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 8 Thomas F. Düllmann, University of Stuttgart

What we did: Kieker Building Process Jenkins Worker • Possible improvements: • replace automated build • automate Ansible runs How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 9 Thomas F. Düllmann, University of Stuttgart

Lessons learned • If you put things in a container, you need a way to get them out again [1] • Easier and more consistent configuration rollouts with automation tools [1] http://www.hausjournal.net/wp-content/uploads/Dose-ohne-Dosenoeffner-oeffnen.jpg How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 10 Thomas F. Düllmann, University of Stuttgart

What we achieved already LiveDemo How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 11 Thomas F. Düllmann, University of Stuttgart

What we plan to do with Docker • Integration tests • Getting started with Kieker • Docker local build tooling to provide more insight How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 12 Thomas F. Düllmann, University of Stuttgart

Discussion • Further ideas to use Docker in an open-source project • Other technologies that could be helpful How we (plan to) use Docker to Streamline the Kieker Development Process and Infrastructure 17-11-14 13 Thomas F. Düllmann, University of Stuttgart