Mobile to Mainframe - the Challenges of Enterprise DevOps Adoption

  • 4,041 views
Uploaded on

Delivering software is complex. Systems being developed are made up of multiple components, which in turn interact with other systems, services, application servers, data sources and invocations of …

Delivering software is complex. Systems being developed are made up of multiple components, which in turn interact with other systems, services, application servers, data sources and invocations of 3rd party systems. In an Enterprise this complexity is further enhanced by the cross-platform nature of the infrastructure typical enterprises have. While the customers may be interacting with Systems of Engagement using Mobile and Web Apps, the core capabilities of the enterprise that the customers access are in Systems of Record that are running on large datacenters and more than likely Mainframe systems. Keeping these complex systems up and running and constantly updated with the latest capabilities is a task that requires constant coordination between the lines of business, various cross-platform development, QA and operations teams.

DevOps addresses these development and deployment challenges. The goal of DevOps is to align Dev and Ops by introducing a set of principles and practices such as continuous integration and continuous delivery. Cross-platform enterprise Systems take the need for these practices up a level due to their inherent complexity and distributed nature. Such systems need even more care in applying DevOps principles as there are multiple platforms to be targeted, in a coordinated manner, each with its own requirements, quirks, and nuanced needs.

This talk will take a look at the DevOps challenges specific to Cross-platform Enterprise Systems and present Best Practices to address them.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
4,041
On Slideshare
0
From Embeds
0
Number of Embeds
12

Actions

Shares
Downloads
0
Comments
0
Likes
9

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Use the Pace-Layered Application Strategy to Guide Your DevOps Strategy – Gartner, Oct
  • Companies that can close the resulting execution gap stand to benefit. In fact, almost 70 percent of the companies currently leveraging software development for competitive advantage outperform their peers from a profitability standpoint--------------------------------------------------------------------------------------------------Note: Outperformers were determined by a self-assessment of profitability against peers in the industry, ranging from 1 (Significant underperformers) to 5 (Significant outperformers) Significant outperformers were ranked as a 5, Average performers a 3-4 and Underperformers 1-2
  • Another cultural and process gap is that operational orgs and development orgs have very different notions of what it means to be “done, with quality”. Some of these different concerns are described in the text under the ops and dev people above.
  • Main Point: So the idea is to build a continuous delivery pipeline, from ideas through to delivery. Products, services, apps, and infrastructure flow through the pipeline as software and related artifacts, This way, you can get to the speed needed to meet those ever-increasing rates of market shifts and customer demand. You need to consider and leverage to your best use – Mobile, Cloud, Big Data, Social, etc…And there are key intermediate stages of specialized tasks in the delivery pipeline workflow which you can associate as discrete sources of customer pain that can be entry points for targeted solution capabilities – Develop and Test, Release and Deploy, Monitor and Optimize.These capabilities utilize the open Jazz platform to deliver specialized services for the intermediate stages & tasks. And to enable feedback, automation, collaboration, data sharing, and task flow. As well as integration of a partner ecosystem of complementary software & services capabilities. All of the above tuned to accelerate time to value for various new workloads and target platforms… the target delivery environment for the DevOps delivery pipeline.You need to have an Optimization feedback loop,continuously providing: Business performance measures (KPIs) for the delivery pipelineFeedback from customers to the front end of the pipelineMeasures and feedback from intermediate stages of delivery are provided back to up-stream stagesUsed to respond quickly, adjust, and deliver again with improved outcomesTRANSITION… Now let’s talk about what’s new to support this DevOps approach…
  • Definitions to avoid confusion with Tivoli productsProvisioning - box or vm; OS+middleware (these are the provisioning step)Deployment - install the app and configure the middleware (ie Hernandez)
  • We have Green Hat virtualized services today and SCD to automate the build, deploy, and test. What is new here is that we are leveraging the cloud for the GH test virtualization server and we have modified SCD to capture GH configuration data as part of a test environment. This gives us the ability to automate the deployment and setup of a test environment for application changes that automatically configures the GH virtualization stubs, turns them on, and configures the application to use the stubs. All of this is done leveraging the private cloud for its dynamic provisioning behavior giving us the ability to provision dedicated test environments without the dependency of complicated and sometimes costly end point services.

Transcript

  • 1. © 2013 IBM Corporation Mobile to Mainframe The Challenges and Best Practices of Enterprise DevOps Sanjeev Sharma IBM Worldwide Lead – DevOps Technical Sales Executive IT Specialist, IBM Software Group sanjeev.sharma@us.ibm.com @sd_architect © 2013 IBM Corporation
  • 2. © 2013 IBM Corporation Acknowledgements 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,WebSphere, Rational, and IBM Mobile Enterrise are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. 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 trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml 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 countries in which IBM operates. The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it 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, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the 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 IBM software. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.
  • 3. © 2013 IBM Corporation Agenda • A Level set on DevOps • IBM‟s view of DevOps • DevOps and the Enterprise • DevOps for Mobile Apps • DevOps for the Mainframe • Adopting DevOps in The Enterprise o People o Process o Technology
  • 4. © 2013 IBM Corporation Agenda • A Level set on DevOps • IBM‟s view of DevOps • DevOps and the Enterprise • DevOps for Mobile Apps • DevOps for the Mainframe • Adopting DevOps in The Enterprise o People o Process o Technology
  • 5. © 2013 IBM Corporation5 Social, Local, Mobile Smart Infrastructure Analytics ERP Legacy DB CRM HR Manage workloads and maintain security Rapid innovation in the cloud User experience and mobile management New era systems integrate existing operational systems with rapid delivery of new client-facing apps
  • 6. © 2013 IBM Corporation Evolving customer and market expectations Capabilities and User Experience Today Emerging Primary Workload Types Systems of Record Transactional Systems of Engagement (+ Record) Big Data, Analytics, Mobile/Social Channels Time to Value Planned Opportunistic Delivery Model Planned Incremental (DevOps) Development and Operations Team Sizes 100s and Costly 10s with built-in DevOps automation Release Frequency Months to Years Hours to Days, based on business opportunity Integration Frequency Weeks Continuous Service Sourcing Develop Consume and Assemble (Public and Private) Operational Model Systems Management Built in to application, Recovery Oriented Computing, Continuous Availability Infrastructure Deployment Days Minutes Risk Profile Big-Bang (High Risk) Incremental
  • 7. © 2013 IBM Corporation Software Delivery is critical to success 7 54% of companies believe software delivery is critical 25% leverage software delivery effectively today But only… 69% outperform those who don’t leverage software delivery effectively Source: “The Software Edge: How effective software development drives competitive advantage,” IBM Institute of Business Value, March 2013
  • 8. © 2013 IBM Corporation And a lack of continuous delivery impacts the entire business 8 Costly, error prone manual processes and efforts to deliver software across an enterprise CHALLENGES Upgrade risk due to managing multiple application configurations and versions across servers Slow deployment to development and test environments leave teams waiting and unproductive CHALLENGES Operations/ Production Development/ TestCustomers Business Owners Software glitch costs trading firm Knight Capital $440 million in 45 minutes A bad software upgrade at RBS Bank left millions unable to access money for four days New Zealand’s biggest phone company, Telecom paid out $2.7 million to some 47,000 customers who were overcharged after a software glitch
  • 9. © 2013 IBM Corporation Patterns of challenges Differences in dev and ops environments cause failures Backlog of agile releases that Ops cannot handle Manual (tribal) processes for release lack repeatability/speed Lack of feedback and quality metric leads to missed service level targets Daily Build Monthly Delivery Who did this last time? Dave… Dave‟s not here man… Dev Prod
  • 10. © 2013 IBM Corporation Why DevOps? Time to value – Deploy faster. Deploy Often – Reduce cost/time to deliver Developer „Self-service‟ – Allow Developers to Build and Test against „Production-like‟ systems Increase Quality – Reduce cost/time to test – Increase test coverage Increase environment utilization – Virtualize Dev and Test Environments
  • 11. © 2013 IBM Corporation Why DevOps? Deployment – Minimize deployment related downtime – Minimize roll-backs of deployed Apps Defect Resolution – Increase the ability to reproduce and fix defects – Minimize „mean-time-to-resolution‟ (MTTR) – Reduce defect cycle time Collaboration – Reduce challenges related to Dev and Ops collaboration
  • 12. © 2013 IBM Corporation Cultural challenges adopting DevOps DeveloperOperator Why does it take so long to get a test environment? I like using new open source libraries. I‟ve checked in my code now it just needs to be deployed (easy). Application deployment failed again because of new libraries. Our processes ensure environment stability. Development is always making bad operational decisions.
  • 13. © 2013 IBM Corporation Agenda • A Level set on DevOps • IBM’s view of DevOps • DevOps and the Enterprise • DevOps for Mobile Apps • DevOps for the Mainframe • Adopting DevOps in The Enterprise o People o Process o Technology
  • 14. © 2013 IBM Corporation Accelerate Software Delivery Balance speed, cost, quality and risk Reduce time to customer feedback DevOps Enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback 1414 Continuous Innovation, Feedback and Improvements DevOps Lifecycle Operations/ Production Development/ TestCustomers Business Owners
  • 15. © 2013 IBM Corporation DevOps Principles and Values  Develop and test against a production-like system  Iterative and frequent deployments using repeatable and reliable processes  Continuously monitor and validate operational quality characteristics  Amplify feedback loops People Process Tools
  • 16. © 2013 IBM Corporation Agenda • A Level set on DevOps • IBM‟s view of DevOps • DevOps and the Enterprise • DevOps for Mobile Apps • DevOps for the Mainframe • Adopting DevOps in The Enterprise o People o Process o Technology
  • 17. © 2013 IBM Corporation17 Adoption paths to a DevOps approach DevOps Foundation Open Lifecycle and Service Management Integration Platform DevOps Lifecycle Operations/ProductionDevelopment/TestCustomers Business Owners Continuous Innovation, Feedback and Improvements Ecosystem BestPractices Monitor and Optimize Plan and Measure Develop and Test Release and Deploy OSLC
  • 18. © 2013 IBM Corporation18 Heterogeneous Environments Public Cloud Private Cloud Data Warehouse Mainframe Enterprise Service Bus Directory Identity File systems Collaboration Mobile App Routing Service Third-party Services Portals Content Providers EJB Shared ServicesArchives Business Partners Messaging Services DevOps in the Enterprise  Heterogeneous Environments  Multi-technology, multi-vendor  Silo-ed development and deployment  Dev – Ops segregation  Distributed Teams  Supply Chain model  Partners and Suppliers  Water-SCRUM-fall model
  • 19. © 2013 IBM Corporation Agenda • A Level set on DevOps • IBM‟s view of DevOps • DevOps and the Enterprise • DevOps for Mobile Apps • DevOps for the Mainframe • Adopting DevOps in The Enterprise o People o Process o Technology
  • 20. © 2013 IBM Corporation DevOps for Mobile - Challenges  Mobile Apps are the front-end to a complex(enterprise) back-end system – Mobile Apps are rapidly becoming a critical user interface to enterprise systems – But they are just one part of a multi-tier, multi-component application “eco-system” – Developing and delivering mobile apps requires coordination across that whole eco-system Heterogeneous Environments Public Cloud Private Cloud Data Warehouse Mainframe Enterprise Service Bus Directory Identity File systems Collaboration Mobile App Routing Service Third-party Services Portals Content Providers EJB Shared ServicesArchives Business Partners Messaging Services
  • 21. © 2013 IBM Corporation DevOps for Mobile - Challenges  Fragmented Platforms – Multiple mobile operating systems – Multiple devices & form factors – Multiple implementation technology choices  Frequently a mix of technology is involved for mobile app implementation  API and Provisioning Keys need to be governed  App stores add additional asynchronous deployment step
  • 22. © 2013 IBM Corporation Mobile Application Architecture: LinkedIn http://engineering.linkedin.com/testing/continuous-integration-mobile
  • 23. © 2013 IBM Corporation Multi-tier mobile apps present specific challenges to DevOps Middle Tier ServerClient Tier Devices Back-end Data & Services Mobile-specific challenges:  Lots of device targets  Provisioning rules and artifacts  Curated App Stores  Dependent upon backend service versions The Mobile-specific challenge in DevOps is mainly: 1. Dealing with the specific issues in the Mobile Client tier 2. And subsequently coordinating separate pipelines for each tier:  Mobile Client  Middleware  Back-end data and services
  • 24. © 2013 IBM Corporation IBM DevOps for Mobile Applications Build it • Distributed build for each target platform Install it • Automated install to emulators, simulators or devices Test it • Automated functional testing Feedback Application Deploy for Mobile • Automates deployments of multi-tier applications and configuration across multiple environments • Graphical DnD editor replaces scripts • Models environments and keeps track of what is deployed where • ~100 Integrations with key MW targets Application Testing for Mobile • Author automated tests for iOS, Android, Hybrid, and Worklight • Drive automated mobile app tests as part of your continuous integration process For mobile teams who wish to reduce cycle times by automating the deployment and testing of their multi-tier mobile apps Bring your own SCM and CI servers, Application Deploy will:  Instrument your app for test  Deploy your app to device targets  Execute automated tests  Give you the results Rational Test Workbench for mobile Continuous Delivery for Mobile
  • 25. © 2013 IBM Corporation Agenda • A Level set on DevOps • IBM‟s view of DevOps • DevOps and the Enterprise • DevOps for Mobile Apps • DevOps for the Mainframe • Adopting DevOps in The Enterprise o People o Process o Technology
  • 26. © 2013 IBM Corporation Mainframe Delivery Pains…  Multiple teams working across restricted dev and test capacity lead to conflict, delays, or bad test results in shared environments  Complex and manual management and configuration tasks result in errors and delays  Too much bad code going into test and production causes crit sits and emergency fixes  Bottlenecks due to inefficient communications between disparate platforms and teams (Dev/Test - System Programmers; mobile – distributed-mainframe)
  • 27. © 2013 IBM Corporation Go on Offense Play Defense …solutions from IBM  Provide cheap, isolated, development and test environments for project teams – Rational Development and Test Environment – Rational Test Virtualization Server – SmartCloud Provisioning – Cloud Ready for Linux on System z  Automate consistent build, configure, and deploy processes across all stages – Rational Team Concert – uDeploy – SmartCloud Orchestrator  Enforce base quality standards automatically prior to promotion – Rational Test Workbench – Rational Quality Manager – SmartCloud Application Monitoring – Omegamon  Improve communication and collaboration with cross-platform release planning – IBM Collaborative Lifecycle Management – Smart Cloud Control Desk
  • 28. © 2013 IBM Corporation28 28 Test LPAR z/OS … Typical z/OS Testing Architecture Organized by project team, vertically scaled, sharing resources, limited automation Project Team [April Maintain] Project Team [Prototype SOA] Project Team [June New Func] Project Team [Dec Sys Upgrade] Test Data App App App Problems Encountered 1.Shared resources combined with overlapping schedules can elicit conflicts, impede innovation and slow code delivery 2.Coordination of environmental changes and releases cause bottlenecks, delays and additional overhead 3.Shared test data is difficult to manage and can lead to over testing or incorrect test results
  • 29. © 2013 IBM Corporation COBOL, PL/I, C++, Java, EGL, Batch, Assembler, Debug Tool x86 PC running Linux IMS z/OS WAS DB2 MQ CICS Note: 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 more robust development workloads including without limitation production module builds, pre-production testing, stress testing, or performance testing. DevOps Lifecycle Continuous Feedback and Improvements Operations/ProductionDevelopment/TestCustomers Business Owners IBM Continuous Integration Solutions for System Z IBM Rational Test Workbench Rational Development and Test Environment for System z Continuous build and test of distributed systems 29 IBM Application Deploy
  • 30. © 2013 IBM Corporation Agenda • An Level set on DevOps • IBM‟s view of DevOps • DevOps and the Enterprise • DevOps for Mobile Apps • DevOps for the Mainframe • Adopting DevOps in The Enterprise o People o Process o Technology
  • 31. © 2013 IBM Corporation Adopting DevOps in the Enterprise 31 DevOps Foundation Open Lifecycle and Service Management Integration Platform DevOps Lifecycle Operations/ProductionDevelopment/TestCustomers Business Owners Continuous Innovation, Feedback and Improvements Ecosystem BestPractices Monitor and Optimize Plan and Measure Develop and Test Release and Deploy OSLC
  • 32. © 2013 IBM Corporation32 • Common Business Objectives • Vision Statement • Common measures of Success Product Owner Team Member Team Lead Team Member Team Member Senior Executives Users Domain Experts Auditors Gold Owner Support Staff External System Team Operations Staff Adopting DevOps in the Enterprise: People/Culture
  • 33. © 2013 IBM Corporation33 • The case for and against „DevOps Team‟ • NoOps • The DevOps Liaison Team • No overlay layer of bureaucracy Adopting DevOps in the Enterprise: People/Culture
  • 34. © 2013 IBM Corporation34 • Building a DevOps Culture • There is no Silver Bullet • Right People are needed Product Owner Team Member Team Lead Team Member Team Member Senior Executives Users Domain Experts Auditors Gold Owner Support Staff External System Team Operations Staff Adopting DevOps in the Enterprise: People/Culture
  • 35. © 2013 IBM Corporation • Organizational Change „Shift Left‟ – Operational Concerns Build „Application aware‟ Environments Environment Sprints Adopting DevOps in the Enterprise: People/Culture
  • 36. © 2013 IBM Corporation Agenda • An Level set on DevOps • IBM‟s view of DevOps • DevOps and the Enterprise • DevOps for Mobile Apps • DevOps for the Mainframe • Adopting DevOps in The Enterprise o People o Process o Technology
  • 37. © 2013 IBM Corporation37 • DevOps as a Business Process • A Process to get Capabilities from Ideation to Value • Apply Lean Thinking to Processes Adopting DevOps in the Enterprise: Process
  • 38. © 2013 IBM Corporation Key Capabilities 1. Collaborative Development & Continuous Integration 2. Continuous Business Planning 3. Continuous Release and Deploy 4. Continuous Testing 5. Continuous Feedback Adopting DevOps in the Enterprise: Process
  • 39. © 2013 IBM Corporation 1. Collaborative Development and Continuous Integration http://bit.ly/PRQ4a7 Mobile App Developent Teams Enterprise Services Developent Teams Adopting DevOps in the Enterprise: Process
  • 40. © 2013 IBM Corporation 2. Continuous Business Planning 3. Continuous Release and Deploy 4. Continuous Testing 5. Continuous Feedback http://bit.ly/PRQ4a7 Adopting DevOps in the Enterprise: Process
  • 41. © 2013 IBM Corporation Agenda • An Level set on DevOps • IBM‟s view of DevOps • DevOps and the Enterprise • DevOps for Mobile Apps • DevOps for the Mainframe • Adopting DevOps in The Enterprise o People o Process o Technology
  • 42. © 2013 IBM Corporation • Infrastructure as Code/Software Defined Environments package "apache2" do package_name node['apache']['package'] end service "apache2" do case node['platform_family'] when "rhel", "fedora", "suse" service_name "httpd" # If restarted/reloaded too quickly httpd has a habit of failing. # This may happen with multiple recipes notifying apache to restart - like # during the initial bootstrap. restart_command "/sbin/service httpd restart && sleep 1" reload_command "/sbin/service httpd reload && sleep 1" /* REXX */ /* REXX BIND processor sample */ trace o Arg PACKAGE DBRM rcode = 0 /* Set BIND options */ SYSTEM = 'DSN9' i = Pos('(', DBRM) len = Length(DBRM) LIBRARY = Substr(DBRM, 1, i - 1) MEMBER = Substr(DBRM, i + 1, len - i - 1) OWNER = 'DEVDBA' ACTION = 'REPLACE' VALIDATE = 'RUN' ISOLATION = 'CS' EXPLAIN = 'NO' QUALIFIER = 'DEVDBA' Call Bind_it Exit rcode Bind_it: /* Create a bind control statement as a single long line. Then */ /* queue that into a FIFO stack */ DB2_Line = "BIND PACKAGE("PACKAGE")" ||, " LIBRARY('"LIBRARY"')" ||, " MEMBER("MEMBER")" ||, " OWNER("OWNER")" ||, " ACTION("ACTION")" ||, " VALIDATE("VALIDATE")" ||, " ISOLATION("ISOLATION")" ||, " EXPLAIN("EXPLAIN")" ||, " QUALIFIER("QUALIFIER")" /* Write the bind control statement to the data queue and execute */ /* DB2I to perform the bind. */ queue DB2_Line queue "End" Address TSO "DSN SYSTEM("SYSTEM")" rcode = RC Return Rational Automation Framework (WAS, Commerce, MQ…) Adopting DevOps in the Enterprise: Technology
  • 43. © 2013 IBM Corporation Adopting DevOps in the Enterprise: Technology 43 • Common Collaboration Tools • Common Work Item Management Tool • Dashboards to show status/progress
  • 44. © 2013 IBM Corporation IBM acquires UrbanCode Expand DevOps capabilities and accelerate plans Release and Deploy
  • 45. © 2013 IBM Corporation IBM announces the acquisition of UrbanCode Inc. Enhancing Continuous Release and Deployment:  Drive down cost by automating manual tasks, eliminating wait-time and rework  Speed time to market by increasing the frequency of software delivery  Reduce risk through increased compliance of application deployments. 45 Deployment Complements our DevOps solution:  Deliver a differentiated and engaging customer experience by reducing time to customer feedback  Quicker time-to-value of software-based innovation with improved predictability and success  Increased capacity to innovate by reducing waste and rework in order to shift resources to high-value activities Complementing our DevOps solution, combining IBM and UrbanCode, will enable clients to more rapidly deliver mobile, cloud, big data analytics and traditional applications.
  • 46. © 2013 IBM Corporation Line of Business SmartCloud Orchestrator IBM Pure Application System Openstack Jenkins Rational Build Forge uBuild DevOps Tool Chain Plan and Measure Develop and Test Release and Deploy Monitor and Optimize Rational Focal Point Rational Requirements Composer Rational Team Concert Rational Quality Manager Rational Test Workbench Rational Test Virtualization Server SmartCloud Control Desk SmartCloud Application Performance Management
  • 47. © 2013 IBM Corporation Line of Business SmartCloud Orchestrator IBM Pure Application System Openstack Jenkins Rational Build Forge uBuild DevOps Tool Chain Plan and Measure Develop and Test Release and Deploy Monitor and Optimize Rational Focal Point Rational Requirements Composer Rational Team Concert Rational Quality Manager Rational Test Workbench Rational Test Virtualization Server SmartCloud Control Desk SmartCloud Application Performance Management
  • 48. © 2013 IBM Corporation DevOps Adoption Maturity  Common Source Control  Automated Builds (Build Definitions)  Continuous Integration (CI)  Automated Delivery  Continuous Delivery to Test (CD)  Continuous Delivery to Production-like Systems (Infrastructure as Code)  Continuous Delivery thru Prod
  • 49. © 2013 IBM Corporation Continuous testing with virtualized services Avoid testing bottlenecks due to dependencies on external services • Automate setup and management of test virtualization server in the cloud • Automates configuration of virtualized services for an application under test • Automate setup of production-like test environments with low cost Databases Mainframe applications Third-party Services Rational Test Virtualization Server App deploy Application changes being tested virtualized services IBM SmartCloud Orchestrator IBM PureApplication System SIT FVT IBM Rational Test Workbench
  • 50. © 2013 IBM Corporation What is Service Simulation and Test Virtualization? Test Virtualization enables to create “virtual services”: –Virtual Services simulate the behavior of an entire application or system during testing –Virtual Services can run on commodity hardware, private cloud, public cloud –Each developer, tester can easily have their own test environment –Developer and testers continue to use their testing tools (Manual, Web performance, UI test automation) 50 Capture &Model System dependencies are a key challenge in setting up test environments: Unavailable/inaccessible: Testing is constrained due to production schedules, security restrictions, contention between teams, or because they are still under development Costly 3rd party access fees: Developing or testing against Cloud-based or other shared services can result in costly usage fees Impractical hardware-based virtualization: Systems are either too difficult (mainframes) or remote (third-party services) to replicate via traditional hardware-based virtualization approaches Heterogeneous Environments Public Cloud Private Cloud Data Warehouse Mainframe Enterprise Service Bus Directory Identity File systems Collaboration App Under TestRouting Service Third-party Services Portals Content Providers EJB Shared ServicesArchives Business Partners Messaging Services Databases Mainframe applications App Under Test Third-party Services Packaged apps, messaging services, etc. Virtual Services
  • 51. © 2013 IBM Corporation Testing with dependency virtualization Phase 1 Phase 2 Phase 3 App Test Case Virtual Services 3rd Party Call IMS Data Access CICS Commarea Call App Test Case Virtual Services 3rd Party Call IMS Data Access CICS Commarea Call App Test Case Virtual Services 3rd Party Call IMS Data Access CICS Commarea Call Controlled large system testing by isolating components under test • Easier problem determination • Lower test environment capacity requirements • Improved component quality
  • 52. © 2013 IBM Corporation Where to get more information?  UrbanCode – an IBM Company – http://www.urbancode.com  IBM Enterprise DevOps blog – http://ibm.co/JrPVGR  6 Ways for Enterprises to Adopt DevOps blog – http://ibm.co/xq71xY  My DevOps Blog – https://bit.ly/sdarchitect
  • 53. © 2013 IBM Corporation www.ibm.com/software/rational
  • 54. © 2013 IBM Corporation © 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 have the 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 IBM software. 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 capabilities referenced 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 feature availability 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 Machines Corporation, 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
  • 55. 55