6. THE RIGHT TECHNOLOGY AT THE RIGHT TIME
• No one ever got fired for running VMs
• Who doesn’t love whales?
• You know your work loads
• There isn’t a problem. Why are we doing this?
6
7. THE CONTAINER VALUE PROP
• Developer productivity
• Portable
• Multi-cloud deployments
• Lightweight orchestration
7
10. CONTAINER STRATEGY
• Leave the monolith alone
• Staying in the “success zone”
• Overlay container orchestration on OpenStack
and AWS
• Had to address container security
10
12. CURRENT STATE OF PLAY
• Kubernetes on OpenStack
• Standard microservice deployment pipeline
• Moving workloads - The big payoff is coming
• CI/CD pipeline overhaul
• Multi-cloud
• Happy Developers
12
13. HERE’S HOW WE DID IT
• First iteration was Kubernetes cluster on
Openstack VMs using static routing to deliver
cluster connectivity.
• This provided a cluster that developers can deploy
apps to and network connectivity to allow external
access to the cluster.
Lithium | Klout - Confidential13
14. BOLTING IT ALL TOGETHER – STATIC ROUTING
Lithium | Klout - Confidential14
15. GREAT! IS THAT ALL?
• How about we utilize the same SDN that powers
our Openstack to run out Kubernetes networking?
• Kubernetes cluster running on Openstack VMs
using OpenContrail as the SDN.
• http://superuser.openstack.org/articles/kubernetes
-and-openstack-multi-cloud-networking
Lithium | Klout - Confidential15
21. WISH LIST
• I would like to use OpenStack APIs to provide
networking, storage, images.
• Provide persistent container storage via Cinder.
• Make Glance/Swift a container registry.
• Container registry as a service.
Lithium | Klout - Confidential21