Download to read offline
Uploaded byAshley Roach
One Container, Two Container, Three Containers, Four
Containers provide a way to package and run applications reliably from one computing environment to another. The document discusses how containers helped different teams at an organization overcome challenges with testing, deploying, and managing applications. It introduces containers as a more efficient alternative to virtual machines that allows for continuous integration, high testing throughput, increased server utilization, and microservices architectures. In the end, using containers helped the development, QA, operations, and infrastructure teams work better together and accelerate their software delivery.
More Related Content
![[131] packetbeat과 elasticsearch](https://cdn.slidesharecdn.com/ss_thumbnails/113packetbeatelasticsearch-150914020054-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
![[124] mit cheetah 로봇의 탄생](https://cdn.slidesharecdn.com/ss_thumbnails/124mitcheetah-150914011857-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to One Container, Two Container, Three Containers, Four
![20260201 [FOSDEM] gomodjail - library sandboxing for Go modules.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/20260201fosdemgomodjail-librarysandboxingforgomodules-260201225659-76609ec4-thumbnail.jpg?width=640&height=640&fit=bounds)
One Container, Two Container, Three Containers, Four
- 1. One Container, Two Containers, ThreeContainers Four Ashley Roach -- API Architect – DevNet asroach@cisco.com | @aroach
- 2. • Chapter 1:The situation • Chapter 2: History • Chapter 3: Developers • Chapter 4: Continuous Integration • Chapter 5: Quality Assurance • Chapter 6: Operations • Chapter 7: Microservices • Chapter 8: Conclusion Agenda
- 3.
- 4. My name isAshley. I am the explainer, In the next 10 mins, We talk containers
- 5.
- 6. Let’s meet aweb app Contained within it, you’ll find a db, a front end and back. Source: Docker
- 7. APIs and queues! Postgresand node! Hive and hadoop! Python and go! Look at the matrix! Boy, I don't know...
- 8. Test Ship Regression Black box We musttest and ship! We must black box! We must regress! We must do this in Two hours or less!
- 9. So you canenjoy Our new awesome feature, We need to find Sam, Our QA test leader. https://www.flickr.com/photos/ter-burg/8127253723/
- 10. We need Abeer, OurOps engineer!
- 11. We ask Samto test. He looks with great fury. We nod to Abeer She says in a hurry... https://farm9.staticflickr.com/8044/8127266906_98694498e9_z_d.jpg
- 12. We now doDevOps, We share all our fears. Find a new way To package your gear. http://upload.wikimedia.org/wikipedia/commons/4/4e/Devops.png
- 13. Virt’alize says Sam! Yes,yes! Hip hooray! We needn’t worry ab’t diffr’nce today.
- 14. Yes yes, virt’lize! Yesyes, we must size, Our big boxes To launch our surprise.
- 15. Containers! She shouts. Virtualize,Sam pouts. We suddenly realize There are new routes! Host OS LXC Engine App 1 App 2 Server Bin/Lib Bin/Lib
- 16.
- 17. Containers aren’t new. In’79, Unix V7. The C-groups design.
- 18. Linux Containers, AKA LXC, Setthe bar high. Docker came to be.
- 19. Containers? What arethey? A VM is close. Sans hypervisor, They talk with the host.
- 20. One OS isall. Immutable blocks. Docker is one kind. Containers are rocks.
- 21. You said bestof both. Virtual and 'tainer They can cooexist In your data centers Host OS LXC Engine App 1 App 2 Bin/Lib Bin/Lib Hypervisor Base OS
- 22.
- 23. Meet Tracy, thedev. Her first day is now. She has a new MacBook, And starts to install.
- 24. Npm and git! Mongoand bower! Ember and Grunt! It might take an hour!
- 25. Set this envvar! Oh, I forgot! You need a debugger, To get your box set. https://c2.staticflickr.com/8/7057/6885842505_1138e0a52d_b.jpg
- 26. You must matchthe server. You need to cluster. All these configs! Looming disaster! http://upload.wikimedia.org/wikipedia/commons/3/39/Aus2.jpg
- 27. Abeer speaks up. Goto this wiki! boot2docker will Get you up quickly.
- 28.
- 29. Jenkins is next. Heis our CI. Testing takes so long, I poke out my eyes! We test run in time!
- 30. Says Abeer... "VMs areso bloated. They take time to start. They have a whole OS, And mem’ry runs short." http://commons.wikimedia.org/wiki/File:MemoryRam.jpg
- 31. Abeer talks again, "It’stotally fine With our new Docker We test run in time!
- 32.
- 33. Test Security, Functional andPerf. Now our test mode is All of our turf!
- 34. Pull it fromthe hub. It’s easy to share. Build it like magic. Versioned and not stale. https://jenkins-ci.org/content/official-jenkins-lts-docker-image
- 35. Sam comes around. Nowhe sees the light. He realizes Profit, speed. No fight! https://farm9.staticflickr.com/8054/8127180276_1483a09784_z_d.jpg
- 36.
- 37. Uri is fromOps Think intensity! He wants to increase Compute density
- 38. Uri agrees that VMSare like cows Only few of them Can fit as allows http://upload.wikimedia.org/wikipedia/commons/8/8a/British_White_cattle_in_mobile_pen.jpg
- 39. 10 LXCs now Replace1 VM. Now, that’s density! With servers to trim. http://en.wikipedia.org/wiki/Hedge_trimmer#/media/File:Hedge_Trimming_-_Kolkata_2005-08- 10_02050.JPG
- 40. With servers totrim, Eureka! Uri yells! We now can add Ecommerce that scales.
- 41.
- 42. In software engineering Welike to abstract By breaking it up, Risk doesn’t get jacked. http://upload.wikimedia.org/wikipedia/commons/5/5d/Stapel_bakstenen_- _Pile_of_bricks_2005_Fruggo.jpg
- 43. No! No Monoliths! No!No more curses! Yes! Yes! Loosely coupled. Yes Microservice! http://upload.wikimedia.org/wikipedia/commons/6/61/Murten_Monolith.jpg
- 44. Now, what doesit mean? A micro-serv-ice. Break up our product And, man, is that nice! https://www.flickr.com/photos/psd/13109673843
- 45. Each part canbe patched. Their scope can narrow. Indeed micro teams, More lithe and more agile!
- 46. Chapter 8: InConclusion
- 47. We met Sam Wemet Tracy We met Jenkins We met Uri
- 48. Now the teamachieves… Yes! Velocity! Yes! Optimal speed! Compute Density!
- 49. QA and CI, Devand Ops party. Containers can help EVERYBODY!
- 50.