cloud foundry vancouver meetup july 2016

Container Microservices:A Holistic Look at Managing Containers for Microservices

© Copyright 2015 Pivotal. All rights reserved.

Overview

• Why Containers?• Exploring Docker and Cloud Foundry• Docker and Cloud Foundry Workflow• Diego Cell and Brain

Why Containers?


• a psychological condition of an operator who has suffered (usually persistent) emotional, or psychological abuse from a problematic CI system.

Why Containers?Battered Continuous Delivery

Ops Syndrome


Environment Parity- run tasks locally before

committing

Configurable- declarative CI (no more

snowflakes)- store in version control

Unpolluted builds- previous builds do not

affect subsequent builds

Usability- visualize pipeline- simple ui (click less!)

Scalability- scale up to increase

performance- scale down to decrease

cost

Example: What if we could...

Exploring ContainerPlatforms


Swarm

9

Router Cloud Controller

BOSH Director BOSH Agent

UAA/Login Servers

Messaging (NATS)

IaaS

Cloud Foundry Elastic Runtime Stack

10



UAA/Login Servers

Messaging (NATS)

IaaS


Container Cells

11

Doppler (Metrics & Logs)



UAA/Login Servers

Messaging (NATS)

IaaS


Container Cells

12

Doppler (Metrics & Logs)



UAA/Login Servers Brain

Messaging (NATS)

IaaS


Container Cells


The Container: Runtime vs No-Runtime

Platform buildpacks provide standard runtime

Platform provides fixed OS container image

Developer brings customized app

Developer brings runtime container image

Developer brings container OS image

Developer brings customized app

Platform provides fixed host OS Kernel

Platform provides fixed host OS Kernel

App container


Back-end Container Stuff

Container Orchestrator Container Engine

docker/docker-engine runC*

Kubernetes/kublet docker-engine -> runC*

Cloudfoundry/garden-linux custom code

Cloudfoundry/garden-runc runC*

*runC – Open Container Initiative reference implementation


CF Root Filesystem

cflinuxfs2

Droplet

Docker

Write layer

• Layered file system in the container namespace

• RootFS changed by pivot root

• RootFS can be either cflinuxfs2 or from a Docker image

• Buildpacks are the Droplet added to the write layer

• Write layer is ephemeral

Write layer

BuildPack Docker


CF Buildpacks Provide Runtime


Concourse.ci Pipelines: Docker-Native CI/CD


Finding The Runtime


Figuring Out How to Add My Application


Creating The Dockerfile


Running the Image

• Cloud Foundry– cf push

• Docker:– docker build– docker push– docker run


Orchestrating PCF Demo Application


Cloud Foundry Manifest


Docker Compose (On Docker-Machine)


Kubernetes


Deploying the Application• Cloud Foundry

– cf create-service– cf push

• Docker– docker-compose up

• Kubernetes– kubectl create -f ./pcfdemo.yml– kubectl create –f ./pcfdemo-service.yml– kubectl create –f ./rabbitmq.yml– kubectl create –f ./rabbitmq-service.yml


Ease of Platform Management

• Installing/Deploying Platform• Monitoring• Configuration• Upgrades


BOSH

• Cloud Foundry is a distributed system that runs on many infrastructures

• BOSH was mainly designed as a holistic approach to deploying and managing Cloud Foundry-managed VMs– BOSH keeps the Cloud

Foundry runtime running

..

.BOSH

Cloud Foundry VMs

Infrastructure


BOSH Architecture


Deploying New Services

• Managing Credentials• Connection Configuration and Metadata• Ease of Adding New Capabilities• Command Line Access• Accessible API


Service Broker API


Architectural Diagram of Services


Examples of Services

• MySQL, RabbitMQ, Redis, and Kafka• Spring Cloud Services: (i.e. Netflix OSS)

– Eureka – Service Registry– Hysterix – Circuit Breaker– ConfigServer – Configuration Service

• Route Services (contributed by GE Predix)– Rate Limiting– Authentication– Caching Services


Logging and Metrics: Two Perspectives

• Application Developers–Access to logs with logging a ticket–Self-service access for diagnostics

• Operations–Understanding the health of the Platform–Insights for Analysis and Capacity Planning


Application Dashboard

• Display current app status, scale, and route

• Streaming Data– last five

minutes of container and network metrics

– most recent app events


Container Metrics Detail

• View app events in context with streaming:– CPU– Disk– Memory

• Viewable by day, hour and minute


Network Metrics Detail

• View app events in context with streaming:– HTTP requests– HTTP errors – Latency

• Viewable by day, hour and minute


Loggregator

• Applications write logs to STDOUT and STDERR

• Relevant Cloud Foundry component events added to application stream

• Log events collected, collated, and expose via API and the Firehose

DeveloperWorkflow


Focus of Cloud Foundry

• Increase Developer Productivity• Speed Application Development• Shorten Feedback Loop• Product Development Focused on Large

Enterprises


PCF Workflow

• Docker and PCF Workflow• PCF (Pivotal Cloud Foundry) Workflow


Initial Docker and PCF Workflow

Select base find/ images Build Artifact Create Dockerfile

Create Manifest

cf create-service Build Docker Image

cf push Check App/Service

Push Docker Image to Registry


Subsequent Docker/PCF Workflow

Build Artifact Rebuild Docker Image

cf restage Push Docker Image to Registry

Check App/Service


Initial Cloud Foundry Workflow

cf create-service Build Artifact

Create Manifestcf push

Check Service/App


Subsequent Cloud Foundry Workflow

Build Artifact cf push

Check App/Service


Services of PCF• Container and Runtime Management

– Native: Complete Container and Runtime– Docker: User brings own Runtime

• Orchestration• Logging and Metrics• Services

– Databases– Message Queues

• Routing– Routing Services


Diego Brain And Cell• Rep

– Auction– Commands to Executor

• Executor– Manages the Container– Decoupled from Container Format

• Garden– Interface that defines Container– Garden-Linux– Garden-runC*– Can be Garden-Windows

• Metron– Manages Logging and Metrics


Gardenallows Diego to programmatically say

“make me a container”

“put this in it”

“then run this”

via a platform-agnostic API


Gardenallows Diego’s abstractions to be flexible


The Open Container Initiative


Values Guiding the OCI Specification

• Composable - Container format not bound to runtime or clients

• Portable – Usable across different HW, OS, Clouds etc• Decentralized – Standard format for referencing images• Minimalist – Spec should focus on doing a few things well• Backward Compatible – Strive to be as backward

compatible as possible with Docker container format

Thank You:Stuart Charlton@svrc

With thanks to @jyidiego for muchof this content

cloud foundry vancouver meetup july 2016

Technology