DevOps Automation On

DevOps Automation On

The Story So Far

My introduction to Unix.

The Story So Far

"No problem should ever have to be solved twice." Eric S. Raymond

The Story So Far

Yesterday: Server Management was Unwieldy.

The Story So Far

New Tools Emerged.

The Story So Far

Today: 100% Automated response.

DevOps Automation Service

Engineering around the clock.

DevOps Automation Service

Everything is shared.

DevOps Automation Service

Collaboration in chat.

Table of Contents

App Deployment Patterns

App Deployment Patterns

Pre-Baked

App Deployment Patterns

In Place With Artifact Server

App Deployment Patterns

Chef With Docker

App Deployment Patterns

In Place App Deployments.

Design Decisions

Chef Code is Real Code

Design Decisions

Chef is not opinionated.

Design Decisions

The resource collection.

Design Decisions

Dynamic configuration.

Community Cookbooks

The Supermarket.

Wrapper Cookbooks

Grouping common functions.

Stacks

Best of community and integrations.

Git Workflow

Production and staging.

Git Workflow

Feature branches.

Git Workflow

Rolling back (or forward).

Test Kitchen

Infrastructure + app should be well tested and fast.

Test Kitchen

Chef workflow.

Test Kitchen

Kitchen workflow.

Serverspec

Kitchen test

Serverspec

Example spec

Monitoring and Auth Strategies

By Matt Thode

Rackspace Cloud Monitoring

• Explanation
  • alerting and ticket creation for services deployed
• Usage
  • server side config via autogenerated yml files
• What it gives
  • same monitoring on both private and public cloud
  • all alerts go to one account (cloud)

New Relic Monitoring

• Explanation
  • Performance metrics and application monitoring
• Usage
  • system agent auto-deploys
  • application agent can be enabled as needed
• What it gives
  • Able to generate tickets from application / performance metrics

Dedicated Service Net

• Explanation
  • Private cloud access to service net and to public cloud instances (and visa versa)
• Usage
  • controled via neutron
  • access control via security groups
• What it gives
  • common network backend between both public private providers
  • centralized firewall

Bastion Usage

• Explanation
  • a single node from which you access the rest of your infrastructure.
    • can be limited to be one per environment
• Usage
  • able to be in between for both private and public cloud
• What it gives
  • centralized access control for developers and sysadmins

Use Case

• Burst in public cloud
• more controled infrastructure vs less controled infrastructure

Automating Applications with Heat

By Walter Bentley