Everything as Code

everything
as code
hart hoover
cloud evangelist
Wednesday, August 21, 13

WHAT IS devops?
2

3
Culture & Work Methodology

4
What Does DevOps Enable?

8
Tooling

11
Gerrit

13
Deployment Strategies

17
Cookbooks
Nodes
(chef-client)
Chef
Server HTTPS
Workstation
knife

•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
18

CHEF TOOLS
19
Test Kitchen
berkshelf
foodcritic
Vagrant

21
Manifests
Agents
Puppet
Master HTTPS
Puppet
CA

•Nodes: Servers
•Environments: Groups of
nodes (Dev/QA/Prod)
•Manifests: Describes the
desired state of a node
•Catalog: Group of Manifests
•Facts: information about the
current state of a node
22

PUPPET TOOLS
23
Test Kitchen - soon
librarian-puppet
puppet-lint
Vagrant

PUPPET vs. CHEF
24

26
States
Minions
Master

•Nodes: Minions
•Environments: Groups of nodes (Dev/QA/Prod)
•States: Describes the desired state of a node
•Grains: information about the current state of a node
27

29
SSH
Playbooks
Hosts

•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.
30

ANSIBLE vs. SALTSTACK
31

32
Measure All the Things

CollectD + GRAPHITE
33

CollectD + GRAPHITE
34

CollectD + GRAPHITE
35

NAGIOS
36
NAGIOS
Linux
Windows
Networking
NSClient++
NRPE
SNMP

NAGIOS PluGINS
37

38
• Application Monitoring Service
• Agent-based
• Plugins

39
Automate All the Things

42
SOME OF THESE != SUCCESS

43
NO CULTURE BUY-IN = NO DEVOPS

44
SOFTWARE DEVELOPMENT LIFECYCLE

45
DEV OPS+

45
DEV OPS+ QA+

45
DEV OPS+ QA+
=
DEVOPS

How to Embrace
DevOps
46
SCRUM KANBAN AGILE

SCRUM
47
Scrum Master
Product Owner Developers

Product
Backlog
Sprint
Backlog
Sprint
Working increment
of the software
48
1. Design
5. QA 2. Build
4. Release 3. Configure

49
1. Design
5. QA 2. Build
4. Release 3. Configure

SCRUM: KEY MEETINGS
50
Backlog Grooming
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective

Features In Progress Blocked Tabled Testing Complete
Feature A
Feature B
Feature C
51
KANBAN

Feature A
Feature B
Feature C
52
KANBAN

Feature A
Feature B
Feature C
Feature E
Feature D
52
KANBAN

Feature AFeature BFeature C
Feature E
Feature G
53
KANBAN

Feature AFeature BFeature C
Feature E
Feature D
Feature F
Feature G
53
KANBAN

Feature A
Feature B
Feature C
Feature E
Feature D
Feature F
Feature G
54
KANBAN

Feature A
Feature B
Feature C
Feature E
Feature D
Feature F
Feature G
Feature H
Feature I
54
KANBAN

Feature A
Feature B
Feature C
Feature EFeature D
Feature F
Feature G
Feature H
Feature I
55
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
56

AGILE TEAMS
57
Traditional Teams AGILE Teams
Project Manager /
Team Lead
Servant Leader /
Facilitator
Self-Organized

CONTINUOUS DELIVERY
58

59
Same Problems

60
What Version is in Production?

61
Issues are Found, Fixed & Redeployed Quickly

62
Test as You Develop

63
Same Best Practices

64
Tag, Branch & Release Code that Defines Infra

65
Coverage Lifecycle Over Various Stages

66
Continuously Test

70
INDUSTRY STANDARD!

70
INDUSTRY STANDARD!
OPEN SOURCE!

70
THEMES!
INDUSTRY STANDARD!
OPEN SOURCE!

70
THEMES!
PLUGINS!
INDUSTRY STANDARD!
OPEN SOURCE!

70
THEMES!
PLUGINS!
INDUSTRY STANDARD!
OPEN SOURCE!
WE KNOW IT!

So What
Happened?
Why
Change?

74
Scaling WordPress is
complicated

75
Our process was terrible

75
•Someone emails one of us a post

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

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

75
•Round and round we go.

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

75
•Andrew emails us a different copy with his edits.

75
•Andrew emails us a different copy with his edits.
•We copy/paste into WordPress and post.

77
OCTOPRESS

78
OCTOPRESS
+

79
Rackspace Cloud Files
is GLOBAL

80
Rackspace Cloud Files
is CHEAP

82
http://github.com/rackerlabs/devsite

83
Our new process is
awesome

83
•Someone forks our GitHub repo
Our new process is
awesome

83
•They write a post: rake new_post[‘Some post’]
Our new process is
awesome

83
•They submit a pull request to us.
Our new process is
awesome

83
•We revise it via a GitHub discussion
Our new process is
awesome

83
•We merge the commit.
Our new process is
awesome

83
•We merge the commit.
•DEPLOY!
Our new process is
awesome

86
DEMO TIME

86
DEMO TIME
MAYBE
?

Conclusions...

92
OCTOPRESS
+

ENJOY YOUR
LUNCH!

Everything as Code

More Related Content

Viewers also liked

Similar to Everything as Code

More from Wayne Walls

Recently uploaded

Everything as Code