Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

DevOps in Cloud OSLC Integration

Presentation given to CSCC on June 27, 2013

  • Be the first to comment

DevOps in Cloud OSLC Integration

  1. 1. © 2013 IBM Corporation1 DevOps in the Cloud: Addressing Integration Challenges Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web Steve Speicher – IBM Rational STSM, OSLC and Linked Lifecycle Data @sspeiche
  2. 2. © 2013 IBM Corporation2 Agenda
  3. 3. © 2013 IBM Corporation 1. Background and “The” Problem
  4. 4. © 2013 IBM Corporation4 Software delivery is critical to success 86% of companies believe software delivery is important or critical 25% leverage software delivery effectively today But only… Source: “The Software Edge: How effective software development drives competitive advantage,” IBM Institute of Business Value, March 2013 69% outperform those who don’t of those who leverage software delivery today
  5. 5. © 2013 IBM Corporation5 Client challenges to accelerate software delivery Development/ Test Operations/ Production Business OwnersCustomers Agile Development Develop Deploy Test Stable Operations Monitor Release Optimize 41% experience development delays 34% experience deployment delays 45% experience production delays 4-6weeks to deliver code changes PlanFast and continuous innovation
  6. 6. © 2013 IBM Corporation6 Accelerate Software Delivery Balance speed, cost, quality and risk Reduce time to customer feedback DevOps 6 Continuous Innovation, Feedback and Improvements DevOps Lifecycle Operations/ Production Development/ TestCustomers Business Owners Definition: Enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback
  7. 7. © 2013 IBM Corporation7 6 Factors of High Performing DevOps teams Track and Plan everything Version everything Automate everything Test everything Audit and Monitor everything Dashboard everything Application Artifacts Application Code Application Code Instrumentation and Configuration Instrumentation and Configuration Runtime Environment Definition Runtime Environment Definition Dev Test Ops Version Automate Test Track and Plan Audit and Monitor Dashboard
  8. 8. © 2009 IBM Corporation 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
  9. 9. © 2009 IBM Corporation IBM DevOps Reference Architecture Monitor and OptimizeRelease and DeployDevelop and Test Mobile Cloud Social Intelligent Devices Developer Communities SecurityBig Data Expert Systems EcoSystem ImplementationServices Industry DevOps Foundation (enabled by the Jazz Platform) Deployment Platforms (PaaS, IaaS, Physical Infrastructure) TOSCA Linked DataOSLC
  10. 10. © 2009 IBM Corporation Line of Business SmartCloud Orchestrator IBM Pure Application System Openstack Jenkins Rational Build Forge uBuild IBM 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 See an integration need?
  11. 11. © 2013 IBM Corporation No consensus driven approach No external review No visibility into solution Built after the fact with limited product APIs Solution focuses on 2 tools in hand License fees Fear of giving up IP Forces alternative solutions Limited Participation Restrictive Participation Need for Open Collaboration on Solutions Past Integration Approaches Have Fallen Short No open process for others to join in Limits solution to particular use cases and technologies Limited to small set of business partners Lack of transparency Restrictive licenses and intellectual property Point-to-point integrations
  12. 12. © 2013 IBM Corporation Universal metadata standard “How did I ever think all those vendors would be able to agree?” Single repository “Can I really expect one vendor to provide all the functionality I need? And what about my existing tools?” Point-to-point integrations “How can I ever upgrade one tool without breaking everything else?” Standard implementations “Did I really believe that every vendor would rewrite their tools on a single framework?” Limited choice and coverage Slow to emerge and disruptive to adopt Need for a Better Solution Past Integration Approaches Have Fallen Short
  13. 13. © 2013 IBM Corporation 2. A Simple Solution
  14. 14. © 2013 IBM Corporation14 The Executive Summary: OSLC’s Simple Solution Automation Monitoring Increased traceability Architecture of the Web Linked Data Increased reuse Standard Interfaces Better visibility “Just Enough” integration Decreased maintenance costs Users can work seamlessly across their tools (complex and fragile synchronization schemes not required) OSLC is an open and scalable approach to lifecycle integration. It simplifies key integration scenarios across heterogeneous tools
  15. 15. © 2013 IBM Corporation15 OSLC Automation  2.0 provides support for common and simple REST- based automation pattern  Motivated by scenarios from DevOps, Continuous Integration, Deployment, Test Execution  Implementations rolling in – Jazz for Service Management – Rational Quality Manager – Tivoli Workload Scheduler – ….*
  16. 16. © 2013 IBM Corporation16 OperationsDevelopment Incidents (e.g. IBM Smart Cloud Control Desk) Management and Monitoring Data Center S e r v e r S e r v e r S e r v e r S e r v e r S e r v e r S e r v e r OSLC Interactions Defects (e. g. IBM Rational Team Concert) • Align IT operations and development teams. • Allow teams to work seamlessly with the tools the are familiar with. • Remove the need to synchronize data across tools. • Based on OSLC Change Management 2.0 Tracing Problems from Ops into Dev
  17. 17. © 2013 IBM Corporation17 Cloud Application Lifecycle w/ OSLC and TOSCA Leverages TOSCA, OSLC Asset Management and use OSLC interaction See demo and more at
  18. 18. © 2013 IBM Corporation 3. OSLC Community and Vision
  19. 19. © 2013 IBM Corporation19 OSLC: Standardizing the sharing of lifecycle data Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web Linked Data Platform Working Group Inspired by the web Proven Free to use and share Open Changing the industry InnovativeOSLC: Generally applicable: specs available for many domains covering ALM, DevOps, ISM, and PLM Leading choice for strategic integration technology Scenario-driven & Solution-oriented OSLC Member Section The Resource for OSLC Implementers Based on and Shaping the Future of Internet Architecture Open and Independent Governance and Leadership
  20. 20. © 2013 IBM Corporation20 HistoryCommunitygovernanceofOSLC IBM de facto governance (with community support) Steering committee Multi-organization steering committee established New governance model introduced OASIS Internationally recognized independent SDO Formal support from 22 organizations (at launch) Participation governed by established OASIS model June 2012 May 2013 2012
  21. 21. © 2013 IBM Corporation21 OASIS OSLC Co-Founders
  22. 22. © 2013 IBM Corporation22 Why OSLC Standardization Matters
  23. 23. © 2013 IBM Corporation23 Aspirations for OSLC *Defined by OSLC Steering Committee
  24. 24. © 2013 IBM Corporation24 Approved Standard Approved Standard The Organizational Vision for OSLC OSLC Member Section at OASIS Steering Committee Technical Committees Forums ~~~ ~~..~~ Implementer’s Expo News Resources and Tutorials Eclipse Lyo OSLC4NetLibraries Test Suites Samples and Examples Reference Implementations W3C LDP WG Use what you need, share what you can. User Groups Subcommittees
  25. 25. © 2013 IBM Corporation 4. Not Done Yet
  26. 26. © 2013 IBM Corporation26 How to Participate in OSLC Today Get active at Complete a Members Agreement and get listed on the Organizations page Join a User Group to help define scenarios Join a Work Group to help define the version 3 specifications Start discussing your ideas and voicing your opinions As a CSCC Working Group for DevOps? On the OSLC Member Section mailing list On the OSLC Forums Get involved in the Steering Committee election Stand for election Make sure your organization votes Be a co-founder of the Core TC
  27. 27. © 2013 IBM Corporation 5. Questions and Discussion For more about OSLC visit
  28. 28. © 2013 IBM Corporation backup
  29. 29. © 2013 IBM Corporation29 The Basics: What is OSLC, and why should I care? OSLC is an open community building practical specifications for integrating software OSLC is beneficial to many stakeholders Contributing Organizations:
  30. 30. © 2013 IBM Corporation30 OSLC inside OASIS OSLC Member Section 5+ OASIS Members are the founders Other OASIS Members can join when they choose OASIS Steering Committee1 Technical Architecture TC2 Technical Architecture TC2 1. The current OSLC Steering Committee becomes the OASIS OSLC Member Section Steering Committee 2. The Core workgroup becomes the Technical Architecture TC (Technical Committee). 3. Domain TCs are created by composing several OSLC domain workgroups. 4. Subcommittees may be created by the Steering Committee for a number of purposes. E.g. scenario development and prioritization or exploration of new domains ahead of creating a new TC. Domain TCDomain TC Domain TCDomain TC Domain TC3Domain TC3 Subcommittee Subcommittee Subcommittee4 advises guides <relationship> overseesoversees
  31. 31. © 2013 IBM Corporation31 Linked Data – Defined by Tim Berners-Lee 1. Use URIs as names for things 2. Use HTTP URIs so that people can look up those names. 3. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL) 4. Include links to other URIs. so that they can discover more things. He concludes this with: “Simple.” Reference: “Linked Data”, Tim Berners-Lee, 2006-07-27
  32. 32. © 2013 IBM Corporation32 Linked Data – What is it? TestCase 14 is blocked by Issue 973 http://srv/qm/tc/14 qm:blockedBy Joe is a committer for Apache doap:committer 32
  33. 33. © 2013 IBM Corporation33 Linked Data – What is it? TestCase 14 is blocked by Issue 973 http://srv/qm/tc/14 qm:blockedBy Issue 973 depends on Bug 318 cm:dependsOn Joe is a committer for Apache doap:committer Issue 973 is owned by Joe dc:contributor
  34. 34. © 2013 IBM Corporation34 Linked Data – Bridging separate data sources (but with meaning) ource: Sept 2011 34
  35. 35. © 2013 IBM Corporation35 Lifecycle ToolLifecycle Tool ChangeChange ManagementManagement Lifecycle ToolLifecycle Tool Quality ManagementQuality Management Lifecycle ToolLifecycle Tool RequirementsRequirements ManagementManagement Service ManagementService Management Help DeskHelp Desk Service ManagementService Management DeploymentDeployment <http://cm/bugs/2314> a oslc_cm:ChangeRequest ; dcterms:relation <http://cm/bugs/1235>; oslc_cm:implementsRequirement <http://rm/req/56> . <http://rm/req/56> a oslc_rm:Requirement ; dcterms:title “Online shopping cart”; oslc_rm:validatedBy <http://qm/tc/17> . Common Resource Definitions Link Preview Delegated Dialogs OSLC – Based on Linked Data