containers vms and clouds
play

Containers, VMs, and Clouds: Containers & Clouds & VMs: OH - PowerPoint PPT Presentation

Containers, VMs, and Clouds: Containers & Clouds & VMs: OH My Oh My! Mike Coleman, Technology Evangelist Docker @mikegcoleman Who Am I? Technology evangelist at Docker Former: Puppet, VMware, MSFT, Intel, and HP First


  1. Containers, VMs, and Clouds: Containers & Clouds & VMs: OH My Oh My! Mike Coleman, Technology Evangelist – Docker @mikegcoleman

  2. Who Am I? • Technology evangelist at Docker • Former: Puppet, VMware, MSFT, Intel, and HP • First half of my career was in IT • Second half in product management and technical marketing • @mikegcoleman (but mostly soccer)

  3. So why are you sitting here today • Containers vs. VMs? • Physical vs Virtual? • Virtual vs. Cloud? • Cloud vs. Physical?

  4. VMs 4

  5. Containers 5

  6. They’re different, not mutually exclusive 6

  7. Just answer the question . . .

  8. Besides, you wouldn’t like the answer http://nextgenerationgardener.blogspot.com/2013/03/building-show-garden-gathering-it-all.html

  9. So many variables • Performance • Security • Scalability • Existing Skillsets • Costs • Etc. http://people-equation.com/do-your-words-encourage-or-deflate/math-equation_chalkboard/

  10. Points to Consider • Capacity • Existing Automation • Mixed Workloads Frameworks • Latency • Resource Pools / Quotas • Disaster Recovery • Multi-tenancy • Licensing Costs

  11. Why even start? • Faster deploy times −Build vs. Run time • Simplified dependencies • Unified tool chain • Identical environments • API automation

  12. Reduce costs and streamline operations Containers and VMs together: App App App App • Optimize: Added flexibility in Bins/Libs Bins/Libs Bins/Libs Bins/Libs using infrastructure resources OS OS OS OS Virtualization Virtualization • Consolidation: Greater workload Before: One service and OS per VM density across existing servers. • Reduce Costs: Lower OS and App App App App VM licensing CapEx and reduce Bins/Libs Bins/Libs Bins/Libs Bins/Libs OpEx costs to support and Docker Engine maintain smaller infrastructure OS Virtualization After: One container per service. Multiple containers running per VM 12

  13. Swisscom 13

  14. Migrate any workload anywhere Infrastructure agnostic platform App App App • Standardize: Docker abstracts Bins/Libs Bins/Libs Bins/Libs away the infrastructure and OS OS OS virtualization away from the standardized app containers • Portability: Containers move without friction from one environment to another – no App App App recoding needed Bins/Libs Bins/Libs Bins/Libs • Lift and Shift: Containerize Docker Engine Docker Engine OS OS legacy and microservices to gain portability 14

  15. Centralized CaaS for DevOps Before After App B App A Application Teams App Service App Service Universal Control Plane Trusted Registry App Service App Service Auth Auth Authorization Auth Logging Auth Logging App B App A App Reg Marketplace App Reg Marketplace App Registration Session App Reg Session Portability App Reg Management Marketplace Marketplace Logging App Service Logging App Service Integration Auth Logging Auth Logging App A App B Logging App Reg App Reg Marketplace Marketplace …more …more …more 15

  16. ING delivers value faster Challenge • 9+ months to deploy to production • Poorly rated applications • Redundant processes and apps Solution • Continuous Integration with Docker Engine and Registry open source and adopt DevOps Benefits • Ready to deploy in 15 minute • 1,500 deployments per week • 180 DevOps teams • CD pipeline transformed in 4 month 16

  17. Gilt deploys over 100X a day Challenge − From dev-to-deploy: weeks − 7 Monolithic apps − Wasted time implementing monolithic IaaS and PaaS Solution − Continuous Delivery with Docker Engine open source and private repos on Docker Hub Benefits − From dev-to-deploy in minutes − 400+ microservices − 100+ innovations a day − Easily burst to cloud burst at peak shopping times 17

  18. Dockerizing Monoliths • Microservices to Monoliths continuum • Monoliths and Microliths • Focus on the real challenges − static configs, fixed ports, multiple processes • Start somewhere . . . • End up somewhere else

  19. Cornell University • First Dockerized App: Confluence – April 2015 • Complicated Tech Stack − Apache 2.2.10 − OpenSSL 0.9.8H − Java 1.6 (EOL 2/13) − Confluence 5.6.5 • Custom code for SSO and LDAP integration • Previous Confluence update took 6 months • Out of synch environments • Brain drain 19

  20. Cornell University – End Product • Infrastructure as code “ . . . Docker can improve the state of • Custom images (rebuilt daily) many applications including legacy and vendor solutions” • CI workflow featuring Jenkins and Docker Trusted Registry - Shawn Bower, Cloud Architect – • Quarterly upgrades Cornell University • 2 Months to Dockerize and move Confluence to the cloud • 10x reduction in staff hours supporting Confluence 20

  21. What’s the Right Tool for the Job?

  22. So, what’s next • Pick a project • Get your hands dirty • Mistakes may (will) be made • Join the community

  23. Thank You! Q&A

  24. Docker Sessions @ LinuxCon - Booth 41! Wednesday Aug 24th Tues Aug 23rd From 1 to N Docker Hosts: Getting Started with Docker Clustering - Mike Goelzer and Victor Vieux Runc: The Little (container) Engine that Could - Phil Estes Highly Available and Distributed Containers - Unikernals: When you Should and When your Shouldn’t - Kendrick Coleman, Docker Captain Amir Chaudhry User Namespace and Seccomp Support in Docker Toronto Docker Meetup Engine - Paul Novarese When the Going gets Tough, Get TUF Going - Riyaz Faizullabhoy Toronto Docker Meetup Thurs Aug 25th Tutorial: Orchestration Containers in Production at Scale with Docker Swarm - Jerome Petazzoni 24

Recommend


More recommend