• Save
DevOps 101 for Government
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

DevOps 101 for Government

  • 2,842 views
Uploaded on

Basics introduction to DevOps for Government customers

Basics introduction to DevOps for Government customers

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Hi Sanjeev,
    Very useful presentation
    Sachin
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
2,842
On Slideshare
2,836
From Embeds
6
Number of Embeds
3

Actions

Shares
Downloads
0
Comments
1
Likes
3

Embeds 6

http://www.linkedin.com 2
http://192.168.33.10 2
http://w3.skycode.biz 2

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
  • Mandatory closing slide (1 of 2) <br /> Acknowledgements and disclaimers <br /> IBMers must include This mandatory “Acknowledgements and Disclaimers” slide at the end of your presentation before the closing “Thank You” slide. <br /> - You will need to customize the “Acknowledgements and Disclaimers” text in red appropriately. <br />
  • Main Point: We know organizations have a gap between the software delivery capabilities they need to succeed and the ones they have in house currently. Successful organizations know that when they improve their abilities in this area, they increase their success. <br /> In fact a recent IBV study where organizations self-reported that... Insights from 435 executives in 58 countries, spanning 18 industries <br /> 85% realize and reported it is important to critical <br /> Only 25% say they are able to fully leverage software delivery effectively <br /> So there is a gap -- but when companies that can close the resulting execution gap stand to benefit. <br /> Almost 70 percent of the companies currently leveraging software development for competitive advantage outperform their peers from a profitability standpoint <br /> TRANSITION – so there is a huge opportunity for our clients to close that gap…let’s move to the next slide and talk about how <br /> -------------------------------------------------------------------------------------------------- <br /> 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 <br /> new Rational/WebSphere IBV Study "The Software Edge - How effective software development drives competitive advantage" <br /> This study examined the correlation between software delivery competency and industry competitive advantage <br /> Insights from 435 executives in 58 countries, spanning 18 industries <br /> Roles included executives at director level and above in IT and other software organizations <br /> Software delivery refers to all areas of development, operations, and support within IT and other development / engineering organizations <br /> “There was 54% of the companies who said they believe software is critical and 32 percent who called it moderately important – so that’s 86 percent of the respondents say software is either critical or moderately important and that points to the need for better tooling for software development and delivery.” said Randy Newell, director of capabilities marketing for IBM Software Group with a focus on the Rational brand. <br />
  • http://gizmodo.com/5931284/software-glitch-costs-trading-firm-440-million-in-45-minutes <br /> http://www.theregister.co.uk/2012/06/25/rbs_natwest_what_went_wrong/ <br /> http://business.scoop.co.nz/2011/10/19/telecom-makes-2-7m-settlement-for-incorrect-meter-readings/ <br />
  • From the Agenda: <br /> In this “new normal,” the most forward thinking companies will: Establish an enterprise capability for accelerated delivery of software that enables them to seize market opportunities and reduce time to customer feedback, improve governance while balancing quality and cost <br />
  • Continuous release and deployment: Continuous release and deployment provides a continuous delivery pipeline that automates deployments to test and production environments. It reduces the amount of manual labor, resource wait-time, and rework by means of push-button deployments that allow higher frequency of releases,reduced errors, and end-to-end transparency for compliance. <br /> ibm.com/software/products/us/en/continuousdelivery/ <br /> WebMD: <br /> 1. Problem: WebMD offers numerous online applications that provide information to clients on critical health issues. As they made the move to an agile methodology, they needed to reduce the cost of deployments in able to be more iterative. <br /> 2. Solution: Deployment automation for both test and production leveraging UrbanCode’s uDeploy. <br /> 3. Result: Before it took 2 days to deploy a build, with uDeploy, it takes us less than 60 seconds. <br />
  • &lt;> <br /> UrbanCode improves software delivery enabling continuous release and deployment via application release automation, helping to drive down costs, speed time to market and reduce risk. <br />
  • Deployment Automation Developer or Deploy Administrator imports the AMC Plug-in into Deploy. The Plug-in is configured to auto-discover WAS installs on specific resources so when the agent comes on-line it will invoke the AMC plug-in which will discover the cell topology and create WAS Cell and WAS Cluster subresources back on the Deploy server. <br /> A Middleware Administrator or Application Developer unzips the AMC plug-in on a system that has connectivity to the exemplar WAS cell <br /> The Middleware Administrator or Application Developer will run a script packaged in the AMC plug-in that will prompt for some information, then discover and import configuration from the exemplar WAS cell <br /> The AMC template creation script will ask the user for a base product template (e.g. WAS v8.5) and to chose what configuration data from the imported cell should be added (either only cell scoped configuration or a cluster configuration). Note that if any custom tokens are required (e.g. host specific information like JDBC connection URL, etc.), then the Middleware Administrator or Application Developer will need to open the appropriate template file up for editing and insert the tokens manually. They will then need to create appropriate properties on the appropriate WAS Cell/Cluster resources to ensure the token substitution happens correctly during deployment (this is not directly shown in the diagram above for the sake of clarity). <br /> The AMC template creation script will prompt the user for information required to connect to a Deploy server, including the name of the WAS configuration component and will create/update the template in CodeStation. <br /> The Deployment Automation Developer should now have all the Deploy artifacts he needs to assemble the Application including deploy/undeploy processes <br /> The application, including WAS configuration, can be deployed and promoted across all environments defined in the application <br />
  • Industry pattern is to target a subset of devices and progressively roll out – Facebook, Mailbox <br />
  • Optional slide. Graphic is available in English only. <br />
  • Mandatory closing slide (2 of 2) <br /> Thank You Slide (available in English only). <br />

Transcript

  • 1. DevOps 101 Concepts and Overview – DevOps for Government Sanjeev Sharma IBM WorldWide Lead – DevOps Technical Sales sanjeev.sharma@us.ibm.com DevOps Blog: http://bit.ly/sdarchitect Twitter: @sd_architect Author: DevOps for Dummies – http://ibm.co/devopsfordummies © 2013 IBM Corporation
  • 2. Acknowledgements and disclaimers 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. © 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 products and services 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 If 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. 2
  • 3. Agenda • • • • Why DevOps? What is DevOps? Adopting DevOps o People o Process o Technology IBM DevOps Solution
  • 4. Agenda • • • • Why DevOps? What is DevOps? Adopting DevOps o People o Process o Technology IBM DevOps Solution
  • 5. Organizations that effectively leverage software innovation outperform their competitors... yet few are able to deliver it effectively 86 % of companies believe software delivery is important or critical But only… 25 % of those who leverage software delivery today 69 % outperform those who don’t leverage software delivery effectively today 5 Source: “The Software Edge: How effective software development drives competitive advantage,” IBM Institute of Business Value, March 2013
  • 6. And a lack of continuous delivery impacts the entire business CHALLENGES CHALLENGES Costly, error prone manual processes and efforts to deliver software across an enterprise Customers Software glitch costs trading firm Knight Capital $440 million in 45 minutes 6 Slow deployment to development and test environments leave teams waiting and unproductive Business Owners Upgrade risk due to managing multiple application configurations and versions across servers Development/ Test New Zealand’s biggest phone company, Telecom paid out $2.7 million to some 47,000 customers who were overcharged after a software glitch Operations/ Production A bad software upgrade at RBS Bank left millions unable to access money for four days
  • 7. 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 Who did this last time? Dev Daily Build Dave… Monthly Delivery Dave’s not here man… Prod Lack of feedback and quality metric leads to missed service level targets
  • 8. Market trends and expected client business outcomes Dependent on rapid Software Innovation and Delivery Rapidly deliver differentiating digital content, applications and services to fulfill citizen needs & obtain new users Systems of Interaction Systems of Engagement SAP Provide differentiating client experience to meet the needs of empowered citizens Leverage cloud to enable flexibility and offer new services HR DB Continuous client experience 8 Systems of Record ERP Cloud-based Services Internet of Things Integrate, evolve and maintain stability of services and comply with any regulations and comliance Partner value chain Enable a software supply chain of Government System Integrators Deliver software based innovation to enable machine to machine interactions
  • 9. Agenda • • • • Why DevOps? What is DevOps? Adopting DevOps o People o Process o Technology IBM DevOps Solution
  • 10. DevOps is a Philosophy Source: http://virtualplatosacademy.blogspot.com/p/great-philosophers.html
  • 11. DevOps definitions DevOps (a portmanteau of development and operations) is a software development method that stresses communication, collaboration and integration between software developers and Information Technology(IT) professionals. DevOps is a response to the interdependence of software development and IT operations. It aims to help an organization rapidly produce software products and services. -- Wikipedia
  • 12. Deming Cycle  William Deming – American statistician  Major influencer of Japanese manufacturing and business alit Qu y  Famous for Plan-Do-Check-Act cycle (Deming Cycle) – I like “Adjust” versus “Act”  PDCA cycles found in DevOps 12 William Edwards Deming
  • 13. DevOps Enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback DevOps Lifecycle Customers Business Owners Development/ Test Operations/ Production Continuous Innovation, Feedback and Improvements Accelerate Software Delivery Balance speed, cost, quality and risk Reduce time to customer feedback 13 13
  • 14. DevOps approach: Apply Lean principles to software innovation and delivery to create a continuous feedback loop with customers 1 1. Get ideas into production fast 2. Get people to use it 3. Get feedback 2 Line-ofbusiness Customer Adopt DevOps approach to continuously manage changes, obtain feedback and , deliver changes to users 3 Eliminate any activity that is not necessary for learning what customers want
  • 15. Starting Point: Release and Deploy Case Study: WebMD Accelerate delivery of usable increments for continuous outside-in feedback Provide a continuous delivery pipeline that automates deployments to test and production environments Reduce overhead with push-button deployments Quantify change stability and measure transparently for compliance “Before it took 2 days to deploy a build, with uDeploy and our new processes, it takes us less than 60 seconds.” Matthew Wilson Director, Consumer Web Operations
  • 16. How We are Improving - An Example from CLM (RQM, RTC, RRC) Measures of Operation Lifecycle Measurements 2008 2010 2012 – 2013 Total Improvement Project Initiation 30 days 10 days 2 days 28 days Groomed Backlog 90 days 45 days On-going 89 days Overall Time To Development 120 days 55 days 3 days 117 days Iteration Length 6 weeks 4 weeks 4 weeks 2 weeks 6 8 3 N/A 36 hours 12 hours 8 hours 400 % N/A 18 hours < 1hour 17 hours Iteration Test Time 5 days 2 days 4 hours 4 days Total Deployment Time 2 days 8 hours 2 hours 2 days Overall Time To Production 9 days 3 days 15 hours 8 days 12 Months 12 Months 3 Months 9 Months Number of Iterations Composite Build Time BVT Availability Time Between Releases
  • 17. Agenda • • • • Why DevOps? What is DevOps? Adopting DevOps o People o Process o Technology IBM DevOps Solution
  • 18. Adopting DevOps in the Enterprise DevOps Lifecycle Customers Business Owners Development/Test Operations/Production Plan and Measure Develop and Test Release and Deploy Monitor and Optimize DevOps Foundation Open Lifecycle and Service Management Integration Platform OSLC 18 Best Practices Ecosystem Continuous Innovation, Feedback and Improvements
  • 19. DevOps Solution: Adoption paths, open platform and key capabilities Business Owner Service Developer Platform Operations Target Customer Plan / Measure Develop / Test Release / Deploy Monitor / Optimize Portfolio Management Code Deployment Monitoring Requirements Test Provisioning Customer Feedback Collaboration Change & Configuration Management Jazz, OSLC and Open Standards Platform Dashboards/ Analytics
  • 20. Agenda • • • • Why DevOps? What is DevOps? Adopting DevOps o People o Process o Technology IBM DevOps Solution
  • 21. Adopting DevOps in the Enterprise: People/Culture • Common Business Objectives • Vision Statement • Common measures of Success Team Lead Team Member Users External System Team Auditors Product Owner Team Member 21 Team Member Domain Experts Senior Executives Operations Staff Gold Owner Support Staff
  • 22. Adopting DevOps in the Enterprise: People/Culture • The case for and against ‘DevOps Team’ • NoOps • The DevOps Liaison Team • No overlay layer of bureaucracy 22
  • 23. Adopting DevOps in the Enterprise: People/Culture • Building a DevOps Culture • There is no Silver Bullet • Right People are needed Team Lead Team Member Users External System Team Auditors Product Owner Team Member 23 Team Member Domain Experts Senior Executives Operations Staff Gold Owner Support Staff
  • 24. Adopting DevOps in the Enterprise: People/Culture • Organizational Change ‘Shift Left’ – Operational Concerns ‘Shift Left’ – Operational Concerns Build ‘Application aware’ Environments Build ‘Application aware’ Environments Environment Sprints Environment Sprints
  • 25. Agenda • • • • Why DevOps? What is DevOps? Adopting DevOps o People o Process o Technology IBM DevOps Solution
  • 26. Adopting DevOps in the Enterprise: Process • DevOps as a Business Process • A Process to get Capabilities from Ideation to Value • Apply Lean Thinking to Processes 26
  • 27. Adopting DevOps in the Enterprise: Process Key Capabilities 1. Collaborative Development & Continuous Integration 2. Continuous Business Planning 3. Continuous Release and Deploy 4. Continuous Testing 5. Continuous Feedback
  • 28. Adopting DevOps in the Enterprise: Process 1. Collaborative Development and Continuous Integration Mobile App Developent Teams Enterprise Services Developent Teams http://bit.ly/PRQ4a7
  • 29. Adopting DevOps in the Enterprise: Process 2. Continuous Business Planning 3. Continuous Release and Deploy 4. Continuous Testing 5. Continuous Feedback http://bit.ly/PRQ4a7
  • 30. Agenda • • • • Why DevOps? What is DevOps? Adopting DevOps o People o Process o Technology IBM DevOps Solution
  • 31. Adopting DevOps in the Enterprise: Technology /* 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 • 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" Rational Automation Rational Automation Framework Framework (WAS, Commerce, MQ…) (WAS, Commerce, MQ…)
  • 32. Adopting DevOps in the Enterprise: Technology • Common Collaboration Tools • Common Work Item Management Tool • Dashboards to show status/progress 32
  • 33. Agenda • • • • Why DevOps? What is DevOps? Adopting DevOps o People o Process o Technology IBM DevOps Solution
  • 34. DevOps Solution: Adoption paths, open platform and key capabilities Business Owner Service Developer Platform Operations Target Customer Plan / Measure Develop / Test Release / Deploy Monitor / Optimize Portfolio Management Code Deployment Monitoring Requirements Test Provisioning Customer Feedback Collaboration Change & Configuration Management Jazz, OSLC and Open Standards Platform Dashboards/ Analytics
  • 35. UrbanCode: premier Release and Deploy Automation Solution Enabling clients to more rapidly deliver mobile, cloud, big data and traditional applications with high quality and low risk IBM UrbanCode Release IBM UrbanCode Deploy • • • • • 35 Simplifies deployment automation for applications Manage configurations across environments Intelligent deployment artifact tracking Higher quality with repeatable, reliable, and governed processes Technology plugins supported out of the box • • • • • Define, manage, and coordinate operational releases Aggregates applications into single release Phases to support quality and geo dispersed deployments Coordinate manual and automated tasks Replaces manual spreadsheets and documents
  • 36. Example DevOps Tool Chain Incrementally adopt when/if needed Rational Focal Point Rational Requirements Composer IBM UrbanCode Release Line of Business SmartCloud Orchestrator IBM Pure Application System IBM UrbanCode Deploy Jenkins IBM UrbanCode Build Rational Application Developer Rational Team Concert Rational Quality Manager Rational Test Workbench Rational Test Virtualization Server SmartCloud Application Performance Management 36
  • 37. Improve Delivery Lifecycle with Software Defined Environments Build Automation Build Automation SCM SCM Pull changes Publish build IBM PureApplication System SmartCloud Orchestrator Execute application deployment and manage settings across environments Environments Provision platform DEV DEV DEV DEV DEV DEV QA QA PROD PROD Patch/update Platform Config Management IBM Endpoint IBM Endpoint Manager Manager Deploy early and Deploy early and often to ensure often to ensure higher quality and higher quality and faster releases faster releases using repeatable, using repeatable, reliable, and reliable, and managed managed automation automation
  • 38. Application-centric middleware configuration management Middleware Administrator -orApplication Developer Deployment Automation Developer 2 - Plugin Artifact Library 3 - Import 4 - Assemble 5 - Publish Exemplar WAS Cell WAS Configuration Template 6 – Define Deployment Process Cluste Cluste rr WAR WAR templa templa DB DB te te Application EAR EAR Application Deployment Automation WAS Configuration Template Creation QA Dev Prod Application Environments
  • 39. IBM UrbanCode Deploy v6.0 Accelerate continuous testing with Service Virtualization 1 IBM UrbanCode Deploy RTW plugin Test Deplo y Dev Dev QA QA RTVS plugin 3 Rational Test Workbench 2 Confi gure Databases Mainframe applications Third-party Services Virtualized services Rational Test Virtualization Server Deploy what is ready, virtualize the rest - Enable continuous integration testing and progressive deployments throughout the software delivery lifecycle for complex applications Automate the creation of virtual test environments as part of the end-to-end DevOps process Establish a virtual system pattern with automated deployment to standardize and share test environments quickly and easily across projects and teams Enable an end-to-end Agile software delivery process Increase the frequency of releases by testing earlier in the development cycle and deploying reliably to pre-production and production environments..
  • 40. IBM UrbanCode Deploy v6.0 DevOps for Mobile IBM UrbanCode Deploy RTW Mobile IBM UrbanCode Release IBM UrbanCode Build Mobile Application Deploy Process Worklight Console Accelerate delivery of mobile apps focusing on quality and user experience – Automate deployment of Worklight mobile applications as part of end-to-end delivery process. Continuous Feedback and Optimization using Tealeaf helps monitor user sentiment and usage, letting teams react to poor feedback before it spirals Application Center adapter .wlapp Binary (IPA/APK)
  • 41. IBM UrbanCode Deploy v6.0 – Plug-ins • • • • 41 51 plug-ins from15 different vendors and open source organizations Broad range of plugins supported: • Application servers • Databases • Messaging platforms • Test automation • Issue tracking systems • Operating system services • Cloud platforms • Issue tracking • Even more… Plug-ins can be downloaded for free from http://plugins.urbancode.com/IBMUrbanCodeDeploy Dedicated team focused on rapid delivery of new and updated plug-ins IBM Confidential: NDA
  • 42. DevOps for Dummies – available now! 42 http://ibm.co/devopsfordummies
  • 43. 43
  • 44. © Copyright IBM Corporation 2013. 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. 44