cloud hybridation leveraging on docker 1.12

Adrien BlindDevOps Coach@adrienblind

Ludovic Piot, OxalideConseil, architecture, DevOps@lpiot

Usecase: cloud hybridationleveraging on Docker 1.12

@adrienblind @lpiotPlease twit us on #experiences !

On-demand & pay-per-use

DevOps compliant : easy automation, Infra-as-code, versionnable, reproductible

Leads to new usecases: elastic applications, ephemeral environments…

The cloud is sexy


Versatile resources Fail-over through distributed architecture Rebuild vs. restore Frequency of reinstall

Pay per-use but… low perf/cost ratio load-balancing network-based architecture : asynchronous

architecture

A cloudy picture


Security No network peripheral security New organisation-based security model

Managed services very appealing but… vendor lock-in consequences on project/prod collaboration

Keep a decent ROI on recent on-premise assets

A cloudy picture


Docker benefits‘’A universal, self-sufficient and standard artifact embedding an app module,

and its subsequent infrastructure configuration’’

Docker provides both the artifact and the ecosystem to handle it!

Immutable

Portable Lightweight

Incremental

Versionned/taggedDisposable


Topology & orchestration

App 3

App 2

App 1

X64/WIN X64/LINUX ARM/LINUX

An app is made of several atomic containers

Compose, Bundle & Service enable to manage topologies of containers accross a single cluster of nodes

Docker should support ARM & Windows enabling to describe various types of assets in the topology

Third-part assets may be handled artificially through abassador containers


Span a cluster over providers

Extend your network up to cloud vendors platform (VPN, dedicated connections…)

Set up an hybrid docker swarm cluster on top of this various commodites

NETWORK

Host


Scale the application through docker services

Scale the swarm cluster capacity

Scale up, scale down

BEWARE OFAPP ARCHI !



Demo


Architecture

Raspberry(ARM)

Win 2016SWARMCLUSTER

Load injector (Apache AB) IIS Website MySQL Backend Overlay network

LinuxX86_64

LinuxX86_64

LinuxX86_64

LinuxX86_64

LinuxX86_64

INTERNET (arg!)

REDIS


Have a look on the running cluster

Scale the cluster with docker-machine

Scale the app with docker service

Focuses


A real, hybrid clusterARM/Linux

x86_64/Linux

x86_64/Winx86_64/Linux


Spawning docker services


Scale up & down



Conclusion


Docker offers a nice opportunity to create an abstraction layer to facilitate transition to the cloud

Hybridation facilitates composite orchestration… when it’ll be fully operational

Conclusion


Step 1 Shift to docker packaging pardigmes Start deploying your apps through docker (trough CD pipelines

for instance) Step 2

Shift to dynamic orchestration: swarm cluster handles container deployments over the cluster, ensures desired instances are up, etc.

Step 3 Extend your local own cluster to third-part vendors

Step 4 Shift to self-healing clusters (autoscaling nodes for instance)

Plan your migration



Thank you!

cloud hybridation leveraging on docker 1.12

Technology