2015 devops breakfast introduction

9
AGENDA What is DevOps? Getting the right team together Key Benefits Cool things that DevOps enables Key Challenges DEVOPS EXECUTIVE BREAKFAST

Upload: nvisia

Post on 12-Apr-2017

227 views

Category:

Software


0 download

TRANSCRIPT

Page 1: 2015 DevOps Breakfast Introduction

AGENDA• What is DevOps?• Getting the right team together• Key Benefits• Cool things that DevOps enables• Key Challenges

DEVOPSEXECUTIVE BREAKFAST

Page 2: 2015 DevOps Breakfast Introduction

DEVOPS BREAKFAST WHAT IS DEVOPS?

Two foundational principles:

• Get the right people together on the team

• Automate as much as possible in the build, test, deploy cycle

Page 3: 2015 DevOps Breakfast Introduction

“Back in the Day”

Product Vision / “The Business”

Development Team

QA

Operations

DEVOPS BREAKFAST GETTING THE RIGHT TEAM TOGETHER

Specify features, throw it over the wall to Dev and pray that nothing goes wrong

Hope that we understand the requirements, hope that the business shares our appreciation of elegant architecture, etc.

Hope that the specs capture the requirements, above all, don’t let bugs get into production, even if it delays important

features

Reliability and stability trump. Lots of manual processes, so we can only release once a quarter. Annual freezes. Don’t trust

those dev guys, they’re up to something

Page 4: 2015 DevOps Breakfast Introduction

“Back in the Day” Agile 1.0

Agile Team

Product Vision / “The Business”

Development Team

QAQA

OperationsOperations

Product Owners and Developers now collaborating, release-ready features emerging on frequent basis

Wow, these user stories don’t have the level of detail that we’re used to. Above all, don’t let bugs get into production,

even if it delays important features

Reliability and stability trump. Lots of manual processes, so we can only release once a quarter. Annual freezes. Don’t trust

those dev guys, they’re up to something

DEVOPS BREAKFAST GETTING THE RIGHT TEAM TOGETHER

Page 5: 2015 DevOps Breakfast Introduction

“Back in the Day” Agile 1.0 Agile +

DevOps

DevOps Enabled Agile Team

Agile Team

Product Vision / “The Business”

Development Team

QAQA

OperationsOperations

DEVOPS BREAKFAST GETTING THE RIGHT TEAM TOGETHER

Full team now invested in the success of the product,

release-ready features emerging on frequent

basis, getting tested for quality, and continuously delivered into production

Page 6: 2015 DevOps Breakfast Introduction

DEVOPS BREAKFAST KEY BENEFITS

Break down the barriers between Product, Development, QA, Operations• Deeper involvement between the factions fosters empathy for the goals of all parties

Better knowledge sharing across the technical specialties• Developers learn about the realities of operations• Development and QA have opportunities to collaborate on automated tests

More efficient use of headcount• Highly automated deployments act as a force multiplier

Page 7: 2015 DevOps Breakfast Introduction

DEVOPS BREAKFAST SOME COOL THINGS THAT DEVOPS ENABLES

The end of patching servers• Easy to promote “fresh” servers to production and crush the out-of-date servers• Servers are cattle, not pets (Gavin McCance)

Test & QA environments that look like production environments• Depending on your cloud infrastructure, it may be practical to have the same server topology

in test as you will have in prod

DevOps is a key enabler of zero-downtime deployments and Continuous Delivery

• Zero-downtime deployment would be too risky without the reliability of a scripted deployment

Blue-Green Deployments• Essentially deploy two versions of the software in parallel• Route users to the new instance• Easy to fall back in case of error

Page 8: 2015 DevOps Breakfast Introduction

DEVOPS BREAKFAST KEY CHALLENGES

Current Culture• DevOps is a culture shift• Some Ops resources may see it as a threat

Challenging to acquire the right resources• The ideal DevOps resource blends skills from both software development and operations

Rapidly maturing technologies• New frameworks and tools are being released on a frequent basis• Not all will survive

Legacy applications may need significant rework to realize the full benefits• May need to re-architect for Microservices

Breaking down separation between teams may raise concerns around security, ITIL, etc.• Current processes may not solve this completely• Trade-off: quality may rise while potentially increasing security risk

Page 9: 2015 DevOps Breakfast Introduction

QUESTIONS?