they’re shiny. they’re new. and they’re what devops...

Post on 01-Jun-2020

22 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

They’reshiny.They’renew.Andthey’rewhatDevOpsisallabout!ThecooltoolsetsthatenablesuchamazingITperformancecallouttous:“Downloadme!Installme!I’llmakeyourIT-lifegreat!”Butdon’tfallfortheirSirenSong!

1

WhileitistruethatDevOpsmaturityrequiresagoodtoolset,itisalsotruethatDevOpsismuch,muchmorethanjustimplemenLngtools.DevOpsisaboutpeople,anditisabouttheprocessesweuse.DevOpsoMenrequiresustorethinkthearchitectureofoursystemsandservices,evenhowourorganizaLonisstructured.AndDevOpswillinevitablyraiseculturalchallengesthatnotoolscanaddress.So,whilewe“automateeverythingwecan”,wemusttakecareabouthowalloftheseshinynewtoolswillworkwiththerealiLesofthepeople,processes,architectures,organizaLon,andcultureofourITshop.Let’stakealookatsomeexamples.

2

WhatcanbemoreobviousthanusingPuppetorCheftoautomateconfiguraLonofourservers?Butwhowillusethesetools,andwhatwilltheyusethemtoconfigure?Theserverteam?Thenetworkgroup?Back-endsupport?Desktopteam?HowaboutDatabaseAdministraLon?OrourApplicaLonteams?Maybealloftheabove?Ifso,who’sresponsibleforwhat?And(especiallywherethereareoverlaps–e.g.ourStorageAreaNetworkorapplicaLonservers)howwillalloftheseteamscooperateandcollaborate?HowwillthoseconfiguraLonsbedefinedandstandardized?Whoisallowedtodowhat,andwhen?OrganizaLonalsiloscomplicatethesesortsofimplementaLons,soifyourshopisorganizedthatway(andmostare),thenbeforeanytooldecisionsaremade,you’llneedtoreachacrosssiloboundaries,iniLatecollaboraLon,andworktogethertofigureouthowtogetstarted,andhowtoconLnuethatcollaboraLonoverthelonghaul.What?Youdon’tgetalongwithsomeofthosefolks?Thenthere’ssomeevenmoreorganizaLonalmendingthatyouneedtoaddressbeforeyoucangetstarted.

3

Jenkinsisoneofthecoolesttools!Andascreamin’fastdeploymentpipelineiswhatweallwant.Butwhodeploysstufftoday?Theanswerislikelytodependonwhatstuffyou’rethinkingof.(ApplicaLons?ServerconfiguraLons?OSPatches?Mobileapps?Firewallchanges?)Andregardlessofwhatyouwanttodeploy,“who”islikelytobeavarietyofpeoplefromdifferentspecialtygroups.Anddon’tforgettheChangeControlBoard(CCB)!NothinggoesoutwithouttheChangeManager’sOK.Yourcurrentdeploymentprocessprobablyinvolvesanalysis,approvals,signoffs,andthenacLvitybylotsofdifferentpeople.AnyautomaLonweputintoplacewillaffecteveryoneofthoseplayersandhowallofthosedifferentgroupsinteract.EverychangewemakewillrequirenegoLaLonsamongalloftheseplayerstoensurethatthealloftherisksaresufficientlyaddressedandtheflowthruthedeploymentprocessisindeedopLmized.Thiswillresultinsignificantchangestopeople’sacLviLesandresponsibiliLes.Thosewithmorepowerarelikelytoresistrelinquishingcontrol,andthosewithseriousconcernsarelikelytobequiteconservaLveinwhattheywillagreeto.

4

WhileautomatedtesLngtoolsarenotnew,theirusewillexpandasyouembraceDevOps.IndeedyourdeploymentpipelinecannotbeopLmizedwithoutsignificantautomatedtesLng.WhoisresponsiblefortestautomaLoninyourshoptoday?Thetestteam?Asub-groupofyourteatteam?Ormaybenoone,becausealltesLngismanual?IfyourshophasneverusedtestautomaLon,acompletechangeinthinkingmuststartatthetop.TheholdersofthepursestringsmustunderstandboththevalueandthenecessityofinvesLnginthetools(andthetrainingpeoplewillneedinordertousethem).TheymustalsoembracetheideathatbuildingsomethingisnotcompleteunLlwehavealsobuilttheautomatedteststhatareneededtoverifyit.Beyondthat,addingtestautomaLontothemixmeansaddingtoourtechnicalcontributors’responsibiliLes.ThisaffectstheirjobdescripLons(whichimpactontheperformanceappraisalprocess),aswellastheirself-percepLon,andquiteessenLally,meanstheymustaltertheirworkhabits.IfyoualreadyhavetestautomaLonprofessionals,youwillfindthattheywillneedtoshareresponsibilityforwriLngautomatedtestswithothers.ThiswillmeansignificantchangestotheirjobresponsibiliLes,expectaLons,andworkpaeernsas

5

SecuritymustbeaprimeconsideraLonineverythingweimplement.Ontheonehand,automaLngourdeploymentpipelinewillyieldlielevalueifwehavetostopattheSecurityGateattheendoftheprocess,whereourworkisrouLnelykickedbackforrework.Sowewillneedtocollaboratewithoursecurityteamtoweavesecuritychecksinthroughoutthedeploymentpipeline.WiththelimitednumberofsecurityprofessionalsmostITshopshave,findingtheLmeforthiscollaboraLoncanbeachallenge.Butthebiggerimpactis(likesomeoftheitemsdiscussedabove)thewayitwillchangepeople’sjobs(makingsecuritypartofeveryone’sjob)andthewaysinwhichthesecurityteaminteractswitheveryoneelse.TheotherbigimpactissecuringalloftheautomaLonweputintoplace.Whenspecialistsdidthingsbyhand,securitywasn’tabigissue(aslongaswetrustedthosespecialists).ButwhenanyonecanpushabueonorcheckinaconfiguraLonfile,andwhenallofoursystemcredenLalshavetobemadeavailabletoourtools,securingthesethingsbecomescrucial.ConsidertheexposureifahackerbrokeintoouroperaLonandgainedcontroloverourdeploymentpipeline,orchangedtheconfiguraLonofourfirewallorserverstoopendoors,orharvestedrootpasswordsfromourrepository.YIKES!Thisisanother

6

SmallbatchsizebecomesafocuswhenyouareimplemenLnganyofthesetools.DoingworkinlargebatchestaxestheautomaLonmakingismuchlessefficient,andimpedingtheflowofourwork.TheAgilemethodshavealreadytaughtusaboutthis.Webreakprojectrequirementsdownintoalargenumberofverysmalldeliverables(Stories),andthenbuildtheminsmallbatches(afewStoriesineachshortSprint).ThemostefficientandeffecLvewaytouseanyofourDevOpstoolsandpracLcesistoapplythisconceptnotjusttodevelopingsoMware,buttoeverythingwedo.•  ApplicaLonArchitecture:MovingfromlargemonolithicapplicaLonstoServiceOriented

Architecture(SOA)orMicroservicesmeansthatweareworkingwithmanysmallparts,whichmakesourdeploymentpipelinemoreefficientandsimplifiesautomatedtesLng.

•  Projects:ShiMingfromlargeprojectstoaseriesofsmallerupdatessimplifiestheflowandthetesLngevenmore.SomeITshopsaremovingawayfromaprojectorientaLonaltogether,focusinginsteadonmakingincrementalchangestoservicesorapplicaLons(aproductorientaLon).Eitherway,thatisacompletereformoftheorganizaLon’sapproachtochangethatreachesallthewayuptoseniormanagementwhereprojectsareapprovedandfundingisallocated.

•  OrganizaLonstructure:MostDevOpsorganizaLonsmovetoacross-funcLonalteamstructure(usingAgileself-organizaLonteamprinciples)whichmeansthatspecialistsarenolongersegregatedalongspecialtylines,butareinsteadworkingshoulder-to-shoulderwithothersofdifferentspecialLes.AndsomeareabandoningfuncLonalteamsaltogether

7

Yes,DevOpsisaboutthetools,butitisaboutmuchmorethanjustthetools.TherearemanyotherthingswehavetopayaeenLontoaswechooseourtoolsandfigureouthowtousethem.ThereisnosubsLtuteforgejngstarted…withsomegoodguidance.AgoodstarLngpointforlearningisASPE’sDevOpsImplementa7onBootCamp,orourIntroduc7ontoDevOpsCourse,orforseniormanagersourDevOpsExecu7veWorkshop.hep://aspetraining.com/subjects/devops-training-coursesAMeryou’vewrappedyoumindaroundthebigpictureandhaveaplanformovingforwardwiththetoolsandtheotherelements,thenyouwillwanttocomebackforourtooltraining(e.g.Puppet,Chef,Jenkins,Docker,Git),andourtechnicalpracLcestraining(e.g.CI/CDWorkshop,TestAutomaLon,Test-DrivenDevelopment).ThatwillgiveyouagoodstartonyourDevOpsJourney.

8

top related