What's new in containers
Download as PPTX, PDF1 like77 views
This document discusses strategies for modernizing existing applications, including transforming monolithic applications into microservices, containerizing existing applications, and accelerating new application development. It provides examples of how organizations have benefited from these strategies and highlights tools that can help with the modernization process, such as Docker and Visual Studio 2017 container tools.
![“We love the pristine and predictable environments provided by Windows Server Containers.
Service Fabric brings us a safe and consistent deployment strategy that maximizes uptime. The
marriage of the two in Microsoft Azure gives us unlimited potential.”
– Ralph Feltis, Senior Software Engineer
“With Azure Service Fabric and Windows Containers, we were able to push out [a] new feature
immediately …. That’s a big win for our team and for the airline.”
– Debra Moore, Senior Product Owner](https://image.slidesharecdn.com/newincontainers-170717192553/85/What-s-new-in-containers-10-320.jpg)
![ConvertTo-Dockerfile `
-RemotePath 192.168.1.5c$ `
-OutputPath c:newDockerFile `
-Artifact IIS
# escape=`
FROM microsoft/aspnet:windowsservercore-10.0.14393.693
SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]
RUN Remove-Website 'Default Web Site';
# Set up website: iis-env
RUN New-Item -Path 'C:iisiis-env' -Type Directory -Force;
RUN New-Website -Name 'iis-env' -PhysicalPath 'C:iisiis-env' -Port 8090 -Force;
EXPOSE 8090
COPY ["iis-env", "/iis/iis-env"]](https://image.slidesharecdn.com/newincontainers-170717192553/85/What-s-new-in-containers-16-320.jpg)
What's new in containers
- 2. Debugging existing applications “Fixing” existing applications Adding “features” to existing applications Fixing the feature someone else added Building a new application (maybe… if there’s time)
- 3. Maintaining existing applications Re-deploying existing applications Diagnosing issues with existing applications Troubleshooting issues from feature additions Deploying a new application (maybe… if there’s time)
- 4. We can’t throw out every old app. We can’t stop adding features. We can’t stop maintaining old apps. We can make it easier… We can use new tools/code with existing apps…
- 5. TRANSFORM MONOLITHS TO MICROSERVICES New code and transforming existing code CONTAINERIZE EXISTING APPLICATIONS Containerize for portability, efficiency and reliability ACCELERATE NEW APPLICATIONS Agile cloud native app development
- 7. “By upgrading to Windows Server 2016, we were able to ‘lift and shift’ a key security application into Windows Server Containers, gain the flexibility to run it anywhere, and begin to use microservices to refactor aspects of the application to gain needed scalability.” -Stephen Tarmey, Chief Architect
- 9. Reduce infrastructure and operational cost while moving to Azure and modernizing application architecture
- 10. “We love the pristine and predictable environments provided by Windows Server Containers. Service Fabric brings us a safe and consistent deployment strategy that maximizes uptime. The marriage of the two in Microsoft Azure gives us unlimited potential.” – Ralph Feltis, Senior Software Engineer “With Azure Service Fabric and Windows Containers, we were able to push out [a] new feature immediately …. That’s a big win for our team and for the airline.” – Debra Moore, Senior Product Owner
- 12. TRANSFORM MONOLITHS TO MICROSERVICES New code and transforming existing code CONTAINERIZE EXISTING APPLICATIONS Containerize for portability, efficiency and reliability ACCELERATE NEW APPLICATIONS Agile cloud native app development
- 13. Visual Studio 2017 Container tools
- 16. ConvertTo-Dockerfile ` -RemotePath 192.168.1.5c$ ` -OutputPath c:newDockerFile ` -Artifact IIS # escape=` FROM microsoft/aspnet:windowsservercore-10.0.14393.693 SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] RUN Remove-Website 'Default Web Site'; # Set up website: iis-env RUN New-Item -Path 'C:iisiis-env' -Type Directory -Force; RUN New-Website -Name 'iis-env' -PhysicalPath 'C:iisiis-env' -Port 8090 -Force; EXPOSE 8090 COPY ["iis-env", "/iis/iis-env"]
- 17. Open source PowerShell module WIM, VHD, VHDx or Live Servers Roles and Features along with installed programs Internet Information Services (IIS) - HTTP Handlers in IIS configuration - IIS Websites and filesystem paths - ASP.NET web applications Microsoft SQL Server Instances Apache Web Server https://www.powershellgallery.com/packages/Image2Docker/ https://github.com/docker/communitytools-image2docker-win
- 18. TRANSFORM MONOLITHS TO MICROSERVICES New code and transforming existing code CONTAINERIZE EXISTING APPLICATIONS Containerize for portability, efficiency and reliability ACCELERATE NEW APPLICATIONS Agile cloud native app development
- 20. Integrated web management portal Role Based and LDAP/AD Access Control Self-healing and rolling app deploy/upgrade Image scanning, signing & E2E security
- 21. Support for Windows Server Containers and Hyper-V isolation Image deployment and activation Volume driver support Networking and DNS discovery Resource governance https://docs.microsoft.com/en-us/azure/service- fabric/service-fabric-containers-overview
- 22. Alpha Support for Windows Server Containers Control plane runs on Linux nodes, Kubelet/kube-proxy run on Windows Network is achieved using L3 routing Only One Container Per Pod https://kubernetes.io/docs/getting-started- guides/windows/
- 23. TRANSFORM MONOLITHS TO MICROSERVICES New code and transforming existing code CONTAINERIZE EXISTING APPLICATIONS Containerize for portability, efficiency and reliability ACCELERATE NEW APPLICATIONS Agile cloud native app development
- 25. Functions on-premises Preview of Azure Functions Runtime https://aka.ms/azafr
- 30. Host User Mode Container Runtime Hyper-V Isolation Virtual Machine Specifically Optimized To Run a Container Hyper-V Isolation Virtual Machine Specifically Optimized To Run a Container One Docker engine Choice of Linux kernels Yes, this will be on Win10! One container host Any container, regardless of OS
- 32. taylorb@taylorb-pc:/mnt/c/Users/taylorb$_cat /mnt/c/build-announce.txt The Windows Subsystem for Linux (aka Bash) is coming to Windows Server! taylorb@taylorb-pc:/mnt/c/Users/taylorb$ _ _
- 34. Uncompressed container image ~1GB Components not relevant in containers Optional components not layers
- 35. Size at pull: 78 MB Size on disk: 195 MB Removing components not relevant to containers or modern development Optional components are layers
- 36. Mapping named pipes into containers Hot-add of network interfaces Initial support for sharing network interfaces between containers Network overlay support (shipped!)
- 37. License.txt PerfLogs Program Files Program Files (x86) Users Windows C: D: <Path> Container Host License.txt PerfLogs Program Files Program Files (x86) Users Windows <container path>
- 38. License.txt PerfLogs Program Files Program Files (x86) Users Windows <Path> Container Host License.txt PerfLogs Program Files Program Files (x86) Users Windows <container path> File Server fileserver shareC: