devops from control to enablement

30
DevOps: Transform the Culture from Control to Enablement Nathan Aker Informa(on Systems Manager @ Symphony Talent

Upload: joanna-cheshire

Post on 13-Jan-2017

88 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: DevOps from Control to Enablement

DevOps:TransformtheCulturefromControltoEnablementNathanAkerInforma(on Systems Manager @ Symphony Talent

Page 2: DevOps from Control to Enablement

2

Percep(on Problem

Credit:[email protected]

Page 3: DevOps from Control to Enablement

3

•  Sales•  Innova:on•  MarketShareIncrease•  Differen:a:on•  CustomerSa:sfac:on/Reten:on•  Expansion•  BrandBuilding•  Profitability

Business Goals

Growth

Page 4: DevOps from Control to Enablement

4

•  Availability•  Security•  Stability•  Performance•  Efficiency•  RepeatableProcesses•  Metrics

IT Goals

Control

Page 5: DevOps from Control to Enablement

5

•  Development–Op:mizethefunc:onalityoftheservice•  Opera:ons–Op:mizetheefficiencyandstabilityoftheservice•  QA–Op:mizethequalityoftheservice•  Security–Op:mizetheconfiden:ality,integrity,andavailability

IT Func(onal Org Separa(ons

Page 6: DevOps from Control to Enablement

6

Strengths:-  Closesttobusinessneeds-  Delivernewcapabili:es-  Protectuserexperience-  Experiencedautomators

Weaknesses:-  Losefocusonscalability,stability,andsupportabilityat:mes

-  Typicallyunderpressuretodeliverquickly

-  Securitynotalwaystopofmind-  Notalwaysexperiencedop:mizers

Tradi(onal Development Group

Development

Page 7: DevOps from Control to Enablement

7

Strengths:-  Experiencedop:mizers-  Costconscience-  Focusonstabilityandavailability-  Tendtoconsidercross-func:onalimpacts-  Experienceddataandperformanceanalysts

-  Championdocumenta:on

Weaknesses:-  Typicallymanualprocessintensive-  Underpressuretominimizechange-  Catchinguponautoma:on-  OXenviewedasabo.lenecktoagility

Tradi(onal Opera(ons Group

Opera:ons

Page 8: DevOps from Control to Enablement

8

Strengths:-  Focusonquality(obviously)-  Experiencedincrea:ngtestcases-  Considerallusers/personas-  Collaboratorsbynecessity

Weaknesses:-  OXenrequireheavyguidancefromdevelopmentteam

-  OXenheavilyfunc:onalfocused(attheexpenseofload,performance,andsecuritytes:ng)

-  Usuallythemosttosufferina:melinecrunch

Tradi(onal QA Group

QualityAssurance

Page 9: DevOps from Control to Enablement

9

Strengths:-  Experiencediniden:fyingunintendedinterfaces,ports,orexecu:onmechanisms

-  Keenunderstandingofnetworkroutes&communica:onchannels

-  Uptospeedoncommona.ackvectors-  Strongskillsincomplianceandstandardiza:on-  Greatunderstandingofriskanalysis

Weaknesses:-  OXenstronglynetworkfocused-  Frequentlymoresecre:ve-  Tendencytosay“No”insteadof“Let’sfindasolu:on”

Tradi(onal Security Group

Security

Page 10: DevOps from Control to Enablement

10

DevOpsseekstoremovethesilosbychangingtheculturefromamyopicfunc:onalperspec:vetoamoreinclusivecollabora:vemindset.

Enter DevOps

Development Opera:ons

QualityAssurance Security

DevOps(DevSecOps)

Page 11: DevOps from Control to Enablement

11

•  Isitanorganiza:onal/teamre-alignment?•  Isitcloudinfrastructureautoma:on?•  Isitconfigura:onmanagement?•  IsitCICD/deploymentautoma:on?•  Isittes:ngautoma:on?•  Isitsecurityautoma:on?

What is DevOps?

Page 12: DevOps from Control to Enablement

12

•  DevOpsisamindset–builtonthefollowingfounda:ons:•  FocusonBusinessEnablement•  Collabora:on•  Automa:on•  Scalability•  Quality•  Velocity&Agility•  Con:nuousFeedback&Improvement

•  KeyObjec:ve•  Reliablyreduce:mefromIdeatoValueRealiza:on(withoutimpac:ngquality,performance,availability,security,orscalability)

DevOps is a Mindset

Page 13: DevOps from Control to Enablement

13

1.  AutomatealltheThings

2.  IntegratetheTeams

3.  ReduceTimetoValue

DevOps is a Mindset

Page 14: DevOps from Control to Enablement

14

•  Mindset/CultureChange

•  OrgChanges

•  SkillsetChanges

•  FocusonDecreasingTimetoValue

What does DevOps Involve?

People Process Technology

•  Dev/Ops/QA/SECProcessChanges

•  Automa:onofProcess(requiresunderstanding/documenta:on)

•  AccountabilityChanges

•  New/UpdatedRoles

•  Configura:onManagement

•  Con:nuousDelivery

•  Automa:onU:li:es/Scrip:ng

•  AutomatedTes:ng

•  SecurityAutoma:on

Page 15: DevOps from Control to Enablement

15

•  InfrastructureCreaCon•  Automa:callycreateinfrastructurecomponentsandserverinstances.

•  ConfiguraConManagement•  Configureserverinstancestohardened/definedspecswithnecessarycomponentsinstalled.

•  ConCnuousIntegraCon/ConCnuousDelivery•  Automatethedeliveryofapplica:onreleasesfromDevtoProduc:on.

•  SourceControl•  CentralizedcodemanagementforAppsandInfrastructure.

•  ContainerizaCon•  Hostapplica:ons/componentswithinlogicalcontainerswithinavirtual/physicalhost

•  TesCngAutomaCon•  Automatefunc:onal,integra:on,regression,andsecuritytes:ng

DevOps Technology Areas

Page 16: DevOps from Control to Enablement

16

Infrastructure Delivery - Old Way

Page 17: DevOps from Control to Enablement

17

Infrastructure Delivery - DevOps

Page 18: DevOps from Control to Enablement

18

Code Deployment - Old Way

Page 19: DevOps from Control to Enablement

19

Code Deployment - DevOps

Page 20: DevOps from Control to Enablement

20

DevOps Mindset Impacts all IT

•  Development•  Gainastakeinwhatittakestorunandsupporttheapplica:onatscale.•  Embedsecurity/QAtes:ngintotheSDLC.•  AssistsOps,QA,andSecuritywithautoma:onoftheirprocesses.•  Begintobuildperformanceandstabilitymetricsintodeliverypipeline.•  Youbuildit–yousupportitmentality(sharedaccountability).

•  Opera:ons•  Begintoautomaterepeatableandstandardizedprocesses.•  Starttomanageinfrastructureascode.•  Becomeinvolvedinapplica:onqualityprocess.•  Be.eringrainsecurityhardeningintoinfrastructure.•  Gainunderstandingofwhatcode/applica:onisdoingontheirboxes.

Page 21: DevOps from Control to Enablement

21

DevOps Mindset Impacts all IT

•  QA•  Automatetes:ngsoitcanbeperformedatscale.•  Collaboratewithdevelopmentgrouponbusinesscontextandneeds.•  Includesecuritychecksintotes:ngloops.•  Begintobecomescalable.

•  Security•  Ensureimmediatecompliancebycollabora:ngoninfrastructureautoma:onandCICD.•  Reduceorganiza:onalriskbyintegra:ngintotheSDLC.•  Shareexperienceandknowledgeofcommona.ackvectorswithDev&Ops.•  Increaseconfidencethattheenvironmentis“known”.•  Becomeenablersinsteadofblockers.

Page 22: DevOps from Control to Enablement

22

Phoenix Project

NovelbyGeneKim,GeorgeSpafford,andKevinBehr

AnalogyofITbeinglikeafactoryproducConfloor:•  ProcessFlow•  Inputs/Outputs•  WaitTimes•  Bo.leNecks•  Con:nualImprovement/Automa:on

Page 23: DevOps from Control to Enablement

23

1.  Culture–AboveallDevOpsisaMindset.•  Educa:on•  OrgChanges•  Champions•  SkillAddi:ons•  Consul:ng

2.  ProcessChanges–StartSmall•  Iden:fyakeyservicewiththehighestvalueproposi:onandlimitedrisk•  Rememberthemanufacturingfactoryanalogy.Iden:fyabo.leneckorpain

point.•  Leanmindsetwithrealis:cgoalsandcon:nuousimprovementloops.

I’m Ready for DevOps – Where to Start?

Page 24: DevOps from Control to Enablement

24

•  Tools–Cultureandprocesschangeswillleadyoutotools.•  InfrastructureCreaCon

•  Terramark,AWSCloudForma:on,CloudServiceBroker,VMWare

•  ConfiguraConManagement•  Chef,Puppet,Ansible,Salt

•  ConCnuousIntegraCon/ConCnuousDelivery•  Jenkins,TeamCity,Bamboo,Maven

•  SourceControl•  Git,GitHub,BitBucket

•  ContainerizaCon•  Docker

•  TesCngAutomaCon•  Selenium,Appium,QMetry

I’m Ready for DevOps – Tools

Page 25: DevOps from Control to Enablement

25

•  StrongOS,Scrip:ng,andInfrastructureSkillswithDevelopmentCompetence•  Strongdesiretoautomate(obviously)•  Tinkerer•  Con:nuallyseekingtounderstandthe"Why"behindthe"What”•  IntrinsicallyMo:vated–Wanttobuildgreatthings•  Typicallyoutinfrontoftheirorganiza:on

(Hint:pickupgreattalentfrustratedwithslowculturalmovementofcurrentemployer)

•  Con:nuallytryingtoautomatethemselvesoutoftheprocess.•  HATESrepe::vetasks(Healthyleveloflaziness)•  Enjoyschangeandnewtools

Prac(cal – Traits of a Great DevOps Engineer

Page 26: DevOps from Control to Enablement

26

•  ReduceTimetoValue•  TurnITfromacontrollingbo.lenecktoabusinessenabler•  Buildresiliency&scalabilityintoyourinfrastructure•  Enablenewcapabili:es•  Leveragethingslikeon-demandandserver-lesscompu:ngtosaveinfrastructurecosts

•  EmbedsecurityandQAtes:ngintothedeliverylifecycle.•  IncreasedQuality•  ReducedRisk

•  Helpdrivemeaningfulbusinessgrowth

Recap – Why DevOps?

Page 27: DevOps from Control to Enablement

27

• Itwillputmeoutofajob• Myappisuniqueandcannotbeautomated• Idon'thave:me• Wedon'thavetheskillset• Mysecurityteamwillnotallowit• WejustmadeaheavyinvestmentinHardwareassets

Misnomers of DevOps

Page 28: DevOps from Control to Enablement

28

MonthlymeetupgroupfocusingoncloudinfrastructureinAWSwithregulardiscussionsonDevOps,CICD,andAutoma:ontopics.www.meetup.com/Oklahoma-City-AWS-User-Group/

Connect & Learn

Page 29: DevOps from Control to Enablement

29

We’realwayslookingfortalentedDevOpsprofessionals

[email protected]

Shameless Plug

Page 30: DevOps from Control to Enablement

30

Email:

[email protected]:

h.ps://www.linkedin.com/in/nathanaker

Ques(ons?