everything as code

hart hoovercloud evangelist

Wednesday, August 21, 13

WHAT IS devops?

Culture & Work Methodology

What Does DevOps Enable?

Tooling

Gerrit

Deployment Strategies

Cookbooks

Nodes(chef-client)

ChefServer HTTPS

Workstation

•Nodes: Servers

•Environments: Groups of nodes (Dev/QA/Prod)

•Recipes: Describes the desired state of a node

•Cookbooks: Group of Recipes

•Roles: Group of Cookbooks (Web)

•Attribute: information about the current state of a node

CHEF TOOLS

Test Kitchen

berkshelffoodcritic

Vagrant

Manifests

Agents

PuppetMaster HTTPS

PuppetCA

•Nodes: Servers

•Manifests: Describes the desired state of a node

•Catalog: Group of Manifests

•Facts: information about the current state of a node

PUPPET TOOLS

Test Kitchen - soon

librarian-puppetpuppet-lint

Vagrant

PUPPET vs. CHEF

States

Minions

Master

•Nodes: Minions

•States: Describes the desired state of a node

•Grains: information about the current state of a node

Playbooks

•Hosts: Servers

•Groups: Groups of Hosts (Dev/QA/Prod)

•Play: Describes the desired state of a Host.

•Playbook: Group of Plays

•Roles: Group of Hosts (Web)

•Facts: information about the current state of a Host.

ANSIBLE vs. SALTSTACK

Measure All the Things

CollectD + GRAPHITE

NAGIOS

Windows

Networking

NSClient++

NAGIOS PluGINS

• Application Monitoring Service

• Agent-based

• Plugins

Automate All the Things

SOME OF THESE != SUCCESS

NO CULTURE BUY-IN = NO DEVOPS

SOFTWARE DEVELOPMENT LIFECYCLE

DEV OPS+

DEV OPS+ QA+

DEVOPS

How to Embrace DevOps

SCRUM KANBAN AGILE

Scrum Master

Product Owner Developers

Product Backlog

Sprint Backlog Sprint Working increment

of the software

1. Design

5. QA 2. Build

4. Release 3. Configure

1. Design

5. QA 2. Build

4. Release 3. Configure

SCRUM: KEY MEETINGS

Backlog Grooming

Sprint Planning

Daily Scrum

Sprint Review

Sprint Retrospective

Features In Progress Blocked Tabled Testing Complete

Feature A

Feature B

Feature C

KANBAN

Feature A

Feature B

Feature C

KANBAN

Feature A

Feature B

Feature C

Feature E

Feature D

KANBAN

Feature AFeature BFeature C

Feature E

Feature G

KANBAN

Feature AFeature BFeature C

Feature E

Feature D

Feature F

Feature G

KANBAN

Feature A

Feature B

Feature C

Feature E

Feature D

Feature F

Feature G

KANBAN

Feature A

Feature B

Feature C

Feature E

Feature D

Feature F

Feature G

Feature H

Feature I

KANBAN

Feature A

Feature B

Feature C

Feature EFeature D

Feature F

Feature G

Feature H

Feature I

KANBAN

AGILE DEVELOPMENT

• Individuals and interactions over process and tools

• Working software over comprehensive documentation

• Customer collaboration over contract negotiation• Responding to change over following a plan

AGILE TEAMS

Traditional Teams AGILE Teams

Project Manager /Team Lead

Servant Leader /Facilitator

Self-Organized

CONTINUOUS DELIVERY

Same Problems

What Version is in Production?

Issues are Found, Fixed & Redeployed Quickly

Test as You Develop

Same Best Practices

Tag, Branch & Release Code that Defines Infra

Coverage Lifecycle Over Various Stages

Continuously Test

INDUSTRY STANDARD!

OPEN SOURCE!

THEMES!

INDUSTRY STANDARD!

OPEN SOURCE!

THEMES!

PLUGINS!

INDUSTRY STANDARD!

OPEN SOURCE!

THEMES!

PLUGINS!

INDUSTRY STANDARD!

OPEN SOURCE!

WE KNOW IT!

So What Happened?

Why Change?

Scaling WordPress is complicated

Our process was terrible

•Someone emails one of us a post

•We read it and send it back to them for revisions.

•They rewrite it and send us a new file... via email.

•Round and round we go.

•We email the finished article to our editor, Andrew.

•Andrew emails us a different copy with his edits.

•We copy/paste into WordPress and post.

OCTOPRESS

Rackspace Cloud Files is GLOBAL

Rackspace Cloud Files is CHEAP

http://github.com/rackerlabs/devsite

Our new process is awesome

•Someone forks our GitHub repo

•They write a post: rake new_post[‘Some post’]

•They submit a pull request to us.

•We revise it via a GitHub discussion

•We merge the commit.

•DEPLOY!

DEMO TIME

Conclusions...

OCTOPRESS

ENJOY YOURLUNCH!

everything as code

github discussion

current state

rake newpost

finished article

desired state

open source

industry standard

github repo

Technology

everything digital as a service (edaas)

“everything the teacher does as well as the manner in

if only everything in life was as reliabale as a volkswagen

everything you should know about qr code

code of conduct - bny mellon | consider everything

everything as a service - esell · everything as a service...

everything-as-code. polyglotte software-entwicklung in der...

everything as-code. polyglotte entwicklung in der praxis

anything as a service makes everything possible

keep everything freelancer and consultant at jtom.me … ·...

everything should be as simple as possible, but no simpler

1 core ingredients of computing a “universal” machine...

everything as code a journey into it …...case study: ci/cd...

everything as a service

everything as a code

recording everything: digital storage as an enabler...

everything-as-code. ein polyglottes abenteuer. #jax2017

pipeline as code for your infrastructure as code

infrastructure as code software defined everything for...

everything as a cookbook