Transcription
17310: DevOps on the Mainframe:Managing the Cultural DivideSal Del ConteDirector Implementation and SupportSoftware Engineering of America (SEA)Jim MorganDirector Major Accounts, SEAInsertCustomSessionQR ifDesired
AgendaI.Introductionsa) Key terminologyb) Why is the DevOps conversation important?I.HurdlesII.Agreement on common goalsIII. DevOps in the SDLC? What might I observe?IV. Lets come out of the cloud!a) A discussion around your SCM and JCLb) How might I start?c) Practical examplesV.Recap8/5/20153
Definitions DevOps Agile CI ITIL
Why is this conversation necessary? Your peers and your managers are talking about it! Systems of Record and Systems of Engagement Information is Power. Remember DevOps by definition iscollaborative.
Hurdles to DevOps on the Mainframe
Hurdles to DevOps on the Mainframe Very mature environment (decades?) Belief that limiting change minimizes risk Belief that ‘Agile’ approach applies more to Dev andSystems of Engagement and wouldn’t apply for the‘well managed’ Systems of Record
Hurdles to DevOps on the Mainframe Existing processes for mainframe systems-of-record arewell-entrenched over many years. Adapting these to a CIapproach can be viewed as overly time-consuming andcostly Collaboration is often hindered by current Test / Deployprocesses for the mainframe which can be very silo’edand inconsistent among Dev teams Financial justification can be challenging
Hurdles to DevOps on the Mainframe DEV team often lacking tools to find/fix defects early in theSDLC DevOps teams use different tools / inconsistent approachesfor Test / Release / Deploy CMDB of APP components is unavailable / inaccurate SDLC lacks automation at key release / deployment points SDLC and/or DEV tools lack metrics and reporting forgovernance and continuous improvement DEV teams lack knowledge of overall batch flows and/orability to model changes
Common ObjectivesCost ofDefectsDEVQAPROD
Common ObjectivesDefectsAvoidedDEVQAPROD
DevOps in the SDLC? What might one observe?Enabling TechnologyCompressing TimeBetween ReleasesConfidence in TestingAccuracyReliance on metricsAutomated Maintenance ofdocumentation CIsContinuous Process ImprovementDEVQAPROD
Lets come out of the .Your JCL and SCM Process The best place to start is the source and scripting code managementprocess and toolset (SCM) The change management process is a good starting point, as it providesthe Organization’s promotion and deployment map. Scripting (JCL) is as important as application code Fundamentally, look for all opportunities in the SDLC to increase thespeed for Test / Release / Deploy within the systems-of-record whileadhering to quality guidelinesTESTAuditAddQADEVPromotePRODCheckout14
So How Do We Get There? Empower developers with the right toolsto enable frequent iterations of highreliability testing early (and throughout)the SDLC Provide reliable documentation for modeling and maintenance(especially for legacy systems)Provide a consistently accurate CMDB to ensure high confidencein application component dependencies
So How Do We Get There? Instill high confidence in the Build/Test/Deployprocess. When looking at it one should observe: Limited varianceo (e.g. Why do we need different build/testprocesses for each application group?)o Can we use middleware to connect systems and reduce thenumber of unneeded instances (risk of variance)? As much well designed automation as possible Shared metrics and reporting for governance and continuousimprovement A high level of confidence that processes are not bypassedwithout well-defined and accepted exception approval procedures
Technology and Automation ToolsContinuousDelivery Middleware Centric Simulation Environment andDeployment Tools17
Middleware Centric and Simulation Automation Tools DEVEclipse IDE and othersSimulation and run-time validationAutomate environments provisioningReduce Mean-Time-To-Repair
JCL Testing and Documentation Tools JOBPGMDB2VTOCCCDEV Complete System Level DocumentationCleanup obsolete and decommissionedcomponentsTestingModeling (Reuse)Application Rebuild
Measured Process Automation “ The Handoff” QAAutomate TestingCheck DependenciesExecution forecast and simulation
Real-time Predictive Analysis PROD
Measuring process adoption DEVQAPRODIdentify right group of quality andrelevant metrics to the businessEstablish a baseline and continuousmonitoring and feedback
Measuring process adoptionIndex and Correlation Engines
Other ConsiderationsContinuous Process Improvement
Continuous Process ImprovementRefactoring using Naming Conventions TESTSTDsPRODSTDsDEVQAPROD
Summary!These are not new conceptsWe all want better quality soonerIt’s not about
SDLC DevOps teams use different tools / inconsistent approaches for Test / Release / Deploy CMDB of APP components is unavailable / inaccurate SDLC lacks automation at key release / deployment points SDLC and/or DEV tools lack metrics and reporting for governance and continuous improvement
