Real dev ops with containers
Download as PPTX, PDF1 like470 views
The document discusses container technology, specifically focusing on the distinction between operating system virtualization through containers and traditional hardware virtualization using virtual machines. It outlines components like Docker Engine, container orchestration tools, and the use of control groups and namespaces for managing containers on both Windows and Linux platforms. Additionally, it emphasizes the benefits of packaging applications with their dependencies for consistent deployment across various environments.
Real dev ops with containers
- 2. Containers
- 4. Server Host OS Hypervisor Server Host OS Docker Engine Guest OS Guest OS Guest OS Bins/Lib s Bins/Lib s Bins/Lib s App A App A’ App B Bins/Libs Bins/Libs AppA AppA’ AppB AppB’ AppB AppB’ AppB AppB’ Guest OS Bins/Lib s App B’
- 9. Containers = Operating system virtualization ContainerContainerContainer Traditional virtual machines = hardware virtualization VM VM VM Windows Server containers No different from Linux containers Container Container Container Hyper-V containers Isolation plus performance Container Container Container
- 12. Docker Platform Specific Platform Independent Linux Control Groups cgroups Namespaces Pid, net, ipc, mnt, uts Layer Capabilities Union Filesystems: AUFS, btrfs, vfs, zfs*,DeviceMapper Other OS Functionality Containerd + runC Docker Engine REST Interface libcontainerd graphlibnetwork plugins Windows Control Groups Job objects Namespaces Object Namespace, Process Table, Networking Layer Capabilities Registry, Union like filesystem extensions Other OS Functionality Compute Services Docker Client Docker SwarmDocker Compose Docker Registry
- 13. Real DevOps with Containers
- 14. Package an application and its dependencies Everything-as-code Consistency across development, test, & production Package once, run everywhere Same tooling for both Linux & Windows
- 15. Cloud Microsoft Azure On premises Third party Frameworks & Langages .Net PHP C++ JavaRuby Win32 Go Perl Python JavaScript Node Virtual Machines Containers Orchestrator Service fabric, Swarm, Kubernetes, DC/OS, Red Hat Open Shift…
- 16. Devs Develop the application Build a Docker image Push the image into a registry Ops Pull the image from a registry Composition, Configuration as Code, Execution Monitoring
- 17. … … … … … … Container Service Service Fabric Batch App Services Coming soon Build/CI, Integrate, Test 3. 1. Outer-Loop Push Code Production environments Run, Manage 5. 6. Code Run Validate Debug Inner-Loop CD, Deploy 4. Visual Studio Team Services Source Code Control (SCC) 2. Container Registry Azure
Editor's Notes
- #10: VM’s include application, necessary binaries and libs and an entire guest OS – all of these add up to tens of GB’s in size Containers include the app and all its dependencies, but share kernel with other containers. Run as isolated process on the host OS. Not tied to any infra , docker containers run on any computer, on any infrastructure and on any cloud. Containers do not provide sufficient isolation for many workloads. Hyper-V containers (Windows only) provide the same level of isolation has Hyper-V VMs but with minimal additional overhead compared to containers. The container itself is the same binary object whether you run as a Hyper-V container or a normal container.
- #13: Linux containers have been around for many years and consist of cgroups, namespaces, layers and a few other bits Docker built an engine that provides an API on top of these kernel technologies. They also built a bunch of tools that make it easy to work with containers via this API. For Windows Server Containers the Windows team added a “Computer Services” layer that provides similar features in the Windows Kernel. They then worked with Docker to port the open source Docker Engine to Windows. The API remains unchanged and thus all the existing tooling works across both Windows and Linux containers.