Downloaded 37 times
Uploaded byPatrick Chanezon
Docker Enterprise Workshop - Intro
This document provides an overview of Patrick Chanezon's background and interests related to Docker and containerization. Some key points: - Patrick is Chief Developer Advocate at Docker, where he focuses on developer relations and platforms. - His interests include agile development, DevOps, microservices, and using containers and Docker to improve developer productivity and application portability. - He discusses how containers have evolved from early uses in mainframes and virtualization to today's platforms like Docker that make containers a natural fit for modern application architectures like microservices and serverless computing.
More Related Content
Similar to Docker Enterprise Workshop - Intro
Docker Enterprise Workshop - Intro
- 1. Patrick Chanezon Chief DeveloperAdvocate @chanezon The Tao of Docker
- 4. French Polyglot Platforms Software Plumber San Francisco DeveloperRelations @chanezon
- 5. “The future isalready here — it's just not very evenly distributed” William Gibson, Neuromancer
- 6. Dreams of mychildhood
- 7. The Singularity… ina galaxy far far away
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 16.
- 17. Low MTBIAMSH MTBIAMSH (MeanTime Between Idea And Making Stuff Happen)
- 19.
- 20.
- 21.
- 22.
- 23.
- 24. Devops • Cultural movement •Inspired by agile methods • People, Processes & Tools • Continuous delivery • Infrastructure as code • Cross silo collaboration • Small iterations • Feedback loop, measurement Image from Patrick Debois http://www.slideshare.net/jedi4ever/devops-the-war-is-over-if-you-want-it http://www.slideshare.net/jedi4ever/devopsdays-downundervfinal
- 25.
- 26.
- 27. 28 https://blog.docker.com/2014/12/dockercon-europe-keynote-continuous-delivery-in-the-enterprise-by-henk-kolk-ing/ Henk Kolk, ING,DockerCon EU 2014 People, Processes, Products deployment time: 9 months -> 15 min 1500 deployments/week
- 28.
- 29. Cloud La LaLand
- 30. Supta Virasana: posedu hero allonge Le cloud en vrai, ca marche mieux avec des accessoires! En theorie En pratique
- 31. There and backagain: a journey to hybrid/multi cloud
- 32.
- 33.
- 35. History of containerization •1960’s mainframe • 1990’s hardware virtualization • 1990’s OS virt precursors: BSD Jails, Solaris zones • 2006 Cloud IaaS • 2009 platform virtualization (PaaS) • 2013 Docker See @bcantrill’s deck http://www.slideshare.net/bcantrill/docker-and-the-future-of-containers-in-production
- 36. Isolation using Linuxkernel features namespaces ● pid ● mnt ● net ● uts ● ipc ● user cgroups ● memory ● cpu ● blkio ● devices
- 37. Union File Systems& Image Layers
- 40.
- 41. Traditional Micro services ISV / COTSIoT Big Data ML AI ...Serverless Cloud VM Bare Metal Edge Device Docker Platform
- 42. Docker Momentum Docker Hosts 21.0M Growth inDocker job listings 77K% Container downloads 24B Industry Standards
- 43. Enterprise Momentum Portability AgilitySecurity 50% total cost savings
- 44. DEVELOPERS OPERATORS Applications Infrastructure The DockerPlatform in a nutshell
- 45. INDEPENDENCE OPENNESS SIMPLICITY Core Principles ofthe Docker Platform
- 46. Docker Enterprise Edition DockerCommunity Edition containerd 1 2 3 4 The best container development workflow The best enterprise container security and management Native Kubernetes integration provides full ecosystem compatibility Industry-standard container runtime Docker with Swarm and Kubernetes
- 48.
- 49. Docker is buildinga stack to program the Internet CE EEA commercial product, built on a development platform, built on infrastructure, built on standards.
- 50.
- 53.
- 54. Docker Community Edition DevelopersEnterpriseContainer Ecosystem The Docker Innovation Model Docker Enterprise Edition 9,149 Open Source Contributors 8800 PRs/Year
- 55.
- 56. Governance: BDFL ->TSC https://github.com/moby/tsc
- 57.
- 61. containerd An open andreliable container runtime
- 62. containerd 1.0 Dec2017 https://blog.docker.com/2017/12/cncf-containerd-1-0-ga-announcement/
- 63. Early History APRIL 2016Containerd “0.2” announced, Docker 1.11 DECEMBER 2016Announce expansion of containerd OSS project, roadmap to 1.0 Management/Supervisor for the OCI runc executor Containerd 1.0: A core container runtime project for the industry
- 65. runc containerd Why Containerd 1.0? ▪Continue projects spun out from monolithic Docker engine ▪ Expected use beyond Docker engine (Kubernetes CRI) ▪ Donation to foundation for broad industry collaboration ▫ Similar to runc/libcontainer and the OCI
- 66. Technical Goals/Intentions ▪ CleangRPC-based API + client library ▪ Full OCI support (runtime and image spec) ▪ Stability and performance with tight, well- defined core of container function ▪ Decoupled systems (image, filesystem, runtime) for pluggability, reuse
- 67. Requirements - A lacarte: use only what is required - Runtime agility: fits into different platforms - Pass-through container configuration (direct OCI) - Decoupled - Use known-good technology - OCI container runtime and images - gRPC for API - Prometheus for Metrics
- 68. Use cases - CURRENT -Docker (moby) - Kubernetes (cri- containerd) - SwarmKit (experimental) - LinuxKit - BuildKit - FUTURE/POTENTIAL - IBM Cloud/Bluemix - OpenFaaS - {your project here}
- 69. containerd 1.0 factsand figures • 1994 GitHub stars, 401 forks • 108 contributors • 8 maintainers from independents and and member companies alike including Docker, Google, IBM, ZTE and ZJU . • 3030+ commits, 26 releases
- 70. Resources To participate incontainerd: github.com/containerd/containerd • Getting Started with containerd: http://mobyproject.org/blog/2017/08/15/containerd-getting-started/ • Roadmap: https://github.com/containerd/containerd/blob/master/ROADMAP.md • Scope table: https://github.com/containerd/containerd#scope • Architecture document: https://github.com/containerd/containerd/blob/master/design/architecture.md • APIs: https://github.com/containerd/containerd/tree/master/api/. • Learn more about containerd at KubeCon by attending Justin Cormack’s LinuxKit & Kubernetes talk at Austin Docker Meetup, Patrick Chanezon’s Moby session Phil Estes’ session or the containerd salon
- 71.
- 72. Microservice architecture pattern ChrisRichardson http://microservices.io/patterns/microservices.html
- 73. Worker Nodes Docker: anatural platform for microservices Node Manager Node Worker Node Manager Node Manager Node Worker Node Worker Node Worker docker universal control plane trusted registry
- 74.
- 75. Image Registry CI/CD Security scan &sign Traditional Third Party Microservices docker store DEVELOPERS IT OPERATIONS Control Plane Docker EE Platform to Modernize Traditional Apps And Beyond
- 79. The Innovation Challenge AverageIT Spend By Type INNOVATION MAINTENANCE 20% 80% 20% 40% 60% 80% 100% 0% 1% Windows Server 2008 Windows Server 2012 Windows Server 2000 Windows Server 2003 Red Hat, Other Linux, Other OS Server OS Market Share Sources: Bank of America, Spiceworks, SolarWinds 18% 45% 24% 12%
- 80. The Modernization Journey App Existing Application Modern Methodologies Convertto a Docker EE Container Modern Infrastructure Ongoing Innovation
- 82. The Docker ModernizeTraditional Apps POC Program Partner Consulting Services Partner Infrastructure Docker Enterprise Edition Portable Agile Secure Efficient < 5 days + + No Code Changes App Existing Application Convert to a Docker EE container Modern Infrastructure
- 83. Reducing total costsby 50% MTA POC Impact Hybrid Cloud-Ready Portability Agility 2x Faster Security Isolation & Integrity
- 84. 84 KEY CHALLENGES • Accumulatedthousands of apps, 400+ systems of record and 5 infrastructures over 150 years • Difficult to innovate with majority of budget spent on maintenance SOLUTION • Leverage Docker MTA program to modernize the email opt- out app with Docker EE to drive down total costs Docker EE and MTA create self funding model for container adoption -70% VMs -67% Cores 10x Average CPU utilization + + -66% Total Cost of Ownership 593 Applications RESULTS • Modernization of single app completed in 1 day • Applying model to other apps built with same technology • Business case forecasts a 66% cost reduction
- 85. 85 KEY CHALLENGES • Maintenancecosts of managing traditional apps on prem • Code quality was increasingly difficult with outsource software house • App delivery process was too slow for the pace of the business SOLUTION • Leverage Docker MTA program jointly with their trusted partner Accenture App Visibility and Consistency at 50% the Cost RESULTS • 50% savings across all applications • Unified architecture for the first time • New visibility into their outsourced applications
- 86. Container as aService
- 87. After Greenfield CaaS Case Study:ADP DevOps and microservices transformation App Service App Service App A App B Auth …more App Reg Marketplace Logging Auth Session …more App Reg Logging Before App BAuth App Reg Marketplace Logging App Service Application Teams Universal Control Plane App AAuth App Reg Marketplace Logging App Service App BAuth App Reg Marketplace Logging App Service App AAuth App Reg Marketplace Logging App Service Portability Authorization App Registration Session Management Marketplace Integration Logging …more Trusted Registry
- 88. Use Case: DecentralizedCaaS for hybrid and multi cloud portability Private datacenter for regulated apps Central Portal • Provision resources • RBAC to VPC / datacenter • Trusted Registry hosted application templates Cloud for all other apps VPC 1 VPC2 App 1 App 2 App App 1 App 2 App Cloud Portability App Portability
- 89. New Trends inUse Cases
- 90.
- 93. Portable Serverless PlatformsGalacticFog Nuclio Fn OpenFaaS OpenWhisk
- 94. Observability with servicemesh: Istio, Linkerd
- 95.
- 96. What is acontainer orchestrator? Management of containers running in one or more container runtimes
- 97. Docker Enterprise Edition DockerCommunity Edition containerd The best container development workflow The best enterprise container security and management Docker: Now Powered by Swarm and Kubernetes Native Kubernetes integration provides full ecosystem compatibility Industry-standard container runtime
- 98. Test locally onSwarm and Kubernetes Develop with Docker Community Edition on your workstation Deploy to production in Swarm Deploy to production in Kubernetes Docker Community Edition All in one development for Swarm and Kubernetes
- 99. Kubernetes in DockerDesktop
- 100. Docker EE 2.0:A conformant kubernetes distribution
- 101. - Easy HighAvailability provisioning - Cryptographic node identity Features Swarm Support - Registry - Content Trust - Secure Scanning - Clean upstream integration - Full ecosystem compatibility - Role Based Access Control - Authorization, Authentication - Node Segmentation Secure Cluster Lifecycle Secure Supply Chain 100% Interoperability Secure Multi-tenancy Management Dashboard Supported and Certified on Windows Server and Major Linux Distributions Kubernetes Support Docker Enterprise Edition Management for Swarm and Kubernetes
- 102. The Tao ofDocker
- 103. 之道 Tao, TheWay
- 104.
- 105. 无为 Wu-wei, Effortlessaction
- 106. 无为 Wu-wei, Effortlessaction
- 107.
- 108. 自然 Ziran, Naturalness container based Nostate No couplingbounded context
- 109. 无为 Wu-Wei: Modernizetraditional applications without coding The Tao (之道) of Docker 自然 Ziran: create microservice applications with the container platform that started the container revolution
- 110. Penser les transformations Pourvos applicationsdes Enterprises
- 111.
Editor's Notes
- #67 This is compared to “container systems of the past” that were monolithic and tightly coupled Example: hard to reuse components; e.g. take a Docker graphdriver and use it to implement a volume driver
- #87 Towards a Docker Containers as a Service application environment that provides a common interface but separation of concerns for your developers and IT operations team to work together to build, ship and run distributed apps
- #88 ADP operates in a more traditional centralized IT model where IT manages and operates the application and environment ongoing. ADP looked at Docker as they began their transition to DevOps. They were interested in gaining more efficiencies and reuse of code by moving to a shared services model instead of monoliths with a lot of repeat services. ADP has OpenStack for their private cloud and AWS for their public cloud. As part of the transition, ADP would will setup a central marketplace where the shared services apps are available for the app teams. In the ADP example both the environment and ongoing management remains centralized. Use Cases - Transition to Micro services - Enable Dev Ops - CI/CD Why Docker? Need app portability so they can choose to move across AWS / Openstack Agility Streamline lifecycle time to move apps from dev to prod Enable a central repository of “app templates” for common services Portability Support AWS cloud and OpenStack private cloud environments Control Centralized management and control of images, apps and infrastructure Enable secure content lifecycle with integrated image signing and verification
- #90 Towards a Docker Containers as a Service application environment that provides a common interface but separation of concerns for your developers and IT operations team to work together to build, ship and run distributed apps
- #113 George decides to consider his career like a startup