1 / 58

DevOps for the CA Plex professional

CA Plex Modern Devops. DevOps for the CA Plex professional. Workshop Overview. We will make a DevOps overview and how CM MatchPoint and partner products can fit in the DevOps Toolchain. Also Lily will show how to deploy a WebClient Application on cloud / container deployment. Speakers.

jaggers
Télécharger la présentation

DevOps for the CA Plex professional

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. CA Plex Modern Devops DevOps for the CA Plex professional

  2. Workshop Overview We will make a DevOps overview and how CM MatchPoint and partner products can fit in the DevOps Toolchain. Also Lily will show how to deploy a WebClient Application on cloud / container deployment

  3. Speakers Eric Giron Senior Consultant Lily Taharudin Senior Consultant Christoph Heinrich BusinessDevelopment

  4. Agenda • Problems that DevOps Solves • How company work Today • Pains in today's companies • About Waste • Introducing DevOps? • Benefit of Devops • Common pitfalls to avoid moving to devops • Best Practices to Ensure Quality • Transition to DevOps • Change the Culture • Change theOrganization • Addressing DevOps Objections • Introducing DevOps Automation • DevOps Toolchain • Why use tools? • DevOps on a CA Plex Shop • Challenges • Solutions • CM MatchPoint Overview • TestComplete Overview • Workshop • CM MatchPoint Workshop Environment Setup Overview • Training Exercises

  5. How most company works today • Complex Deployment Pipeline • Many handoffs • Several Teams involved • Manuel intervention • Downtime Expected • COTS vs Custom Software • Buy Vs Build • Commercial Software update 3-5 years • Products customized beyond recognition • Custom software use in each department • Project Mindset • Projects funded and team formed • After deployment teams disperses and app handled to operations • Documentation • Optimized for cost, Not speed • I.T. priority given to cost savings • Focus on maximizing I.T. efficiency • Value placed on stability and predictably rather than changeability

  6. Pains in today's companies • Serious outages • No Incremental Value • Excessive Infighting

  7. Waste Anything that takes time but doesn’t add value for the customer

  8. Type of Waste Transportation Waste Moving things without adding value Impact on waiting waste Correction Waste Product isn't usable and rework is required Happens when quality  not build into the process Inventory Waste Things are piling up and not realizing value Causes lumpy processing Over-Production Waster Sometimes done to keep staff busy • Knowledge Waste • Disrupting flow of knowledge • Disrupting absorption of knowledge • Waiting Waste • Uneven processing • Highly specialized personnel • Over-Processing Waste • Doing more work that required • Not knowing the requirements • Motion Waste • Unnecessary movement by people

  9. Introduction to DevOps

  10. What do you want to Accomplish? • Increase the value given to the customer • Respect your People

  11. What is Lean ? • Focus on customer • Eliminate Waste • One-piece flow • Shared, continuous learning • Eliminate overburden of people/equipment • Theory of constraints

  12. Defining DevOps C.A.L.M.S • Culture, People and process at the forefront • Automation, Repeatability by automating activities • Lean, Applying lean principles to IT • Metrics, Measure extensively and use to improve • Sharing, Continuous learning y sharing knowledge

  13. What is DevOps? DevOps is a holistic culture of collaboration between development and operations teams, achieved by optimizing people, tools and processes. Dev teams: Business stakeholders, product managers, designers, developers and testers Ops teams: Release engineers, network specialists, systems engineers, operations and security teams.

  14. Does DevOps Matter? • 2604x faster time to recover from incidents • 46x more frequent code deployments • 1.53x more likely to meet or exceed business goals • 1.8x more likely to recommend their team to others 2018 Accelerate State of DevOps report by Dr. Forsgren and team

  15. Benefits of DevOps • Software delivery with minimum risk and disruption Builds cross-team collaboration and culture Faster software releases and value creation

  16. Common Pitfalls to Avoid when Moving to DevOps ? • Faster releases but neglecting user value Different perceptions among stakeholders Lack of optimum toolchain

  17. Best Practices to Ensure Quality while Moving Faster with DevOps • Collaboration • Feedback and Monitoring • Automation • Service Virtualization

  18. Transition to DevOps

  19. Changing the Culture: Re-establish your purpose • Shared objectives • Empathize with customer • Doing some "agile" motions/ceremonies • Misalignment doom efforts

  20. Change of Culture: Empowerment • Trust the team, let them take ownership • Employees do what's is needed to run the services • Anyone can "pull the cord" • Teams forge during crisis to resolve issues

  21. Change Culture: Accountability • Promote Accountability • Can't have empowerment without accountability • Built quality into the process • Share commitment to excellence • Reward who deliver and take responsibility

  22. Change Culture: Teamwork • All disciplines working together, in crisis or in daily operations • Respect unique skill sets • Find excuses the get the team together • Don’t reward the "lone genius" or firefighter

  23. Change Culture:  Learning • Encourage continuous learning • Offer resource and time to learn • Encourage experimentation • Conduct blameless postmortems • Make it easy to share and discover information

  24. Change Culture: Reinforce Values • Live your values, not just print/say them • What triggers promotions? • Managers must lead by example

  25. Change Organization: Understand Customer and Bottlenecks • Build up and value empathy for users • Step back and "see" the systems in place • Its ineffective to optimize anywhere but the constrains

  26. Change Organization: Remove inconsistencies via automation • Aim for similar if not the same configurations for environment for DEV, QA and Production • Aim for on-demand environment with no configuration drift • Automate the path to production

  27. Change Organization: Build Quality and Break down Communication barriers • QA Teams aren't responsible for quality • Test early and often • Poor communication results in push not pull-based systems

  28. Change Organization: Rethink Team Approach • Functional teams of specialist can create waste, uneven flow • Moving from projects to Products • Create Teams around core products • You need complete teams DevOps is a re-org, not a new team to hire, Adrian Cockcroft

  29. Change Organization: Eliminate Waste • Policies and procedures get heavier over time, return to intent • Automate manual steps wherever is possible

  30. DevOps Objections • DevOps makes us less secure • Developers pushing to production? • We have offshore teams • Co-Locations of teams isn't always possible • Nature of outsource parentship needs to be review • Elimination of Ops team? • Operations is more operation, but role change • Is about running platforms, creating API, delivering pipelines • Too much of COTS and legacy code • TDD, continuous integration, deployment automation is possible with legacy environments • The point isn't just pushing code faster, but improve the flow • We don’t have the skills • An investment worth making • Many of this are "soft" skills

  31. Introducing DevOps Automation The Right Technologies to Enable DevOps

  32. Things to remember about DevOps and Tools • The goal is continuous improvement • You cannot "buy" DevOps • Tool adoption happens in stages

  33. The DevOps Toolchain Monitor and Loggin Communications Knowledge Sharing Claud Platforms Configuration Management Continuous Integration Continuous Deployment Build Testing Source Control Issue Tracking Planning

  34. Why use Tools? • Define the right process for your needs • Choose the right tools for your needs • Capturing every request • Communication • Continuous Development • Continuous Integration • Continuous Testing • Continuous Deployment

  35. Planning Tools • Why it Matters: Shared purpose, transparency, empowerment • GitLab • TaskTop • Trello • Azzure Boards

  36. Issue Tracking Tools • Why it matters: Customer responsiveness, limited knowledge waste, feed back Loop • CM MatchPoint • Zendesk • Zoho Desk

  37. Source Control Management Tools • Why it Matters: Asset control, limit transportation waste, empower team • SubVersion + CM MatchPoint SVN Integration • Git • GitHub

  38. Build Tools • Why it matters: Consistent packaging, automates and error-prone activity, yields early quality signals • CM MatchPoint Autogen/Build (Multiple language) • CM MatchPoint Packaging Tool (web applications) • Maven/Gradle • Rake

  39. Testing Tools • Why it Matters: Put focus on built-in quality, creates confidence in deployed artifacts • SmartBear TestComplete + CM MatchPoint User define Process • Junit • Jasmin

  40. Continuous integration tools • Why It matters: Fast feedback, reduce defect waste and waiting waste • CM MatchPoint Model Manager + SVN Integration • SVN Integration • Autogen/Build tool • Packaging Tool • Jenkins

  41. Continuous Deployment Tools • Why it matters: Limit your pre-production inventory, automate complex pipelines, unify team around getting value to customer • CM Match Point Promotion process • Spinnaker • Octopus Deploy

  42. Continuous Management Tools • Why it matters: Enforce consistency, treat infrastructure as code • Terraform • Chef • Google cloud deployment manager

  43. Cloud Platform • Why it Matters: Automation-friendly, observable runtimes for software • Amazon Web Servers • Microsoft Azure

  44. Monitoring an Logging Tools • Why it Matters: Fast recovery, responsiveness, transparency, limited human involvement during incidents • Azure Monitor • Prometheus • Zipkin

  45. Communication Tools • Why it Matters: Connect teams, limit waiting waste, improve collaboration • Slack • MS Team • Google Handouts

  46. Knowledge Sharing Tools • Why it Matters: Reduce knowledge waste, increase new-hire productivity, limit repeat mistakes • GitHub Pages • Confluence • Wiki

  47. DevOps on a CA Plex Shop

  48. Challenges • Manage Requests and Changes • Handle Audit Requirements • CA Plex Model Management • Model Extract/Updates • Performance • Documentation • Versioning/Backup • Audits • CA Plex Gen & Build • CA Plex crashes during large Gen&Builds • Automated Gen&Build and Deployment • Local and Shared Environments • Deployment on distributed • Automated Test • Repetition and People Boredom, Less Reliable • Time for Feedback- Release • Consistency • And more….

  49. Solutions • Manage Requests and Changes • CM MatchPoint Change Request Management • CA Plex Model Management • Model Manager integrated into DevOps process • Documentation/Audit • Backup/Versioning of Group and Local Models • Subversion Integration for Group and Local Models • Update/Extract performance for remote locations • CA Plex Gen & Build • Unattended Gen&Build for multiple variants/versions/systems • Selective builds for cumulative change requests • Subversion integration for • Automated Test • CM MatchPoint Integration whit SmartBear Tescomplete for Tests and Results

  50. MatchPoint Overview • CM MatchPoint is the premier CM (change management) product for Plex. • Change Request Management • Provides information about the activities associated with each change request so you can understand and manage dependencies. • Built In Workflow • Get immediate value from purpose designed workflows that also support user defined processes. • Scheduled deployments • Production changes are automatically deployed to production systems. • Project Information • Reporting based on projects includes information about cost., team members, timelines and timesheets, which facilitates billing. • Customer Information • Assign customers to change requests to enable reporting and chargeback.

More Related