running rancher and docker on dev machines - rancher online meetup - may 2016

© 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc .

Running Docker and Rancher Locally on Dev MachinesMay 26, 2016

#ranchermeetup

© 2015 Rancher Labs, Inc.2 © 2016 Rancher Labs, Inc .

Shannon WilliamsCo-Founder/VP Marketing @smw355

Darren ShepherdCo-Founder/Chief Architect @ibuildthecloudFreenode: darren0

#ranchermeetup


Chris UrwinDevOps Lead - UKRancher Labs @containerschris

Mark MatthewsPrincipalARKM Enterprisehttps://uk.linkedin.com/in/mark-matthews-2965501

#ranchermeetup

https://uk.linkedin.com/in/mark-matthews-2965501




First things first…

This is a not a !

#ranchermeetup

© 2015 Rancher Labs, Inc.5

There are rules for a meetup!• We won’t be done on time• Questions are always welcome• There are no bad questions• Demo, then demo some more• Things will break, be patient

#ranchermeetup


Join the conversation on Twitter #ranchermeetup


Agenda• From Dev to DevOps to Dev - Shannon• Running Docker and Rancher Locally on Dev Machines – Chris• Demo: Building a Micro DC - Chris• User Story: Rancher for our Dev Team – Mark• Latest Rancher Update – Darren

#ranchermeetup


Rancher Labs

#ranchermeetup


Building a Container Service

Container Service

Linux Linux Linux Linux Linux Linux


How to deploy a container service

Container Service

Linux Linux Linux Linux Linux Linux

App Catalog

Orchestration

Scheduling

Monitoring

Access Control

Network

Storage

Distributed DB

Registry

Engine

Security

Helm, …

Compose, Kubernetes, Marathon,

Swarm, Kubernetes, Mesos, …

cAdvisor, Sysdig, Datadog, …

LDAP, AD, GitHub, …

DockerHub, Quay.io, …

Docker, Rkt, …

Notary, Vault, …

VXLAN, IPSEC, HAProxy, …

Ceph, Gluster, Swift, …

Etcd, Consul, MongoDB, …


Rancher OverviewMicroservice Catalog

AD/LDAP

Leverage existing tools:- CI/CD- Code

Repository- Monitoring

Environment 1 Environment N…Network Services Storage Services

Container Orchestration and SchedulingUser Mgmt Ops Mgmt

Environment 2


#ranchermeetup

Running Docker and Rancher Locally on Dev Machines

My other data center is this laptop


Problem Statement

“I want my developers and testers to be able to build and test quality code independently; using the same toolset as production uses.”


Some of the problems….• Multiple developers all trying to update

applications at the same time• Scheduling conflicts• No SSL or proxy server• Data quality/consistency issues• Network contention• Environment consistency


A potential solution• Running Docker in the datacentre…run it

locally• Running Rancher in the datacentre…run it

locally• On a local hypervisor (or natively)• Have a common data set • Useful for Developers and testers


What does it look like

MirrorRancher Server

Rancher Agent

Jenkins

DesktopVirtualisation Layer

App Stack

Development VMShared Folders


Demo


How can Rancher help?• Gives visibility of application stack• Can be utilised by less technical resources• Consistency• API and GUI• Load Balancing• Catalog


Demo App

Voting App

Redis queue

Java Worker

DatabaseResults App

Voting App

Voting AppLoad Balancer


Demo


The flow


Benefits of local dev• More representative of production• Distributed build system• Independent development• Moves Developers more to Devopers• Familiarity with tools• Consistency


Limitations• Physical• The more memory the better• The fastest disks you can get• Your imagination…


Don't Bash it out, Compose it We all start with bash script building and

running docker containers We nearly all then use docker-compose instead The iced cake is using Rancher Compose for

scaling and interdependent service stack management

More composition means more reliable scripting How to take full advantage of this?


Mirror Mirror on the Laptop Reduces network contention Pull in the background today for your build

tomorrow A great enabler for fast dev builds Faster dev builds for quicker feedback cycles Low overhead


CI fingers in all the pies Gives a UI for testers - because most teams still

have these Can talk to the host file system, dev box,

rancher box Make sure you sidekick a data volume, thus

direct code refresh from local git Easily switch between projects (stacks off,

stacks on, no need to delete) Easy re-deploy from latest code


Rancher++ Managing containers is a pain, rancher solves

that, so give it to everyone Rancher lets everyone easily see memory, io,

network traffic - early diagnosis More easily test multi-stack systems - don't

leave that to PTL or Prod, solve the pain early Especially for less surprises on your [sticky] session

handling Internal registry trick "localhost:5000/" Same deployment and management tools as

PTL & Prod Low overhead


Thanks! Enquiries to

Mark Matthews [email protected]

Chris Urwin [email protected]

Hand drawn images and the ARKM logo (c) ARKM Enterprises 2016.

mailto:[email protected]

mailto:[email protected]


Latest Rancher Enhancements

31

1.0.1• Rancher Multi-node Simplification

#ranchermeetup

1.1-dev2 • Experimental Mesos support• F5 Load balancer integration• Customizable Docker Machine UI


Getting StartedRancher and RancherOS are in GitHub – Get Involved!

#ranchermeetup

http://github.com/rancher


New eBook: Building a CI/CD Pipeline with Docker & Rancher

http://info.rancher.com/cicd-with-docker-ebook


Thank yourancher.com

#ranchermeetup

running rancher and docker on dev machines - rancher online meetup - may 2016

Technology