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.

Adopting the IBM Continuous Engineering (CE) solution Configuration Management Capability

538 views

Published on

In version 6, the IBM CE solution added exciting new configuration management capabilities across the lifecycle, better enabling parallel development and strategic reuse. Simply enabling these capabilities won't help you realize their potential; you must consider changes to your process and usage model to achieve results. This presentation describes current considerations, limitations and strategies for adopting configuration management so you can plan a smooth adoption and successfully realize the benefits in your organization.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Adopting the IBM Continuous Engineering (CE) solution Configuration Management Capability

  1. 1. © 2015, 2016 IBM Corporation Adopting the IBM CE solution Configuration Management Capability October 2016 Tim Feeney (tfeeney@us.ibm.com) Unleash the Labs – IBM trfeeney.wordpress.com Kathryn Fryer (fryerk@ca.ibm.com) Unleash the Labs – IBM
  2. 2. © 2015, 2016 IBM Corporation2 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability DISCLAIMER IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. © Copyright IBM Corporation 2016. All rights reserved.
  3. 3. © 2015, 2016 IBM Corporation3 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Topics • Configuration management overview • Trade-offs and considerations – as of current release (6.0.2) • Primary factors • Reporting • OSLC integrations • Linking • QM utilities • Additional considerations • Enabling configuration management • Upgrade and migration • Adoption path and additional resources
  4. 4. © 2015, 2016 IBM Corporation4 21 October 2016 Linked Lifecycle Data
  5. 5. © 2015, 2016 IBM Corporation5 21 October 2016 Zooming In
  6. 6. © 2015, 2016 IBM Corporation6 21 October 2016 What if you have multiple versions of your artifacts? Which version to use? Which version to link to?
  7. 7. © 2015, 2016 IBM Corporation7 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Configurations define the correct artifact versions Tests QM Release A Each tool defines streams (changeable) and baselines (frozen) to select the correct artifact versions Requirements Tests RM Release A QM Release A How do we know which RM stream belongs with which QM stream?
  8. 8. © 2015, 2016 IBM Corporation8 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Global configurations provide context Requirements Tests Global configuration- Release A RM Release A QM Release A The global configuration defines which streams and/or baselines from the various applications belong together for a particular variant or version
  9. 9. © 2015, 2016 IBM Corporation9 21 October 2016 Global configurations reference local configurations AMR Mobile US 1.0 GA AMR (QM) Mobile US AMR (RM) 1.0 US.GA AMR (DM Mobile US AMR (SCM) Mobile US Global Configuration Management Requirements Management Quality Management Design Management Source control AMR Mobile component AMR Mobile US
  10. 10. © 2015, 2016 IBM Corporation10 21 October 2016 Global Configurations provide context
  11. 11. © 2015, 2016 IBM Corporation11 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Global Configurations – building reusable components • A GC component can contribute to a higher-level GC component • By developing a hierarchy, the GC structure can reflect build-up of a product or system • A GC component can contribute to more than one higher-level component • Build variant products/systems • Families of similar-but-different products/systems Model v1.1 Engine v1.1 Pump 2.1 Spark v3.1 Gear v2.1 Global configurations
  12. 12. © 2015, 2016 IBM Corporation12 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability GC Component/Stream/Contributions A contribution from QM Contribution from another GC component stream
  13. 13. 13 Sports model convertible Sports model coupe Sports Model Car X Model Time GL Model Putting it all together: Speeding up delivery of highly customized Innovation  Work in a development stream that spans tools  Baseline across tools  Branch to create new variants or releases  Compare across configs  Control delivery of changes across configs  Reuse without copying, making updates and impact analysis much easier Function Stream Baseline = Baseline = Branch = Artifact propagation Requirements Architecture Test Implementation Car X Model Power Train X GearBox X Engine X Body X Requirements Architecture Test Implementation Requirements Architecture Test Implementation
  14. 14. © 2015, 2016 IBM Corporation14 21 October 2016 Why adopt configuration management?  Extend the value of versioning and configurations across lifecycle and disciplines  Increase reuse, speed of delivery, and reliability in recreating releases  Improve quality and reduce cost
  15. 15. © 2015, 2016 IBM Corporation15 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Trade-offs to consider (for projects adopting configuration management) • Configuration management capabilities come with some trade- offs: • Behavior changes from “non-enabled” projects • Limitations in the initial releases (fewer with each new release) • Some inconsistencies across the products • One must be aware of all factors and carefully consider whether to enable configuration management for a project area • Most critical considerations are described on self-serve page on jazz.net when obtaining an activation key • Guided discussions with Support or other client-facing SMEs are encouraged, especially before production decision • Strongly encourage pilot before any production decision • Because once you enable configuration management for a project area, you cannot disable it!
  16. 16. © 2015, 2016 IBM Corporation16 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Primary factors • Must upgrade everything to consistent v6 level • In general, need consistent level to take advantage of new/growing cross-application capabilities • v5 applications don’t understand versioning and configurations • Working with mixed versions is not practical beyond a short transition • Additional infrastructure required • GCM and LDX applications – include on (expanded) JTS or separate server • LQE server – 8-32 cores, 16-256G RAM • Potential impacts to other servers depending on repository size and shape, number of users, usage patterns… • If RM or QM project areas are linked, enable all or none of them • Enabling only some linked projects is not practical beyond a short transition – Links between them are frozen – Cannot create new links – Links from the non-enabled project may not resolve correctly
  17. 17. © 2015, 2016 IBM Corporation17 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Reporting considerations • Configuration-enabled projects use the LQE data source for reporting • Once enabled, projects do not send data to the data warehouse (DW) but use LQE instead; existing DW data is archived – Exception: RTC, which does not “enable” projects, continues to populate the DW • Existing DW-based reports (BIRT, RRDI, dashboard widgets) must be recreated or replaced – Exception: RTC reports that do not include data from versioned artifacts • Rational Publishing Engine report templates can be reused; specify the target configuration
  18. 18. © 2015, 2016 IBM Corporation18 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Reporting considerations • Some data is not yet available for configuration-aware reporting: • Time-based trending data • DNG view query results • QM lab management resources (e.g. jobs, requests, reservations) • RTC build information • Note: some data is not available in either LQE or DW: – DNG reviews, module hierarchy, change set information – RTC SCM information, plan resources, WI comments • Some data available only by writing custom SPARQL queries: • DM resources • Local configurations • Link validity data • QM lab resources (machines) • Project-area level access control not implemented for Link Validity (can be set manually in LQE) • Sample reports based on JKE sample available on Jazz.net for evaluation; no OOTB reports yet
  19. 19. © 2015, 2016 IBM Corporation19 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability OSLC Integrations • Most OSLC-based integrations outside the CLM applications do not yet support versioned artifacts • Requires support for OASIS OSLC Configuration Management spec (draft); expect list of supporting applications to grow over time • Integrations to RTC work items continue to work as expected, because work items aren’t versioned • Several RQM test execution adapters have been verified to work correctly with enabled projects • IBM ClearQuest V8.0.1.10 introduced initial support for global configurations; see the CQ documentation for details • Progress made with other IBM and third-party applications; expect more announcements in coming months
  20. 20. © 2015, 2016 IBM Corporation20 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Changes related to linking • New Link Validity service replaces “suspect links” in enabled projects • Automatic “suspect” assertion on change • User assertion (valid/invalid/suspect) • No support yet for “profiles” (can’t specify which properties affect validity) • In QM views, you cannot filter on RTC work item and plan traceability links
  21. 21. © 2015, 2016 IBM Corporation21 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Additional considerations • QM Mobile application for offline execution not yet available • New roles and permissions to manage configurations • Behavior changes include: • Working in global configuration context • DNG change sets and reviews • RTC configuration to determine configuration context • See appendix for additional behavior changes and minor limitations • A complete list of limitations and workarounds by release is available on jazz.net • View the 6.0.2 queries for workarounds and limitations • View the pending workaround articles for 6.0.2 from each product’s release notes
  22. 22. © 2015, 2016 IBM Corporation22 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Enabling Configuration Management • Rhapsody DM and RTC already support Configuration Management – no further action needed • Two-step process to fully enable configuration management for DNG and RQM: 1. Enter activation key in application settings – Advanced Properties > Local Versioning Component – Obtain key from self-serve page on jazz.net (for pilot) or contact IBM Support (especially for production) 2. Enable in project area property for a specific RM or QM project area – Configuration Management section > click to enable • Once you enable Configuration Management for a Project Area, you cannot disable it!
  23. 23. © 2015, 2016 IBM Corporation23 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability When you click “enable” for DNG/RQM projects… • Reporting switches to a new configuration-aware solution using LQE • Project area stops feeding the DW and existing DW data is archived • BIRT and RRDI reports no longer work and are removed; Dashboard widgets that use report resources stop working • Backlinks are removed; directional links created in and referenced from Link Index Service • May take some time to fully index, especially for large projects • Existing links from external sources resolve to default configuration • QM snapshots become “reference only”; use baselines instead
  24. 24. © 2015, 2016 IBM Corporation24 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Upgrade and Migration • New components in v6.x to enable configuration management: • GCM application, LQE data source, Link Index service (LDX) • Refer to new topology diagrams on deployment wiki • Be sure to consider related changes to production infrastructure requirements • All v6.x upgrades require migrating to new RQM and DNG repository schemas, regardless of configuration management use • Offline migration • Might take some time depending on repository size/shape and network latency to the database server • No additional online steps needed • Upgrades between 6.x releases require re-indexing LQE data, which might take time • Reporting is unreliable during re-index • Performance of non-configuration management enabled projects expected to be consistent with previous versions • Additional repository updates happen when you enable Configuration Management for a project area (as previously described)
  25. 25. © 2015, 2016 IBM Corporation25 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Adoption path Explore and define how YOUR organization should implement • Process definition is critical • Define usage model including roles, stream strategies, change management and cross-stream delivery… • Assess reporting needs and implementation options Conduct one or more pilot projects • Validate and modify usage scenarios and processes • Consider both new and existing projects Roll out selectively and progressively • Carefully select initial projects to enable • Manage environment changes • Train users on processes, conventions, tool changes
  26. 26. © 2015, 2016 IBM Corporation26 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Global Configuration Management Adoption Service Offering Achieve Strategic Reuse using Global Configurations Benefits Features  Complete a smooth transition to Global Configuration Management  Speed up adoption and avoid common missteps by working with our knowledgeable experts  Benefit from the knowledge, standard practices, and proven repeatable processes brought by our experts  Build skills quickly and effectively with expert advice and information sharing directly from our experienced consultants  Preparing for enabling Global Configuration Management  Prepare the environment and users for the activities to enable the new capability  Supporting the activities to enable the new capability  Support upgrades and installations  Verify successful operation  Supporting users transitioning to Global Configuration Management  Perform mentoring on usage, updates and planning for enabling additional projects Backed by world class Analytics Services Experts.
  27. 27. © 2015, 2016 IBM Corporation27 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability For more information • Configuration management playlists on youtube: • Based on these lab exercises • Introductory series • Jazz.net article 1492 links to many valuable resources including videos and blogs • Try it out: https://jazz.net/products/sandbox/
  28. 28. © 2015, 2016 IBM Corporation28 21 October 2016 ICE -IBM Continuous Engineering Event Website: http://learnquestconference.com/iceiot16/
  29. 29. © 2015, 2016 IBM Corporation29 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability © Copyright IBM Corporation 2015. 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, 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.
  30. 30. © 2015, 2016 IBM Corporation30 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Appendix A: Additional considerations and behavior changes for Configuration Management
  31. 31. © 2015, 2016 IBM Corporation31 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Reporting considerations • When reporting across versioned artifacts and RTC work items, carefully consider filtering • Filtering by configuration will yield correct results for versioned artifacts • Filter work items based on Planned-For or Found-In fields, as they have no direct association to a configuration • When reporting on DNG artifacts: • As of 6.0.2, reverse traceability is now supported for custom link types as well as for OSLC RM-defined links • If you customize data types (new types or attributes), you need to add them to the initial RM stream for them to be visible for reporting – Alternatively, use custom SPARQL queries for customized types that are not in the initial stream • LQE indexes all projects; no UI to select or exclude projects (to reduce volume) • Current scale is 2 million versioned resources per LQE instance with 15,725 configurations • Where concerns arise, IBM can assist with configuring LQE to index only selected project areas • Upgrade notes: • When upgrading from v6.0 (where configuration-aware reporting was Tech Preview only): – Uninstall the v6.0 LQE component and reinstall with v6.0.2 upgrade – Configure RB data sources to add LQE (https://server:port/rs/setup) • When upgrading from v6.0.1 – Rebase the DNG TRS feeds (instructions in the Interactive Upgrade Guide) – Re-index the TRS feeds from DNG, RTC, and ?? data sources (https://server:port/lqe/web/admin/data-sources)
  32. 32. © 2015, 2016 IBM Corporation32 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability RTC considerations • Work items are not versioned; tracking and planning artifacts are not part of GC contributions • RTC work items are targeted to a single Release, and therefore a single GC • Each supported OSLC link type is associated with a single attribute specifying the Release target (Planned For, Found In, or some custom attribute) • When you set or change the Release target (and GC) for a WI, you must save the work item to make the context change take effect • If you change the Release > GC association in the RTC project area, the versioned links will not work correctly. • If there is no GC associated with a Release, links resolve to the default configuration • Child iterations can inherit Release setting from the parent, or have their own (e.g. Sprints under a main iteration can contribute to the same Release and GC) • If you are working in a Personal Stream, RTC cannot resolve the configuration context and therefore cannot filter artifacts by configuration when you create links
  33. 33. © 2015, 2016 IBM Corporation33 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Managing and delivering change • DNG and DM have change sets; RQM doesn’t • If necessary, create separate RQM stream to model changes before delivering to main stream (note that this requires additional stream management, and manual work with a Personal Stream) • Can create link from DNG or DM change set to change request (e.g. RTC work item) • DNG now allows you to enforce: • Requiring change set for any changes • Requiring change set be linked to an approved change request in an OSLC change management provider (like RTC) • Delivering changes varies: • Within DNG: – If you deliver changes from the Manage Configurations view, you can only deliver between parent/child in the stream hierarchy – If you deliver from an artifact view, you can choose any stream as the target (Deliver changes) or source (Accept changes), and start from either direction – You can select one or more change sets; conflicts are highlighted and can be merged – As of 6.0.2, you can choose to automatically deliver changes, providing inputs on how to resolve conflicts (as well as returning to manual mode in case of conflict) • RQM merges changes from a source baseline to the current stream selected by the GC; merge can be selective – Start operation from the target, not the source of the changes – In effect, you accept changes from a source baseline into the current configuration
  34. 34. © 2015, 2016 IBM Corporation34 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability More tips for change sets • In DNG, you cannot create a review against a change set • Your DNG change set is automatically added to your Personal Stream (PS) at creation and removed at delivery/discard: • Only one change set per DNG configuration in the PS at one time; creating a second change set for the same configuration replaces the first in the PS, and requires manual changes to switch between them • You can manually add someone else’s change set to your PS (previous point still applies) • Personal Streams persist and are reused for future change sets – In 6.0.2, when you deliver your change set, the configuration context remains set to your Personal Stream • RTC does not recognize the context of a Personal Stream; when you create links from an artifact in a PS to an RTC artifact, filtering based on configuration context will not work • DNG change set content is not visible after you deliver • Before delivering, you can compare the change set to the existing baseline or stream to identify the changes it contains. • If you link the change set to a WI, you can manually describe the changes in the WI • Use naming conventions to indicate content or reason for change • Use naming conventions so you can recognize change sets at delivery time • If you need to deliver across streams, use explicit change sets • Implicit change sets are hard to identify and differentiate
  35. 35. © 2015, 2016 IBM Corporation35 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Consider security and permissions • To reference a GC, you must be a member of the GC project area (in GCM application) • Even to set the GC context in your RM/QM/DM application • Can use lifecycle projects to ease user administration • Members who need to create Personal Streams must have permission to do so • GC Configuration Leads must be members of RM/QM/CCM/DM project areas in order to access streams and baselines • Must have project permissions to create streams/baselines • Assign roles and permissions for creating streams and baselines in local applications as well as GCM • For DNG, this includes permissions related to change sets owned by yourself and by others
  36. 36. © 2015, 2016 IBM Corporation36 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability GCM considerations • GCM application has no project associations • You can define it as part of Lifecycle Project, but it just makes adding all the users easier, no other effect • A GC may include more than one contribution from a component or project area (“component skew”) • Resolves to first configuration found in list of contributions or hierarchy • Use component skew reports to identify skew and ensure configurations are ordered as intended – especially for large or complex hierarchies
  37. 37. © 2015, 2016 IBM Corporation37 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Deployment considerations • Single GCM application per JTS • A project area can’t contribute to multiple GCM applications • A project area can contribute to more than one GC component or project within a single GCM application • GC components are at granularity of project area – define project areas accordingly • The project area is used in the configuration as a single unit – the entire project area is included in a stream or baseline, and as a contribution to a GC. You can’t subdivide a project area and contribute only part of it. • For more information, including recommended deployment topologies, see the Deployment Wiki
  38. 38. © 2015, 2016 IBM Corporation38 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Appendix C: Architectural changes from 5.x to 6.x (reference)
  39. 39. © 2015, 2016 IBM Corporation39 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability Rational Team Concert CLM Architecture 5.x Rational Quality Manager DOORs Next Generation( RRC) Rational Design Manager CLM Web Client RTC VS/ Eclipse Client Rhapsody DM Client Relational DB Server JAF DB RTC DB RQM DB DNG DB RDM DB Application Server Jazz Foundation . OSLC Integration Reporting • User / Project Admin • Authorization • Repository Services • Process
  40. 40. © 2015, 2016 IBM Corporation40 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability CLM Architecture 6.x (w/ PLE) Rational Team Concert Rational Quality Manager DOORs Next Generation( RRC) Rational Design Manager CLM Web Client RTC VS/ Eclipse Client Rhapsody DM Client Relational DB Server JAF DB RTC DB RQM DB DNG DB RDM DB Application Server Jazz Foundation Config Aware OSLC Integration w/o backlinks Reporting • User / Project Admin • Authorization • Repository Services • Process Lifecycle Query Engine Global Config Service Backlink Index Service Additions or restructured to support multiple configurations Fundamenta l rework of the query and repository services Reorganizatio n of the RQM and DNG data into schema that supports configurations Restructuring of the OSLC cross product linkages to support configuration. Requires removal of “backlinks” Rework of the web UIs to allow selection of configuration and maintain config as user navigates app to app Add configuration management to RQM and DNG. Includes reworking storage layers, adding compare and merge UIs Modify tracking/plannin g to work with versioned CLM resources
  41. 41. © 2015, 2016 IBM Corporation41 21 October 2016 Adopting the IBM CE Solution Configuration Management Capability OSLC Links and Configuration Management • In 5.x and earlier, creating a link from artifact A to artifact B typically resulted in the creation of a link in the reverse direction – a ‘backlink’ • In 6.0 configuration management enabled projects, to link between versioned resources, the configuration is used to determine the right version of the target artifact • A single link is stored in the artifact of the application owning the link (not necessarily the one that created it). A backlink is no longer created and stored. – RTC owns all links involving RTC – RQM owns all links between QM and RM/DM – DM owns links between DM and RM • A new Link Index Service is used to determine if incoming links to an artifact version exist and thus visible/navigable from that artifact • In 6.0 projects that configuration management is NOT enabled, the linking storage/behavior is the same as that used in 5.x, i.e. backlinks are created.

×