dev ops in 2013

15
DevOps in 2013 We can do better. 6/7/22

Upload: jeff-schneider

Post on 15-Jan-2015

2.559 views

Category:

Technology


3 download

DESCRIPTION

The DevOps movement has made significant traction but many organizations still have immature processes and technologies. The presentation reviews the areas of concerns.

TRANSCRIPT

Page 1: Dev ops in 2013

April 10, 2023

DevOps in 2013We can do better.

Page 2: Dev ops in 2013

April 10, 2023

DevOps: We Can Do Better

Fixing yet another ‘organizational silo’ problem, this time between pre-production and go/post-production teams

Widely acknowledged as a process and ownership problem.

Integrate & QAAnalysis Design Release OperateConstruct Consume Evolve

Influence non-functional requirements

Influence architecture

Influence configuration

Continuous releases

Continuous testing

Continuous SLA Enforcement

Aligning Pre-Production and Go/Post Production Teams

Page 3: Dev ops in 2013

April 10, 2023

Next-Gen DevOps

1. Continuous Integration is the Starting Point2. Continuous Testing is a Must3. Continuous Delivery for the Right Reason

4. Integrate the DevOps Tool-Chain5. Architected for Operations 6. Instrumented for Operations

7. Open Source Dominates Tooling8. DevOps on Cloud

9. A Renewed Focus on Metrics, SLA’s and Incentives

Page 4: Dev ops in 2013

April 10, 2023

Continuous Integration is the Starting Point

Continuous integration is in poor shape at many organizations.

Common issues include: Splintered version control systems including old ones like PVCS, CVS, etc.;

failure to consolidate to newer choices: git, svn, etc.

Splintered build systems even on same platform (Ant, Maven, etc)

Running continuous build system – but allowing broken builds to exist

FIX CONTINUOUS INTEGRATION BEFORE MOVING ON

Page 5: Dev ops in 2013

April 10, 2023

Continuous Testing is a Must!

Continuous Testing is in AWFUL shape at most companies!

Create and run basic automated tests with builds: Unit tests (Junit, Nunit, etc.) Integration tests (SoapUI, etc.) Resilience tests (Chaos Monkey, etc.) Load / Performance tests Vulnerability tests UI tests (Selenium, etc.)

It’s a shame we call it “DevOps”, it should be “DevTestOps”!

Page 6: Dev ops in 2013

April 10, 2023

Continuous Delivery for the Right Reasons

Many are rushing to achieve continuous delivery but not for the right reasons.

98% automated deployment - - but can’t get the last bit. Frequent deployments but not infrequent customer releases. When deployments fail, still doing roll-back, not roll-forward. Achieved frequent releases but due to the number of failed

releases have reduced the % of availability.

Not looking at root causes of failures stagnates the automated delivery success rates.

Page 7: Dev ops in 2013

April 10, 2023

Integrate the DevOps Tool Chain

Dis-integrated tools in the delivery process reduce the ability to automate deployments (fast, cheap, accurate)

Integrate the DevOps tool chain: Start with continuous build (version control, build, continuous build, units) Quality tests show in dashboard and affect QA maintenance backlog Use proper repositories (Nexus, etc.), configuration management (Puppet,

Chef, etc.) Integrate with virtual & cloud environments where appropriate Use DevOps workflow automation (RunDeck) across the process

Keeping the tool chain integrated is as important as the first-time integration.

Page 8: Dev ops in 2013

April 10, 2023

Architected for Operations

Many applications aren’t architected to be easy to operate; this is a HUGE problem.

Architected for Operations attributes include: Ability to easily scale in or out without code changes (config/registry only) Ability to easily version or patch the system without taking it offline Ability to partially fail; e.g., keep taking inbound messages and queue them Ability to easily migrate the system (not hardcoded to infra layer)

Operability of a system must be a primary concern in the non-functional requirements

Page 9: Dev ops in 2013

April 10, 2023

Instrumented for Operations

Solution Architects incorrectly assume that operations will instrument their system once they ‘throw it over the wall’.

Instrumented for Operations activities include: System requirements mandate that warnings, errors, exceptions are logged

with unique identifiers; leverage unified logging where appropriate Complex multi-tiered, multi-component systems require additional visibility

of flow between systems (e.g., SQL calls, JSON messages, etc.) Clear direction given on infrastructure and application monitoring Instrumentation is used and tested in pre-production environments

Proper instrumentation is maintains developers, testers and operators sanity. It’s more than a nicety.

Page 10: Dev ops in 2013

April 10, 2023

Open Source Dominates the Tooling

Companies that are showing success in DevOps are utilizing significant amounts of open source tooling.

Less expensive, open source tooling is winning over commercial: Junit, Selenium, SoapUI, etc. are ubiquitous in .com and enterprise Ant, Maven, Jenkins, Nexus, etc are ubiquitous in .com and enterprise Puppet and Chef have moved beyond early adopters and are now being

used by the ‘early majority’.

Open source solutions are being updated at a more rapid rate than their commercial cousins. The wisdom of the crowds is driving innovation.

Page 11: Dev ops in 2013

April 10, 2023

DevOps on Cloud

Infrastructure as a Service is the preferred environment for many companies.

Users of IaaS almost ALWAYS embrace DevOps principles & technologies: AWS is promoting CloudFormation and OpsWorks Cloud solutions like ServiceMesh Agility offer DevOps accelerators Puppet & Chef have strong support for OpenStack, vCloud, etc.

The rapid provisioning of IaaS makes it a natural fit for deploying across dev, test, stage, prod and DR environments.

Page 12: Dev ops in 2013

April 10, 2023

Renewed Focus on Metrics, SLA’s and Incentives

MTTR, RTO and other operational metrics remain important but are not enough.

New Metrics and SLA’s include: Release rate, Quality of Release, Cost of Release System availability (as affected by patches, changes, etc.) Patch rate, In-Compliance % DR fire-drill success rate

Progressive organizations have monetary incentives aligned with metrics/SLA’s; plus or minus 15% of annual salary.

Page 13: Dev ops in 2013

April 10, 2023

MomentumSI on DevOps in 2013

MomentumSI provides consulting services to organizations that want world-class DevOps capabilities. Assessment of current state, workshops and roadmaps Culture transformation: rethinking processes, incentives and systems Upgrading capabilities in continuous builds, testing and deployment Establishing an Integrated DevOps tool chain Implementing continuous delivery scripts for your applications

For a briefing on our DevOps offerings, email: Jeff [email protected]

Page 14: Dev ops in 2013

April 10, 2023

Page 15: Dev ops in 2013