linux containers - the future of iaas
DESCRIPTION
Linux Containers are a new type of cloud server that scales automatically according to server load. They are a recent development, made possible by the latest changes to the Linux mainline kernel. It makes technologies such as Elastic Containers, Docker and LXC possible. Read more at http://www.elastichosts.co.uk/cloud-servers/elastic-containers/TRANSCRIPT
Linux Containers:The Future of IaaS
Richard Davies – Founder & CEO
There’s a buzz about Linux Containers
Recent mainline kernels (3.8+) supportcontainers, using namespaces and cgroups
Userspace tools for running containers,equivalent of hypervisor tools like QEMU
Rapid, automated deployment ofapplications in containers
A u to - S c a l i n g L i n u x C o n ta i n e rs & V M s
But what are Linux Containers?
A u to - S c a l i n g L i n u x C o n ta i n e rs & V M s
Virtualization vs. Containers
A u to - S c a l i n g L i n u x C o n ta i n e rs & V M s
Containers are still isolated but share the host OS kernel
Traditional VMs each run their own guest OS kernel
How do Containers beat VMs?
Automatic scaling• No fixed size specified at boot• Fine-grained scaling of CPU, RAM, etc as needed
Bare metal performance• No hypervisor overhead• Fast userspace-only boot
Efficient use of hardware ( = lower IaaS price)• Idle containers don’t reserve hardware resources
(= don’t pay IaaS fees for idle cloud servers)A u to - S c a l i n g L i n u x C o n ta i n e rs & V M s
Load varies on typical servers
A u to - S c a l i n g L i n u x C o n ta i n e rs & V M s
9:009:30
10:0010:30
11:0011:30
12:0012:30
13:0013:30
14:0014:30
15:0015:30
16:0016:30
17:0017:30
18:000
1
2
3
4
5
6
Memory Needed / GB
- Website link shared on Twitter
- Month-end financial run
- Etc, etc
Most users don’t adjust server size
A u to - S c a l i n g L i n u x C o n ta i n e rs & V M s
9:009:30
10:0010:30
11:0011:30
12:0012:30
13:0013:30
14:0014:30
15:0015:30
16:0016:30
17:0017:30
18:000
1
2
3
4
5
6
Memory Needed / GB
Memory Provi-sioned / GB
Over-paying Over-paying
Slow
Server size adjustment is inaccurate
A u to - S c a l i n g L i n u x C o n ta i n e rs & V M s
9:009:30
10:0010:30
11:0011:30
12:0012:30
13:0013:30
14:0014:30
15:0015:30
16:0016:30
17:0017:30
18:000
1
2
3
4
5
6
Memory Needed / GB
Memory Provi-sioned / GB
Over-paying Over-paying
Over-paying
Slow
Add extra server or expand existing server in crude, imprecise step after load spike starts
Remove extra server or shrink existing server in crude, imprecise step after load spike finishes
Containers auto-scale continuously
A u to - S c a l i n g L i n u x C o n ta i n e rs & V M s
9:009:30
10:0010:30
11:0011:30
12:0012:30
13:0013:30
14:0014:30
15:0015:30
16:0016:30
17:0017:30
18:000
1
2
3
4
5
6
Memory Needed / GB
Memory Provi-sioned / GB
Never over-paying50% cost saving for typical cloud server workloads
Never slowContinuous high performancesince neverunder-provisioned
Fully automatic scalingNo admin work or tools required
Will containers crush virtualization?
A u to - S c a l i n g L i n u x C o n ta i n e rs & V M s