Don’t talk to strangers: Test isolation with containers
•Download as PPTX, PDF•
0 likes•535 views
Shipping quality products needs tests, tests and tests again. And you'd better automate these! But this is not an easy task. Do your tests fail because of polluted environment? Maybe some environment variables, database records or files are left behind by other processes? Or do they step on each other toes? They run in parallel and use the same files, databases or too much CPU and memory? Do you find it hard to structure your release build? You need to cut final release only for the binaries that passed validation. And in real life validation has to be done for several environments. Join us to understand how the trending containerization technology helps address these problems. We’ll briefly talk about what containers are and what they are used for. To solve portability, parallel execution and resource sharing issues we’ll show you how to run your tests in clean and isolated container environment. Finally we’ll use Concourse CI and Docker images to build pipelines that automate your CI tasks from source code to final release. By the end of the session you will have a general understanding on how to use Docker images and how to build a Concourse pipeline.
More Related Content
What's hot
What's hot (12)
Similar to Don’t talk to strangers: Test isolation with containers
Similar to Don’t talk to strangers: Test isolation with containers (20)
More from Hristo Iliev
More from Hristo Iliev (15)
Recently uploaded
Recently uploaded (20)
Don’t talk to strangers: Test isolation with containers
- 1. Don’t talk to strangers Test isolation with containers Hristo Iliev, Georgi Sabev | SAP Labs 18-19 November, Sofia
- 2. Hristo Iliev ISTAcon.org 18-19 November, Sofia SAP • NetWeaver Application Server Java • SAP HANA Cloud Platform Open Source • Eclipse Virgo • Cloud Foundry (Diego & Abacus)
- 3. Georgi Sabev ISTAcon.org 18-19 November, Sofia SAP • SAP HANA Cloud Platform Open Source • Cloud Foundry (Diego & Abacus)
- 4. Pictures Creative Commons @ Flickr ISTAcon.org 18-19 November, Sofia
- 5. Creating Working Software ISTAcon.org 18-19 November, Sofia Tests Automation Discipline
- 6. Problems ISTAcon.org 18-19 November, Sofia
- 7. Test Pollution ISTAcon.org 18-19 November, Sofia Environment variables Database records Files Programs / libraries
- 8. Resource contention ISTAcon.org 18-19 November, Sofia Processes compete for • CPU • Memory • I/O
- 9. Multiple environments ISTAcon.org 18-19 November, Sofia OS Mobile / Desktop Cloud / Standalone Databases Versions
- 10. Test problems summary ISTAcon.org 18-19 November, Sofia Test pollution Resource contention Multiple environments
- 11. Solutions ISTAcon.org 18-19 November, Sofia Traditional • Dedicated hardware • Virtual machines • Cloud: AWS, Azure New tools
- 12. Containers build, isolate, ship ISTAcon.org 18-19 November, Sofia
- 13. Container: Resource isolation Tenant 1 Tenant 2 Tenant 3 ProcessA ProcessB ProcessC ProcessD ProcessE ProcessF CPU Kernel ISTAcon.org 18-19 November, Sofia
- 14. Container: Resource isolation Tenant 1 Tenant 2 Tenant 3 ProcessA ProcessB ProcessC ProcessD ProcessE ProcessF Kernel A FEDCB ISTAcon.org 18-19 November, Sofia
- 15. Container: Resource isolation Tenant 1 Tenant 2 Tenant 3 ProcessA ProcessB ProcessC ProcessD ProcessE ProcessF CPU Kernel A FEDCB ISTAcon.org 18-19 November, Sofia
- 16. Container: Resource isolation Tenant 1 Tenant 2 Tenant 3 ProcessA ProcessB ProcessC ProcessD ProcessE ProcessF CPU Kernel A FEDCB Linux Kernel ISTAcon.org 18-19 November, Sofia
- 17. Container: Namespace isolation Tenant 1 Tenant 2 Tenant 3 ProcessA ProcessB ProcessC ProcessA ProcessA ProcessB PID, Network, Mount, User Kernel ISTAcon.org 18-19 November, Sofia
- 18. Containerization = Lightweight Virtualization ISTAcon.org 18-19 November, Sofia Operating System Hypervisor Virtual Machine Operating System Bins / libs App App Virtual Machine Operating System Bins / libs App App Container Daemon Container Bins / libs App App Container Bins / libs App App Virtualization Containerization Operating System Hardware Hardware
- 19. Container ? ISTAcon.org 18-19 November, Sofia
- 22. Container ++ Content Processes ISTAcon.org 18-19 November, Sofia Network User cgroups PID Isolation
- 24. Container actions Make me a container ISTAcon.org 18-19 November, Sofia
- 25. Container actions Put this in itMake me a container ISTAcon.org 18-19 November, Sofia
- 26. Container actions Put this in it Run this for meMake me a container ISTAcon.org 18-19 November, Sofia
- 27. Docker ISTAcon.org 18-19 November, Sofia “Build, Ship, Run” Containers • Dockerfile • Docker image • Docker Hub
- 28. Logos ISTAcon.org 18-19 November, Sofia Docker Linux Go lang
- 29. Demo ISTAcon.org 18-19 November, Sofia
- 31. Containers: Pros & Cons ISTAcon.org 18-19 November, Sofia Pros • Isolation • Reproducible environment • Easy to maintain Cons • Multi-platform • Discipline
- 32. Software Production ISTAcon.org 18-19 November, Sofia Complexity Tests Automation
- 34. Popular solutions ISTAcon.org 18-19 November, Sofia Build servers Jenkins Travis … Homegrown
- 35. Concourse CI, Pipelines, Delivery ISTAcon.org 18-19 November, Sofia
- 36. Concourse ISTAcon.org 18-19 November, Sofia Reproducible builds Simple building blocks Docker containers
- 37. Concourse: Concepts ISTAcon.org 18-19 November, Sofia Resources Tasks Jobs Build Job Configure Make Install Source Binary
- 38. Concourse: Pipeline ISTAcon.org 18-19 November, Sofia resource jobvalidated resource
- 39. Demo ISTAcon.org 18-19 November, Sofia
- 41. Concourse: Pros & Cons ISTAcon.org 18-19 November, Sofia Pros • Reproducible environment • Native pipeline support • Release process modeling Cons • Maturity • Scripting
- 42. Q&A ISTAcon.org 18-19 November, Sofia
- 43. Thank you! hristo.iliev@sap.com georgi.sabev@sap.com Hristo Iliev, Georgi Sabev | SAP Labs 18-19 November, Sofia
Editor's Notes
- In order to build quality software we need: Tests so that we know it works as expected Automation that allows us to develop and experiment in a cheap and quick manner -> improve Tools can help alot Discipline is required to keep all that is good and improve further
- In order to build quality software we need: Tests so that we know it works as expected Automation that allows us to develop and experiment in a cheap and quick manner -> improve Tools can help alot Discipline is required to keep all that is good and improve further
- GEORGI All photos except our own images are Creative Commons license
- GEORGI In order to build quality software we need: Tests so that we know it works as expected Automation that allows us to develop and experiment in a cheap and quick manner -> improve Tools can help a lot Discipline is required to keep all that is good and improve further
- GEORGI Everyone want to build quality systems, but it Turns out difficult Following are examples of common pitfalls during testing We will introduce tools that mitigate the presented problems
- GEORGI The first problem we want to present is the test pollution In general pollution is caused by resources left behind (as in real life). These can be env. Variables database/storage/persistence data causing an app/program to appear in certain state files (another form of state) dependencies already present on the machine
- GEORGI Consuming too much cpu/memory causes other leads to starvation for other processes Running tests on the same machine may lead to delays and failures (hard to debug) Not talking for performance but for functional - unit/integration tests
- GEORGI Different Kind of devices (emulators and physical hardware) landscapes (cloud) Backends Libraries / set of dependencies and programs Let’s see how we can solve this …
- GEORGI We’ve seen these 3 problems. Let’s now see how all these problems can be addressed …
- HRISTO Dedicated hardware for Android OS env: AWS (mostly linux), Azure (mostly Windows) Recently a few tools and technologies became popular. Let’s see how they can help solve our issues…
- HRISTO In the past goods were delivered ‘as they are’ – multiple different packages Hard to load/unload on different infrastructures Solution: shipping container Engineers borrowed the same idea Isolation, Standartization, Automation
- HRISTO
- HRISTO
- HRISTO
- HRISTO
- HRISTO
- GEORGI Virtualization emulates all devices (memory, disk, video, ….). We can run different OS-es Containerization allows us to run only a single OS, but is much cheaper and lightweight.
- GEORGI
- GEORGI
- GEORGI
- GEORGI
- GEORGI
- GEORGI
- GEORGI
- GEORGI
- GEORGI Docker is an implementation of the container idea Provides definition of container in “Dockerfile” The container is stored as image The image is stored on a site/repo - Hub
- GEORGI Docker is an implementation of the container idea Provides definition of container in “Dockerfile” The container is stored as image The image is stored on a site/repo - Hub
- HRISTO Run 2 (or more) mvn clean install in parallel to demonstrate they fail Now start a container with Ubuntu to show that containers actually work and show uname Whoami restart does not work –this is not a VM Run 2 containers to show that mvn clean install now works
- HRISTO Now it’s a time for demo. You can find the source, container definition (dockerfile) and the presentation itself in github You can take a picture so you don’t have to remember or write down the address.
- HRISTO Linux only. Windows requires different VM Discipline – cleanup still needed. CPU and memory contention is problem in containers too. This has to be addressed in the same way as with VM/standalone env.
- GEORGI Software is complex- it consists of many moving parts, developed by many teams using multiple technologies Like a car in an assembly line our software needs to pass through multiple stages of build and validation until we have an end product We wan to have this assembly line fully automated -> release often and receive feedback. When producing software we have to: Deal with high complexity Have an ‘assembly line’ like process for testing Have this automated We can do everyting in a container, however we are missing one important concept …
- GEORGI Pipelines can help us reach from build through testing to the final packaging and release of our product
- GEORGI We can use popular solutions with containers Or use homegrown tools However … they all miss the concept of a pipeline and don’t treat it as a first class citizen That’s why ...
- GEORGI CI that understands pipelines Concourse was build by the CF community out of necessity – after experimenting with Jenkins and GoCD
- HRISTO
- HRISTO
- HRISTO Conveyor that accepts resources on the input and after processing/manifacturing outputs releases on the output. Resources: Worker Controller Integration suite Release Final-release Jobs: Worker build & unit test Controller build & mysql test Controller build & postgres test Integration test Deploy
- GEORGI Show our local concourse pipeline and explain what it does Change the source of the example and demonstrate: Concourse picks the change Runs tests in parallel (in containers) Packages and releases the code
- GEORGI Now it’s a time for demo. You can find the source, container definition (dockerfile) and the presentation itself in github You can take a picture so you don’t have to remember or write down the address.
- GEORGI Pros Reproducible environment – configuration in pipeline.yml Native pipeline support – pipeline = resources + tasks & jobs Release process modeling – easy to model the whole (end to end) release process Cons Maturity – not matury. A lot of changes Pipeline management – build & support of pipelines is hard Scripting – a lot of scripting involved in tasks/jobs