Mordernizing Traditional Applications. An Introduction to Containerization
- 1. Modernizing Traditional Application An Introduction to Containerization Oluwadamilare Ibrahim Technical Consultant (Enterprise Application Development & DevOps) Wragby Business Solutions and Technologies Limited.
- 2. Challenges between developers and IT Developers IT I need to create applications at a competitive rate without worrying about IT. I need to manage servers and maintain compliance with little disruption. New applications run smoothly on my machines but malfunction on traditional IT server. I’m unsure of how to integrate unfamiliar applications, and I require help from developers. My productivity and application innovation become suspended when I have to wait on IT. I’m unable to focus on both server protection and application compliance.
- 3. Balancing innovation and control How do you empower developers to create innovative applications at a competitive rate without disrupting IT’s ability to manage servers and maintain control? Containers
- 4. What is a container? Containers Traditional virtual machines = hardware virtualization VM VM VM Application OS Hardware Hardware OS OS Applications Kernel = Operating system virtualization Container Container Container Windows Server containers Maximum speed and density Container Container Container Kernel Hyper-V containers Isolation plus performance Hyper-V Container Kernel Container Kernel Container Kernel
- 5. Container benefits Anewapproachtobuild,ship,deploy,andinstantiateapplications Applications traditionally built and deployed onto physical systems with 1:1 relationship. New applications often require new physical systems for isolation of resources. Higher consolidation ratios and better utilization. Faster app deployment than in a traditional, physical environment. Apps are deployed into VMs with high compatibility success. Apps benefit from key VM features, such as live migration, HA. Package and run apps within containers. Key benefits Further accelerate app deployment. Reduce effort to deploy apps. Streamline development and testing. Lower costs associated with app deployment. Increase server consolidation.
- 6. Container overview Dependencies: Every application has its own dependencies which include both software (services, libraries) and hardware (CPU, memory, storage). Virtualization: Container engine is a lightweight virtualization mechanism which isolates these dependencies per each application by packaging them into virtual containers. Shared host OS: Processes in containers are isolated from other containers in user space, but share the kernel with the host and other containers. Flexible: Differences in underlying OS and infrastructure are abstracted away, streamlining ‘deploy anywhere’ approach. Fast: Containers can be created almost instantly, enabling rapid scale-up and scale-down in response to changes in demand. Container App A Bins/Libraries App B Bins/Libraries Host OS w/Container Support Server
- 7. Containers offer unique capabilities Fast iteration Resource controls Rapid deployment Defined state separation Immutabilit y
- 8. Containers Howdotheydifferfromvirtualmachines? Dependencies: Each virtualized app includes the app itself, required binaries and libraries and a guest OS, which may consist of multiple GB of data. Independent OS: Each VM can have a different OS from other VMs, along with a different OS to the host itself. Flexible: VMs can be migrated to other hosts to balance resource usage and for host maintenance, without downtime. Secure: High levels of resource and security isolation for key virtualized workloads. Hypervisor Guest OS Guest OS Virtual Machine App A Bins/Libraries App B Bins/Libraries Server
- 9. Containers inside virtual machines Deploymentoptionssuitedtomanyscenarios Containers in VMs: By combining containers with VMs, users can deploy multiple, different VM operating systems, and inside, deploy multiple containers within those guest OSs. By combining containers with VMs, fewer VMs would be required to support a larger number of apps. Fewer VMs would result in a reduction in storage consumption. Each VM would support multiple isolated apps, increasing overall density. Flexible: Running containers inside VMs enables features such as live migration for optimal resource utilization and host maintenance. Hypervisor Guest OS Guest OS w/ Container Support Virtual Machine App A Bins/Libraries App A Bins/ Libraries Server App B Bins/ Libraries Container
- 10. Docker +Windows server = Windows Containers Anatomyandkeycapabilities Build: Developers will use familiar development tools, such as Visual Studio, to write apps to run within containers. By building modular apps leveraging containers, modules can scale independently, and be updated on independent cadences. Run: Container capabilities built into Windows Server. Manage: Deploy and manage containers using PowerShell, or using Docker. Resources: Define CPU and memory resources per container along with storage and network throughput. Network: Provide NAT or DHCP/static IP for network connectivity. Host OS with container support Server (Physical or Virtual) Web tier LOB app (+Binaries) Container A App tier LOB app (+Binaries) Container B DB tier LOB app (+Binaries) Container C Libraries (Shared across containers) Libraries
- 11. Hyper-V containers = Docker + Windows Server Anatomyandkeycapabilities Consistency: Hyper-V containers use the same APIs as Windows Server containers ensuring consistency across management and deployment toolsets. Compatibility: Hyper-V containers use the exact same images as Windows Server containers. Strong isolation: Each Hyper-V container has its own dedicated copy of the kernel. Highly trusted: Built with proven Hyper-V virtualization technology. Optimized: The virtualization layer and the operating system have been specifically optimized for containers Hypervisor Server Windows Guest OS Optimized for Hyper-V container Hyper-V container App B Bins/Libraries Windows Guest OS Optimized for Hyper-V container Hyper-V container App A Bins/Libraries
- 13. BUILD, SHIP AND RUN Dockerfile, Docker Build, Docker Run
- 14. Dockerfile
- 15. Azure Container Services • Azure Container Services are built to be an easy-to-install, best practice, scalable approach for deploying containers in cloud service provider. • Azure Container Services uses Docker Swarm and/or DC/OS (based on Apache Mesos) to orchestrate the deployment of containers on Azure.
- 16. DEMOs
- 17. Questions