an introduction to rancher

J U L Y 2 0 1 6#RancherRules

Conner SwannDevOps EngineerhiQ Labs

‘s


WHAT IS THE PROBLEM?

▶Many businesses rely on software to function ▶Many businesses sell hosted software to customers (SaaS)


WHAT IS THE PROBLEM?▶ More often than not, software is difficult to update

▶ Requires many steps▶ Requires lots of typing on a keyboard

▶ Deployments are a nightmare if not thought out well in advance▶ Deployment procedure can change as code evolves


SERIOUSLY? THIS IS A PROBLEM? ▶ Devon the DevOps Engineer is trying to deploy the product, but the

dependencies changed and nobody documented it.▶ Evan the Engineer wants to share his build with coworkers, but the only

way is for them to pull the code and run it locally. ▶ Sam the SysAdmin updated a package on the server. Unbeknownst to him,

the software relies on an older version of that package and stops working.


SOMETHING’S GOT TO GIVE - CONTAINER REFRESHER

▶ Software Containers ~> Shipping Containers▶ Step 1: Get the stuff into the container▶ Step 2: Transport the container

▶ Everything you need stays inside the container▶ Update? Make a new container.▶ Abstraction. Abstraction. Abstraction.


RANCHER: WRANGLE YOUR CONTAINERS

▶Rancher is a Container Orchestration Platform

Orchestrate (verb)[awr-kuh-streyt]Automated coordination of an organization's custom-defined DevOps processes, the automation tools, and the tasks those tools carry out.




With that in mind…




makes things happen with containers.


ANATOMY OF RANCHER▶Rancher deals with pools of “resources”

▶Linux Hosts▶Hosts can be a virtual or physical machine▶Rancher Doesn’t Expect Much

▶CPU▶Memory▶Hard Disk Storage▶Network


ANATOMY OF RANCHER: VOCABULARY

▶“Host” ~> “Linux Server”▶“Pool of Resources” ~> “Environment”▶“Running Container(s)” ~> “Service”▶“Group of Containers” ~> “Stack”


ANATOMY OF RANCHER

▶Rancher facilitates a:Microservice-Oriented Architecture


QUICK TANGENT: MICROSERVICES

▶Monolithic Application▶All functionality in single process▶Scales by replicating the monolith


QUICK TANGENT: MICROSERVICES

▶Microservice-Based Application▶Functionality split across several processes▶Scales by distributing the processes to

servers as-needed


RANCHER ARCHITECTURE



▶Makes container-based deployments a breeze▶Supports other orchestration solutions

▶Making it fit is easy▶Abstraction! Experimentation!

▶That and so much more!


RANCHER: HOW DOES THIS AFFECT ME?

▶Microservice-Oriented Architecture▶Sharing builds is simple and automated▶Services are easy to stage and check for faults▶Software faults are easier to diagnose and fix


QUESTIONS?

▶I can answer questions now!


THANKS FOR LISTENING!

▶Bring value to the shareholders!

an introduction to rancher

Technology