Slide 1

Slide 1 text

DevOps ?!@ what? HAZ! @utilities abionic@twitter abhishekkr@github

Slide 2

Slide 2 text

Found DevOps http://www.youtube.com/watch?v=EOveXZhJpr4

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

Not A Role

Slide 6

Slide 6 text

What Is DevOps? Solution to a Human Problem.

Slide 7

Slide 7 text

● From what I heard... around mid 2009, Patrick Debois started formulating the term DevOps. Main consideration being increased feedback loops between business, software delivery and operations. idea?

Slide 8

Slide 8 text

● From what I heard... around mid 2009, Patrick Debois started formulating the term DevOps. Main consideration being increased feedback loops between business, software delivery and operations. ● DevOps << Development IT Operations idea?

Slide 9

Slide 9 text

● From what I heard... around mid 2009, Patrick Debois started formulating the term DevOps. Main consideration being increased feedback loops between business, software delivery and operations. ● DevOps << Development IT Operations ● CAMS : Culture, Automation, Measurement, Sharing soon became, CALMS ~ Lean CAMS Now even Wikipedia has a decent description ( after loads of revision ) around the Idea. Go read. Form your own opinion. idea? John Willis said Jez Humble added

Slide 10

Slide 10 text

What Is DevOps? Id e a

Slide 11

Slide 11 text

culture? ● organization ○ ops perspective in inceptions, showcases and retro ○ one product one team ~ you build you run (amazon) ○ trust your people or stop being agile

Slide 12

Slide 12 text

culture? ● organization ○ ops perspective in inceptions, showcases and retro ○ one product one team ~ you build you run (amazon) ○ trust your people or stop being agile ● team ○ mixed stand-ups ○ devs rotation for tasks, collaborating all the time ○ devs and ops, both on release call and alert panel

Slide 13

Slide 13 text

culture? ● organization ○ ops perspective in inceptions, showcases and retro ○ one product one team ~ you build you run (amazon) ○ trust your people or stop being agile ● team ○ mixed stand-ups ○ devs rotation for tasks, collaborating all the time ○ devs and ops, both on release call and alert panel ● personal ○ broaden perspective beyond localhost ○ find a common ground between change and stability ○ automate and measure every aspect of ecosystem

Slide 14

Slide 14 text

What Is DevOps? Id e a C u ltu re

Slide 15

Slide 15 text

practice? ● inception ○ scrap out legacy ops, or fake-API-fy them ○ evaluate scalability over size, geo-location & time ○ analyze current practices and the shift required

Slide 16

Slide 16 text

practice? ● inception ○ scrap out legacy ops, or fake-API-fy them ○ evaluate scalability over size, geo-location & time ○ analyze current practices and the shift required ● development ○ repeatable and reliable ○ reviewable and rapid ○ resilient and robust

Slide 17

Slide 17 text

practice? ● inception ○ scrap out legacy ops, or fake-API-fy them ○ evaluate scalability over size, geo-location & time ○ analyze current practices and the shift required ● development ○ repeatable and reliable ○ reviewable and rapid ○ resilient and robust ● delivery ○ automate the automation ○ secure the security ○ pin the lynchpin, and get rolling

Slide 18

Slide 18 text

What Is DevOps? Id e a C u ltu re Practice Solution to a Human Problem in Industry. Being Agile.

Slide 19

Slide 19 text

Agile Manifesto ● Individuals and Interactions over Processes and Tools ● Working Software over Comprehensive Documentation ● Customer Collaboration over Contract Negotiation ● Responding to Change over Following a Plan

Slide 20

Slide 20 text

DevOps a Community http://www.youtube.com/watch?v=ucc-Q_F1Gvg Culture where idea of continuous delivery is practiced from infrastructure, data and configuration management to business.

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No matter how well we ideate, create, test, surround & provide the entire product. $#!t happens Need to 'Monitor' every important aspect of product and product ambience. Place 'Alert' on events, that you can wiki-fy on how to handle.

Slide 23

Slide 23 text

DevOps HAZ! Alerting

Slide 24

Slide 24 text

Softwares don't breath on Developer nodes. They are born there. Softwares live in varied environments like QA/Staging/Production. To understand how our product works, we need to notice its activities on environments. Log & Analyze

Slide 25

Slide 25 text

DevOps HAZ! Analyzing Alerting

Slide 26

Slide 26 text

either you will be using ● PaaS (no system level tasks) Platform ● IaaS (no physical maintenance) Infras. ● NaaS (seriously, you Dinosaurus) Null automate everything required for an auto- scaled environment on that NodeModel

Slide 27

Slide 27 text

DevOps HAZ! Infrastructure Analyzing Alerting

Slide 28

Slide 28 text

more complex application's architecture is; the more components to interact; hence more to scale, monitor, log and secure... Analyze and Update Component's Properties

Slide 29

Slide 29 text

DevOps HAZ! Application Infrastructure Analyzing Alerting

Slide 30

Slide 30 text

predictable, reliable; fast feedback, quickly respond to demand; fail fast, continuous improvement; delivery power in hands of business Continuous Integration Continuous Deployment Continuous Delivery

Slide 31

Slide 31 text

DevOps HAZ! Application Infrastructure Analyzing Alerting Continuous delivery

Slide 32

Slide 32 text

Lean ● Eliminate Waste like unnecessary code & functionality, unclear requirements, less testing, bureaucracy, slow communication ● Amplify Learning instead of adding to documentation or planning, try & learn ● Decide as late as possible until they can be made on facts not assumptions. Set-based development flow allows better solutions. ● Deliver as fast as possible, without speed decisions can't be delayed. ● Empower the team, find capable people and let them use their capability. Enable their access to customer. ● Build integrity in product quality, keep it flexible, maintainable, efficient & responsive. Solve requirements simultaneously as the information flows in both direction, not sequentially. ● See the whole... larger the system, the more organizations &/or teams involved, greater the importance of having well defined relationship. A part of strong team is much more beneficial than minimum interaction departments.

Slide 33

Slide 33 text

DevOps Required http://www.youtube.com/watch?v=jAQ7WZWr0mo

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

until now... DevOps https://www.youtube.com/watch?v=lLvfCTgRtmw https://www.youtube.com/watch?v=o7-IuYS0iSE