Saturday, June 3, 2017

Docker on OpenStack with Kubernetes

Why Docker?
1.Performance
2. Repeatability
3.Isolation
4.Quality of Service
5.Accounting
6.Visibility
7.Portability

Container Cluster Orchestration:
1.Docker
2.Kubernetes
3.Container Engine

Everything at Google runs in Containers:
1.Gmail
2.MapReduce
3.GFS
4.GCE

Kubernetes:
1.Container Orchestrator
2.Runs Docker containers
3. Supports multiple cloud and bare-metal environment
4.Inspired and informed by Google's experiences and internal systems
5.Open source, written in GO

Primary Concepts:
1.Container: A sealed application package
2.Pod: A small group of tightly coupled containers
3.Controller: A loop that drives current state towards desired state
4.Service: A set of running pods that work together
5.Labels: Identifying metadata attached to other objects
6.Selector: A query against labels, producing a set results.

Implementation Choices:
1. Local Manual
2. Hosted, Google Container Engine
3. Local, OpenStack Murano

Murano: App Management in OpenStack
1.Repeatability in the cloud
2.Consistency across all tenants

What is Murano:
Application level abstraction with
1.Catalog of different applications in different formats
2.Application Object Model
3. Application life-cycle actions
Event model with web hooks
Domain Specific Language for event-driven workflows




No comments:

Post a Comment