The evolution of server consolidation – from virtualization to containerization

1. Presentation to WVDE
The evolution of server consolidation –
from virtualization to containerization
Jack L. Shaffer, Jr.
Business Transformation Director
vCIO / vCISO

2. Major shift in computing

3. But first, a history lesson……
 Slow deployment times
 Huge costs
 Wasted resources
 Difficult to scale
 Difficult to migrate
 Vendor lock-in
One Application on one physical
server

4. Virtualization arrives…..
 One physical server can contain
multiple applications
 Each application runs in a virtual
machine (VM)Slow deployment
times
 Better resource pooling – one
machine divided into multiple VM’s
 Easier to scale
 VM’s in the cloud
 Rapid elasticity
 Pay as you go model
Hypervisor-based virtualization

5. Virtualization limitations
 Each VM still requires:
 CPU allocation
 Storage
 RAM
 An entire guest Operating System
 The more VM’s you run, the more
resources you need
 Guest OS means wasted resources
 Application portability not
guaranteed
Hypervisor-based virtualization

6. What’s a “container?”
 Method to run applications in
isolation
 Shared OS kernel
 Eliminates the overhead of an
OS and services
 Standardized packaging for
software and dependencies
 Works with all major Linux
and Windows Server
 Many of the technologies are
older, but haven’t been
packaged in an easy to use
tool kit before Docker

7. Containers vs VM’s
Each virtual machine
Includes:
- application
- binaries and libraries
- entire guest OS
Containers:
- Include application and all dependencies
- Share kernel with other containers
- Run as an isolated process.
Not tied to any specific infrastructure

8. Not simply replacing VM’s
Virtual Machine:
Host Virtualization
Containers are used in
Partnership with current
IaaS stacks.
Docker and other
Container platforms
Still need a host.
Container:
Application Virtualization
Take advantage of the streamlined
Process for VM based IaaS and
Gain efficiencies in:
• Higher density workloads
• Scale
• Portability
• Security
.

9. Docker – the most popular container

11.  Next Generation of virtualization
 Agile – containers can be launched in
seconds
 Speed – containers run faster
 Portability – containers can moved without
alteration between physical servers and even
to the cloud
 Better hardware consolidation – 10x or more
higher consolidation
 Even heavily virtualized datacenters are still
plagued by low server utilization rates, often
below 50 percent.
Why use containers?

12. By simply “containerizing” applications and running the containers
in a single VM (rather than running each application in its own
VM), companies have been able to reduce compute resources by
25 percent or more for the same workloads.
Increase server density
Hosting Cost 983 workloads
in AWS
Cost of the 983 workloads
using Docker containers

13.  For instance, Docker Enterprise can run directly on bare metal
servers with just a host OS — no hypervisor or virtual machines.
 This can reduce compute resource requirements by 45 percent or
more.
 Also reduces the storage footprint by 30 to 35 percent, and RAM
requirements by 7 percent.
More efficient utilization of CPU spend

14. Portability

15. Docker runs everywhere

16. Docker on Windows Server 2016
 98% of enterprise workloads supported by Docker
 Microsoft and Docker formed partnership in 2014
 One Docker platform and one adoption journey for all enterprise
applications and infrastructure
 Windows kernel (both 2016 and Windows 10) now has
containerization primitives
 Microsoft and Docker worked to port Docker Engine to Windows,
all in the open on https://github.com/docker/docker
 Ancillary services like registry, Hub, etc. have multi-arch support,
maintain Linux and Windows Docker images side-by-side
 Docker CS Engine with Windows Server 2016 at no additional
cost

17. Docker and Windows 2016
 Can run native Windows
Server containers
 Or Hyper-V containers

18. Docker strategy
 Create a completely portable
application container
 Docker Compose
 Move between any service –
on premise, Azure/AWS, or
other service provider
 Orchestration of multiple
containers with Docker
Swarm, Kubernetes
 Highly scalable – on demand
 Azure container service

19. Next Steps…
 Resources:
 https://www.docker.com/microsoft
 https://blog.docker.com/2016/09/dockerforws2016/
 https://blog.docker.com/2016/09/docker-microsoft-partnership/
 Try Windows Server 2016 and Docker:
 https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016/
 https://blog.docker.com/2016/09/build-your-first-docker-windows-server-
container/
 https://blog.docker.com/2016/09/image2docker-prototyping-windows-vm-
conversions/

20. The evolution continues!
Configuration
Management
Virtualization Cloud
Computing
Bare Metal Service
Orchestration
Magic!

21. Questions

23. advantage.tech/expert

24. Friis, Michael. “Docker and Microsoft - Windows Server 2016 Technical
Deep Dive.” LinkedIn SlideShare, Docker, 17 Oct. 2016,
www.slideshare.net/Docker/docker-and-microsoft-windows-server-
2016-technical-deep-dive.
“Introduction to Docker - 2017.” LinkedIn SlideShare, Docker, 14 July
2017, www.slideshare.net/Docker/introduction-to-docker-2017.
Brown, Taylor. “Ignite 2016 - Windows Containers.” LinkedIn SlideShare,
Microsoft, 25 Sept. 2017, www.slideshare.net/TaylorBrown36/ignite-
2016-windows-containers.
Citations