9. Why Docker?!
(an incomplete list)
• Compatibility with Docker
images (if standardizing or
desiring cross-cloud compat.)
• Dockerfiles provide flexible,
repeatable image building
• Global, multi-cloud image
registry
• Layered images / builds
• Completeness of vision
10. Five major use cases
• Alternative form of virtualization for multi-tenant services!
• Continuous Integration/Continuous Delivery:!
• Go from developer’s laptop, through automated test, to production, and through
scaling without modification!
• Scale-out/Big Data:!
• Rapidly scale same application across hundreds or thousands of servers…and scale
down as rapidly!
• Cross Cloud Deployment!
• Move the same application across multiple clouds (public, private, or hybrid) without
modification or noticeable delay!
• Granular, Loose Security Isolation:!
• Docker simplifies the separation of security concerns. Multiple processes of the same
“application” may run on a host, linked together, sharing resources but within separate
security contexts (SeLinux labels, Linux capabilities, Cgroups, etc)
11. Closer to the Docker workflow
Hybrid-cloud compatible
Scheduled by backing cloud
Integration with other services
Nova features (quota, auth, etc…)
Abstraction layer for other hypervisors
Integrated scheduling
Heat vs Nova!
Comparison
15. Image Management
docker-registry is a proxy
!
users can upload through docker-
registry or to glance directly
!
docker pulls images through the
docker-registry proxy
27. Where container == host; for all practical purposes
Host
VM
Linux
VM
Host
Container
Linux
VM
Vagrant
(or other VM devstack environment)
Dockenstack
28.
29.
30.
31.
32. Project
SOLUM
“Convert code into a managed application running
on an OpenStack cloud at the push of a button.”
FROM CODE TO MANAGED APP