1 / 47

Application Deployment Challenges

Deployment errors result in roll-backs and unplanned down-time of business critical applications. Lost Revenue or Productivity. Lack of an auditable deployment process hinders ability to comply with external regulations. Penalties, Shareholder Value.

rigg
Télécharger la présentation

Application Deployment Challenges

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Deployment errors result in roll-backs and unplanned down-time of business critical applications Lost Revenue or Productivity Lack of an auditable deployment process hinders ability to comply with external regulations Penalties, Shareholder Value Manually configuring complex applications to deployment servers results in inefficient use of IT resources High Labor Costs Inability to ensure the test environment matches production results in quality problems and slow problemresolution Customer Dissatisfaction Application Deployment Challenges

  2. System Deployments Increasingly Complex A Composite Web Application, Involving J2EE, Integration Middleware, and Legacy Systems

  3. Development Operations Application Tests Where these Executable Of this This Produced these Release Test Results System Implemented these Requirements on this Which required these Environment Changes In this Implemented with this Approval Source Code Built using these Approved by Which deployed these Build Scripts Build Artifacts Deployment Artifacts Can You Trace Your Artifacts?

  4. Compliance Need to be able to track software from development to production and back again Repeatability & Reliability Need to reliably deploy software through multiple test phases and ultimately to production: Process – A need to apply a standardized set of steps in an organization Server Configurations – Need production server configurations that match test lab configurations, to avoid errors in deployment Change – Changes cause failures due to lack of understanding of how application is currently deployed, and impact of new application on existing system Security – Authentication and electronic signature approvals Lifecycle Automation Be able to queue multiple automation efforts into a single automated process Build -> Deploy ->Test as a single automated process Build and Deployment Motivators

  5. Managing Builds and Deployment Change Management Build Management Application Deployment Summary Agenda

  6. E-SIG Developer Deployer Build Engineer Tester ProjectManager Typical Deployment Cycle Implement Build & Stage Provision & Validate Server(s) System Test Approve In Production Integration Test Defects User Acceptance

  7. Managing Builds and Deployment Change Management Build Management Application Deployment Summary Agenda

  8. How can I create and enforce a repeatable process for deploying applications through test environments prior to going into production? How can I ensure the build that was approved during testing is the same build deployed into production? How can I prevent unauthorized tampering of the build artifacts? Can I recreate the build currently deployed in a specific environment? What build artifacts are loaded on Testing Servers? The Production Servers? How can we load different machines with the same application version simultaneously? Build and Deployment Questions

  9. Release Deployment Record Approval Approval Team Member Build Environment (Integration Test, Pre-Production, Production) Build Environment (Integration Test, Pre-Production, Production) Build Environment (Function Test, Performance Test, Production) Role (Dev, QE, Project Manager, Operations Manager) Build and Deploy Tracking Records in ClearQuest Approval UCM Project Activities Activities Activities

  10. Define the Release Project Manager creates a Release record to represent the release Choosing a UCM Project to associate with the release provides a link to UCM activities

  11. Define the Roles Defining role names modeled on the role hierarchy in your organization Project Manager creates one or more Roles and associate them with a Release

  12. Define the Environments Project Manager creates one or many Test Environments for a Release System Test Integration Test Pre-Production Production

  13. Team Member Build and Deploy Tracking Records in ClearQuest Release Deployment Record Approval Approval Approval UCM Project Build Environment (Integration Test, Pre-Production, Production) Build Environment (Integration Test, Pre-Production, Production) Build Environment (Function Test, Performance Test, Production) Activities Activities Activities Role (Dev, QE, Project Manager, Operations Manager)

  14. A Build Record in CQ is for tracking build results related to compliance traceability The build record has a pre-defined workflow and is a stateful record with the following states: Submitted - build has been started Completed - build has completed without errors Failed - build has failed Retired - this build record is no longer relevant. Build Tracking

  15. Create a Build Record Communicate status of the build: Submitted Complete, Failed, Retired Aggregate build records for each release

  16. In this demo, Pat will: Define: The release The roles The test environments Create Build Record Pat Demo One: Managing Builds and Deployment Release 1.5 Environment 1 System Test Environment 2 Integration Test Environment 3 Pre-Production Test Environment 4 Production Role Test Manager approves deployment Role Project Manager approves deployment Role Operations Manager approves deployment Role Operations Manager approves deployment

  17. What Got Configured in ClearQuest?

  18. Team Member Deployment Tracking Release Deployment Record Approval Approval Approval UCM Project Build Environment (Integration Test, Pre-Production, Production) Build Environment (Integration Test, Pre-Production, Production) Build Environment (Function Test, Performance Test, Production) Activities Activities Activities Role (Dev, QE, Project Manager, Operations Manager)

  19. For each Release, define the test environments and approvals needed Create Deployment records that track the state of a deployment through the test environments Create Deployment Units to describe which managed artifacts to deploy Optionally link the deployment record to build record(s) for traceability between the build and the deployment E-SIG Tester Project Manager Deployment Tracking System Test Approve Integration Test User Acceptance

  20. Indicates current state for the environment Deployment tracked for a release Records move through the pre-determined environments Approvals provide auditable gates for deploying into an environment Versioned Deployment Units identify build artifacts to deploy Deployment Tracking

  21. Preparing the Deployment Unit ClearCase 1. Create Deployment Unit “template” Create View of build artifacts Capture list of files Check into ClearCase MyApp.xml ClearCase 2.Create build specific Deployment Unit Build the system Check-in the build artifacts Capture version information Check in Deployment Unit MyDU.xml Deployment Record 3.Create Deployment Record ThisApp Create Deployment Record in CQ Associate the Deployment Unit MyDU.xml

  22. <?xml version="1.0" encoding="UTF-8" ?> <tracking:deployment_unit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tracking="http://www.ibm.com/deployment/schema/deploymentTracking.xsd" name="My Test Application" version="1.0"> <history changeOperation="Generate" changeNote="" user="medawson" hostname="melamine.yourco.com" datetime="2005-11-02T09:13:38-0500" /> <file path="/vobs/test_vob/shlib/foo.so" orig_path="foo.so" /> <file path="/vobs/test_vob/shlib/bar.so" orig_path="bar.so" /> <file path="/vobs/test_vob/shlib/baz.so" orig_path="baz.so" /> <file path="/vobs/test_vob/shlib/linked_foo.txt" orig_path="linked_foo.txt" /> </tracking:deployment_unit> Example Deployment Unit Template Schema Info Changes to this file List of files & their location

  23. Review the Deployment Unit Template Review the Deployment Unit Create a Deployment Record Move a Deployment Record Through Test Environments Demo Two – Deployment Tracking Project Manager, Pat Operations Manager, Lou Test Manager, Dana Operations Manager, Lou System Test Integration Test Pre-Production Production

  24. Summary of What Got Configured in ClearQuest

  25. Managing Builds and Deployment Change Management Build Management Application Deployment Summary Agenda

  26. The Hub for Lifecycle Management Govern the test and development process IBM Rational ClearQuest Test Change Defects Single project view Global test project coordination Configurable, enforceable processes Extensible test ecosystem IBM Rational ClearQuest

  27. Simplifies key SCM functions and workflows Easy to adopt Optimized for team productivity Based on hundreds of successful CM implementations Activity Based Change Management Manages High-level Objects Unified Change Management Manage Activities • To Do Lists • Automated Workflow Manage Assets • Versioning: code, models, XML, HTML • Parallel development • Components • Streams • Baselines • Activities IBM Rational ClearCase and IBM Rational ClearQuest

  28. GUI Feature New Promo C B Defect 3452 BL1 Unified Change Management Raising the Level of Abstraction • Projects • A collection of related work with enforced policesand a built-in integration area • Activities • All changes have associated activity • Automatically collect change set • Components • Group related artifacts that make up subsystems • Baselined together as a unit • Streams • Define consistent configurations of versions • Provide the balance of isolation and sharing • Baselines • Represent versions of entire components • Support configurable promotion levels

  29. UCM activities automatically manage change sets Activities in IBM Rational ClearQuest track IBM Rational ClearCase assets Developers, integrators, and testers work with activities, not low-level assets ClearQuest:Organized Activities ClearQuest Manages activities • To Do Lists • Workflow ClearCase Manages assets • Versioning: code, models, XML, HTML • Parallel development Change Set Special Promo a. html V5 b. xml V3 c. jpg V8 Unified Change Management Request Priority Owner Special Promo 1 Terry Bug 527 2 Sandy Add GUI button 2 Kim

  30. Web-based banking application (the “RatlBankWeb” application) Deployed to Apache Tomcat Web server Release 2 under development Contains defect that needs to be resolved Demo Three – Modifying the Application

  31. Pat – Project Manager Dana – Tester / Deployer Alex – Developer Jan – Builder Pat Alex Dana Jan Demo Three Roles

  32. Managing Builds and Deployment Change Management Build Management Application Deployment Summary Agenda

  33. Rational BuildForge – Global Offering Translated and available in 10 different languages! Portuguese, Chinese-simplified, Chinese-traditional, English, French, German, Italian, Japanese, Korean, Spanish

  34. BUILD/RELEASE FRAMEWORK Management Console Centralized Web-based, Collaborative Distributed Access, Role-Based Security IDE Plug-Ins Developer Self-Service, Role-Based Security Workflow Control Acceleration Notification Scheduling Log Analysis Tracking Reporting Process Automation Automated, Repeatable Application Development Lifecycle Package Source Control Product Build Development Quality Assurance Release Scripting Python, VBscript, Batch, Perl, KSH Languages Source Control IDEs Change Mgmt Build Tools Test Tools Release Tools • ClearMake • Ant • NAnt • Make • GNUMake • NMake • Open Source • etc. • Tivoli • WebSphere • WebLogic • WIS • etc. • TestManager • Performance • Functional • Robot • LoadRunner • TestDirector • WinRunner • Junit • etc. • RAD • Eclipse • Visual .NET • ClearCase • StarTeam • Perforce • CVS • PVCS • VSS • Synergy • Subversion • etc. • ClearQuest • Remedy • ChangeMan • DevTrack • Bugzilla • etc. • Java • C • C++ • C# • etc. UNIX, Windows Mac, Linux, Proprietary Platforms System Overview

  35. Source Code Repositories Test Suites Deployment Tools SCM Applications Functional Architecture IMPLEMENT ACCESS EXECUTE Build Forge Management Console Build Forge Server Build Forge Agents Build Systems Server Pools • Build Forge Engine • 3 Tier Architecture • Centrally Managed • Orchestrates BuildForge Tasks AIX Linux Windows Windows Windows • Manage Users • Configure Resources • Set up Projects and Steps • Schedule Process Execution • View Real-Time Status • Troubleshoot Issues • Reporting & Analysis • Build Forge Database • Projects and Steps • Server Configurations • Environment Configurations • User/Permission Information • Project/Process Statistics • System Master Log Windows Solaris Mac Linux Z-Series HP-UX Quality Assurance DB2 Oracle MySQL SQL Server Sybase Build Forge IDE Plugin Windows Solaris Mac Linux HP-UX AIX Production • Integration • Command Line • Adaptors • API Windows Solaris Linux HP-UX AIX • Agents • Real Time Environment Configuration • Execute Project Steps • Return Output / Logs to Mgmt Server • Developer Self Service

  36. Alex - Developer Pat – Project Manager Dana - Tester Dana - Deployer Jan - Builder Demo Four – Build Application Using BuildForge Examine intg. build project & Execute Examine build results View auto resolved defect View changeset & baseline info Examine auto created build record Submit deployment request

  37. Managing Builds and Deployment Change Management Build Management Application Deployment Summary Agenda

  38. Build and Deployment Tracking Release Deployment Record Created by Build Engineer UCM Project Build Build Build Created by Build Forge Activities Activities Build Forge ‘resolves’ activity and adds reference to build Activities

  39. Build and Deployment Tracking Release Deployment Record Approval Approval Approval (RatlBankWeb 2.0) Environment (Integration Test, Pre-Production, Production) Environment (Integration Test, Pre-Production, Production) Environment Project Manager approves deployment of Release 2.0 to System Test environment (System Test) Role (Project Manager)

  40. Use Rational ClearCase and Build Forge to deploy a baselined version of an application Track the deployment via ClearQuest Approach

  41. Demo Five: Deploy Using Rational BuildForge Release Deployment Record Approval Approval Approval (RatlBankWeb 2.0) Environment (Integration Test, Pre-Production, Production) Environment (Integration Test, Pre-Production, Production) Environment Project Manager approves deployment of Release 2.0 to System Test environment (System Test) Role (Project Manager)

  42. Managing Builds and Deployment Change Management Build Management Application Deployment Summary Agenda

  43. Describe Build and Deployment Challenges Discuss Build and Deployment tracking in Rational ClearQuest Identify a Build and Deployment workflow Introduce Rational Build Forge Session Summary

  44. We appreciate your feedback in order to improve this educational event.Please fill out the survey form.

More Related