Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Dev ops for mainframe innovate session 2402

1.283 visualizaciones

Publicado el

Publicado en: Tecnología
  • Sé el primero en comentar

Dev ops for mainframe innovate session 2402

  1. 1. DevOps for the MainframeLeveraging Continuous Integration, the cloud, and beyond todeliver z/OS applicationsSession SC-2402David Myers, Product Manager, Cross-Brand DevOpsmyersda@us.ibm.com@Dave_DoesRosalind Radcliffe, Distinguished Engineer, EnterpriseModernization Solution Architectrradclif@us.ibm.com
  2. 2. Please noteIBM’s statements regarding its plans, directions, and intent are subject to change orwithdrawal without notice at IBM’s sole discretion.Information regarding potential future products is intended to outline our general productdirection and it should not be relied on in making a purchasing decision.The information mentioned regarding potential future products is not a commitment, promise,or legal obligation to deliver any material, code or functionality. Information about potentialfuture products may not be incorporated into any contract. The development, release, andtiming of any future features or functionality described for our products remains at our solediscretion.Performance is based on measurements and projections using standard IBM benchmarks ina controlled environment. The actual throughput or performance that any user will experiencewill vary depending upon many factors, including considerations such as the amount ofmultiprogramming in the user’s job stream, the I/O configuration, the storage configuration,and the workload processed. Therefore, no assurance can be given that an individual userwill achieve results similar to those stated here.
  3. 3. 3Social, Local, MobileSmart Infrastructure AnalyticsERP  Legacy  DB  CRM   HR  Manage workloadsand maintain securityRapid innovationin the cloudUser experience andmobile managementNew era systems integrate existing operationalsystems with rapid delivery of new client-facing apps
  4. 4. Evolving customer and market expectationsCapabilities and User Experience Today EmergingPrimary Workload TypesSystems of RecordTransactionalSystems of Engagement (+ Record)Big Data, Analytics, Mobile/Social ChannelsTime to Value Planned OpportunisticDelivery Model Planned Incremental (DevOps)Development and Operations Team Sizes 100s and Costly 10s with built-in DevOps automationRelease Frequency Months to Years Hours to Days, based on business opportunityIntegration Frequency Weeks ContinuousService Sourcing Develop Consume and Assemble (Public and Private)Operational Model Systems ManagementBuilt in to application, Recovery Oriented Computing, ContinuousAvailabilityInfrastructure Deployment Days MinutesRisk Profile Big-Bang (High Risk) Incremental
  5. 5. DevOps is…A set of principles and values that facilitate collaborationacross disciplines to…1. Enable rapid evolution of deployed business services2. Reduce risk, decrease cost, and improve quality across theportfolioDevOps Principles§  Collaborate across disciplines§  Develop and test against a production-like system§  Deploy frequently using repeatable and reliable processes§  Continuously monitor and validate operational qualitycharacteristics§  Amplify feedback loopsPeopleProcessTools
  6. 6. Solution: A Continuous Delivery PipelineDevelopment Testing Staging ProductionBusinessOwners Customers•  Validate on more production-likeconditions earlier•  Automate hand-offs/promotions toincrease velocity through thedifferent stages•  Standardization on processes andassets between Dev and Ops•  Automated monitoring anddashboarding of quality andperformance against service levelagreements at multiple stagesEnsure applications are production-ready throughout the lifecycleand can be released at any time while minimizing rollback due to quality issues
  7. 7. Mainframe Delivery Pains…§ Multiple teams working acrossrestricted dev and test capacitylead to conflict, delays, or badtest results in sharedenvironments§ Complex and manualmanagement and configurationtasks result in errors and delays§ Too much bad code going into testand production causes crit sitsand emergency fixes§ Bottlenecks due to inefficientcommunications betweendisparate platforms and teams(Dev/Test - System Programmers;mobile – distributed-mainframe)
  8. 8. Go on OffensePlay Defense…solutions from IBM§ Provide cheap, isolated,development and test environmentsfor project teams– Rational Development and TestEnvironment– Rational Test Virtualization Server– SmartCloud Provisioning– Cloud Ready for Linux on System z§ Automate consistent build,configure, and deploy processesacross all stages– Rational Team Concert– UrbanCode uDeploy– SmartCloud Orchestrator§ Enforce base quality standardsautomatically prior to promotion– Rational Test Workbench– Rational Quality Manager– SmartCloud Application Monitoring– Omegamon§ Improve communication andcollaboration with cross-platformrelease planning– IBM Collaborative LifecycleManagement– Smart Cloud Control Desk– UrbanCode uRelease
  9. 9. TestTestDevDev1DevOps for the common mainframe delivery cycleDev Test Staging ProdDevelopment" Test" SystemProgrammer"32 24
  10. 10. 10 10Test LPARz/OS…Typical z/OS Testing ArchitectureOrganized by project team, vertically scaled, sharing resources, limited automationProjectTeam[April Maintain]ProjectTeam[Prototype SOA]ProjectTeam[June New Func]ProjectTeam[Dec Sys Upgrade]TestDataAppAppAppProblems Encountered1. Shared resources combinedwith overlapping schedules canelicit conflicts, impedeinnovation and slow codedelivery2. Coordination of environmentalchanges and releases causebottlenecks, delays andadditional overhead3. Shared test data is difficult tomanage and can lead to overtesting or incorrect test results
  11. 11. The ultimate in modern application development for System z§  Liberate developers to rapidly prototype new applications§  Develop and test System z applications anywhere, anytime!§  Free up mainframe development MIPS for production capacity§  Eliminate costly delays by reducing dependencies on operations staffNote: This Program is licensed only for development and test of applications that run on IBM z/OS. The Program may not be used to run production workloads of any kind, nor morerobust development workloads including without limitation production module builds, pre-production testing, stress testing, or performance testing.RDz & ISPF userISPF userRDz userRDz userRDz userCOBOL, PL/I, C++, Java, EGL, Batch,Assembler, Debug Toolx86 PC running LinuxRDz userIMSz/OSWASDB2MQCICSRational Development and Test Environment for System z
  12. 12. Simulate subsystem dependencies–  Test impact of latency–  Test application response to unresponsiveservicesCreate a stable test environment–  Simulate “public” services–  Reduce capacity requirements oninfrastructure–  Improve security by reducing access fromexternal servicesImprove testing with Green Hat service simulationDecouple subsystem teams using Green HatDatabases MainframeapplicationsThird-partyServicesRational Test Virtualization ServerApplication changesbeing testedvirtualized services
  13. 13. Testing with dependency virtualizationPhase 1 Phase 2 Phase 3AppTest CaseVirtualServices3rd PartyCallIMSDataAccessCICSCommareaCallAppTest CaseVirtualServices3rd PartyCallIMS DataAccessCICSCommareaCallAppTest CaseVirtualServices3rd PartyCallIMS DataAccessCICSCommareaCallControlled large system testing by isolating components under test•  Easier problem determination•  Lower test environment capacity requirements•  Improved component quality
  14. 14. Provision new dev / test systems in minutes•  Fast VM provisioning for near-instantdeployment of 100s of virtual machines andscale based on business needs•  Rich set of web interfaces into the cloudthat can be driven by a user or scripts forcomplete automation•  Reliable, non-stop cloud capable ofautomatically tolerating and recovering fromsoftware and hardware failures•  Near-zero downtime due to faults,hypervisor/management software upgradesor addition/removal of hardwareRequested  VMs  will  be  up    and  running  under  a    minute  using  standard  HW  FunctionTestPerformanceTest
  15. 15. §  Fast, dependable, automatic feedback speeds time to market§  Lower cost of application testing using off-mainframe z/OS test environment§  Enables confidence by automatically tracking and promoting code healthContinuous Integration for zDeveloperFrequent, rapidfeedback earlierto improvequality Rapid FeedbackCodeCheck In + Build + Deploy +Run Automated TestsChangeRequestAutomated,continuous testingwith isolateddevelopment andtest environmentReusableintegrationtests simplifytesting acrosslayersPromoteTo QAHigher qualitygoing into QAReduced delivery time, end-to-end visibility of test activities, safer and faster upgrades (V2V)Fail fast and drive better quality downstream
  16. 16. System zContinuous Integration for System z Scenario16SCM/CIServer(Rational TeamConcert)TestEnvironment(RD&T or LPAR)TestExecutionManager(Rational QualityManager)TestAutomation(Rational TestWorkbench)1.  Check-in code2.  Build code and zUnittests3.  Deploy build resultsand test data to TestEnvironment4.  Execute zUnit Tests<Deploys App+zUnit Tests><Drives>5.  Kick-off AutomatedTest Plan6.  Run automatedinterface tests againstTest Environment7.  Mark executionrecords Pass/Fail inTest ExecutionManager<Starts Tests>8.  Report test resultsin dashboard/buildresults/defectrecords in CI server.<Results>
  17. 17. § Each tool came with its own•  UI - Web and desktoppresentations of views andtasks•  Logic – Workflow, process,search, query, scale, securityand collaboration•  Storage – Availability,traceability•  Privacy, backup/archive§ Resulting in...•  Brittle integrations•  Silos everywhere•  High cost to maintain andadminister•  Proprietary APIsTool ESCMUILOGICDBUILOGICDBUILOGICDBUILOGICDBUILOGICDBTool BReleasePlanningTool DIncidentManagementTool CReportingTool ADev work ItemsSeparate tools makes collaboration inefficient or difficult...
  18. 18. Tie development release to operational releaseRational Team Concert Release Plan and workitemsSmartCloud Control Desk
  19. 19. 19 19Delivery Organized for Flexibility and SpeedOrganized by application team, horizontally sliced, dedicated resources, highly automatedProblems Encountered1.  Shared resourcescombined with overlappingschedules can elicitconflicts, impede innovationand slow code delivery2.  Coordination ofenvironmental changes andreleases cause bottlenecks,delays and additionaloverhead3.  Shared test data is difficultto manage and can lead toover testing or incorrect testresults4.  Provisioning, managing,and synchronizing projecttest environments includingdataQA/IntegrationTestLPARz/OS LPAR…ProjectTeam[April Maintain]ProjectTeam[Prototype SOA]ProjectTeam[June New Func]ProjectTeam[Dec Sys Upgrade]Integr.TestDataLPARDataRD&TDataRD&TDataLPARData
  20. 20. What are we working on inthe lab…
  21. 21. Go on OffensePlay Defense…solutions from IBM§ Provide cheap, isolated,development and test environmentsfor project teams– Rational Development and TestEnvironment– Rational Test Virtualization Server– SmartCloud Provisioning– Cloud Ready for Linux on System z§ Automate consistent build,provision, configure, and deployprocesses across all stages– Rational Team Concert– SmartCloud Continuous Delivery– SmartCloud Orchestrator*§ Enforce base quality standardsautomatically prior to promotion– Rational Test Workbench– Rational Quality Manager– SmartCloud Application Monitoring– Omegamon§ Improve communication andcollaboration with cross-platformrelease planning– IBM Collaborative LifecycleManagement– Smart Cloud Control DeskCloud-style deploy ofzLinux and z/OS dev andtest patterns on RD&T orzHardware
  22. 22. Infrastructureas CodeSource ControlManagementSource Artifacts.cbl.asm.cpyCLIST.rexxProvisioning using Cloud#!/usr/bin/env rubyclass DevopsDeployerdef initialize(build_url, build_id)@log = Logger.new(LOG_FILE)@log.level = LOG_LEVEL@iaas_gateway = IaasGateway.new(HsltProvider.new(),LOG_FILE, LOG_LEVEL)@server_instance = nilrtc_build_system_provider = RtcBuildSystemProvider.new(RTC_REPOSITORY_URL, RTC_USER_ID, RTC_PASSWORD_FILE)@build = rtc_build_system_provider.resolve_build(build_url, ENV[buildResultUUID], build_id)@build_system_gateway = BuildSystemGateway.new(rtc_build_system_provider, LOG_FILE, LOG_LEVEL)enddef add_build_stamptemplate_file = WEB_APP_ROOT +"/app/templates/pages/page.html"@log.info "Adding build ID stamp #{@build.id} to #{template_file}"# Read in the files contents as a string, replace# the build_id, then overwrite the original contents# of the filetext = File.read(template_file)new_text = text.gsub(/{{ build_id }}/,"<a href="#{@build.uri}">#{@build.id}</a>")File.open(template_file, "w") { |file|file.puts new_text}end# ...
  23. 23. Delivery Pipeline FundamentalsDeployEnvironmentRunning SystemSource ControlManagementSource Artifacts.cbl.asm.cpyCLIST.rexxDeployable ArtifactsBuild,Package,& Unit TestApplicationBinaries &PlatformConfigurationLibrary
  24. 24. Consolidate, standardize, simplify deploymentCOBOLJavaCopybooksWSDLDB2DDLIMS DBD/PSBHTMLMQQueueDefDB2PlansProcsJCLDeployEnvironmentRunning SystemDeployable ArtifactsBuild, Package,& Unit TestApplicationBinaries &PlatformConfigurationLibraryEnterprise Applications have thousands of disparate parts•  Currently maintained in separate systems, if maintained at all•  Limited linkage between systems for application and configurationdependencies•  Missing assets and information is rampantDevOps force linkages, automation, and standardized packaging…Source Management
  25. 25. Create, secure, and deploy test data2TB-SubsetProduction orProduction Clone-Compare-RefreshCreate “right-size”production-like environmentsfor application testingDe-identify sensitive informationwith realistic but fictional data fortesting & development purposesDe-identify sensitive informationwith realistic but fictional data fortesting & development purposesz/OSUTRD&TAutomated test datadeployment for eachbuild and test1 GBz/OSUTLPAR1 GBMasked Test DataAutomated Build &Deploy Test DataAutomatedTestingOptim RTCTest Data
  26. 26. Standardize z/OS region configurations to easedeployment•  Standard topologies exist today(production LPARs)•  Standardized regions which can berepeatedly deployed are rare•  Standardized/Automated deployment ofCOMPLETE system is spottyTo adopt the cloud for testing…Standardize and automate provisioning ofeverything …Standard Middleware PatternCICS 5.1 IMS 11.1DB2 10.1Z/OS 1.12ConfigurationDataApplication
  27. 27. RTC/CIzAvailableCapabilitiesStandardize z/OS region configurations to easedeploymentStandard Middleware PatternCICS 5.1 IMS 11.1DB2 10.1Z/OS 1.12ConfigurationDataApplicationPattern/PlatformApplicationload modulesTest DataJCL and REXX
  28. 28. Evolving to deploying regions … cloud-style“Cloud”RD&TOrLPARRD&TOrLPARRD&TOrLPARRD&TOrLPARSmartCloud Orchestrator+<Deployment Automationfor Mainframe project>Region/MiddlewarePatternsCICS+DB2CICS+ IMSDBBatch
  29. 29. 29Daily Apple TV giveaway§  Complete your session surveys online each day at a conference kiosk or onyour Innovate 2013 Portal!§  Each day that you complete all of that day’s session surveys, your name willbe entered to win the daily Apple TV!§  On Wednesday be sure to complete your full conference evaluation to receiveyour free conference t-shirt!
  30. 30. 30Acknowledgements and disclaimers© Copyright IBM Corporation 2013. All rights reserved.–  U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.IBM, the IBM logo, ibm.com, Rational, the Rational logo, Telelogic, the Telelogic logo, Green Hat, the Green Hat logo, and other IBM productsand services are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, orboth. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™),these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarksmay also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyrightand trademark information” at www.ibm.com/legal/copytrade.shtmlIf you have mentioned trademarks that are not from IBM, please update and add the following lines:[Insert any special third-party trademark names/attributions here]Other company, product, or service names may be trademarks or service marks of others.Availability: References in this presentation to IBM products, programs, or services do not imply that they will be available in all countriesin which IBM operates.The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are providedfor informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to anyparticipant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is providedAS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwiserelated to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creatingany warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable licenseagreement governing the use of IBM software.All customer examples described are presented as illustrations of how those customers have used IBM products and the results they mayhave achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials isintended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenuegrowth or other results.
  31. 31. © Copyright IBM Corporation 2012. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind,express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall havethe effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBMsoftware. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilitiesreferenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or featureavailability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business MachinesCorporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.www.ibm.com/software/rational

×