ClearCase Migration A Proven Path in Three Steps

Transcription

1 ClearCase Migration A Proven Path in Three Steps Rainer Heinold, Sr. Technical Director CollabNet, July 18, 2013 blogs.collab.net twitter.com/collabnet ENTERPRISE CLOUD DEVELOPMENT Copyright 2013 CollabNet, Inc. All Rights Reserved.

2 About CollabNet Founded in 1999 (San Francisco) Subversion founder + sponsor, leader in enterprise Git 10,000+ customers Leader in cloud-based Agile ALM and DevOps Learn more at 2 Copyright 2013 CollabNet, Inc. All Rights Reserved.

3 Today s Presenter Rainer Heinold, Sr. Technical Director, CollabNet Rainer and his team guide customers to design and build end-to-end development solutions to meet their greatest challenges. Before CollabNet, Rainer worked 9 years for IBM Rational and helped leading companies implement new configuration management processes to meet the need of globally distributed software development teams. Rainer is a published author with several articles books on Configuration and Change Management. 3 Copyright 2013 CollabNet, Inc. All Rights Reserved.

4 Migration considerations 4 Copyright 2013 CollabNet, Inc. All Rights Reserved.

5 Migration considerations - People 99.99% of the developers are not religious about the versioncontrol system they use as long as it doesn t slow them down and is easy to use 99.99% of the CM admins *ARE* religious about the versioncontrol system being used They are paying their bills The good news is that there is a life and career path after ClearCase 99.99% of the development managers are concerned about cost 5 Copyright 2013 CollabNet, Inc. All Rights Reserved.

6 Migration considerations - process The process to migrate a version-control infrastructure is specific, but not tool specific The practices discussed hereafter are generic and can be applied to other legacy systems as well Be pragmatic rather than dogmatic In an ideal world you have an infinite amount of time and resources In the real world you have budget, resource and project constraints 6 Copyright 2013 CollabNet, Inc. All Rights Reserved.

7 Migration considerations - Tools Although tools will have an impact on how fast and automated you can migrate, a lack of tools will never be the root cause of a failure Every version-control system comes with a scriptable CLI Version-control systems are different in terms of concepts and architecture there is no simple generic one-touch migration utility out there Focus on the important content (follow the Pareto principle) 7 Copyright 2013 CollabNet, Inc. All Rights Reserved.

8 OpenSource VC and the Enterprise 8 Copyright 2013 CollabNet, Inc. All Rights Reserved.

9 What developers love about Git 65% of Git using organizations like powerful branching & merging (and 57% like this the most) 57% of Git using organizations like network performance (and 22% like this the most) 32% of Git using organizations like Git s popularity (and 10% like this the most) People love Git for its powerful branching and merging capabilities and solid network performance. Source: InformationWeek Survey 2013, State of Git in Enterprise, 9 Copyright 2013 CollabNet, Inc. All Rights Reserved.

10 Enterprises continue to have reservations about Git Anybody (Git using orgs): 37% Tool integration (trackers, CI/CD, ) 36% Co-existence with other SCM tools 33% Security, traceability, process governance 16% 24/7 Support and SLA s Managers and Above (Git using orgs): 51% Security, traceability, process governance 49% Tool integration 37% Co-existence with other SCM tools 22% 24/7 Support and SLA s Source: InformationWeek Survey 2013, State of Git in Enterprise, 10 Copyright 2013 CollabNet, Inc. All Rights Reserved.

11 Manage Git and Subversion with One Enterprise Platform 11 Copyright 2013 CollabNet, Inc. All Rights Reserved.

12 Generic 3-phase approach 12 Copyright 2013 CollabNet, Inc. All Rights Reserved.

13 3 Phase Migration Discover and Plan VOBS + Projects Phased Out Active Code Migration Online After Acceptance Archive Offline Project Project Hand-off and On-boarding 13 Copyright 2013 CollabNet, Inc. All Rights Reserved.

14 Phase 1 General Inventory Create an inventory of your ClearCase repositories Be aware you might not have seen all (regions in the registry, etc.) Identify the following data for each VOB Owner Group permissions list Status of replication Usage (Active, phased out, test/sandbox, administration) Projects using the VOB First in line are the administrative VOBs For plain ClearCase they contain trigger skripts or other utilities used by the ClearCase admin team to setup a new project For UCM environments focus on the PVOBS to get an overview about the dependencies between the components and an overview of the component baselines 14 Copyright 2013 CollabNet, Inc. All Rights Reserved.

15 Phase 1 General Inventory All VOBs identified as test/sandbox can either be archived immediately or should be unregistered. The content of admin VOBs needs to be evaluated and migrated first UCM projects will likely be reflected into a project workspace Baselines will be reflected in the new VC system as tags or labels Baselines (either UCM or Labels) should be reflected in the FRS structure What to do with the ClearCase Views? In a nutshell - nothing Create and share a glossary! 15 Copyright 2013 CollabNet, Inc. All Rights Reserved.

16 Phase 1 Alignment Alignment with the project about the timing There s never a good time for a migration as a project is always close to a release, in the middle of a release or immediately after a release The best time to prepare is typically before a release process is started, the best time for migration is immediately after a successful release Alignment with the project about the content Project managers will ask for a 100% migration of the history The presentation of the archiving concept will help gain acceptance for a skimmed migration Alignment with the project about the training and boarding Ideally as web-based training focussing on the particular needs of a project 16 Copyright 2013 CollabNet, Inc. All Rights Reserved.

17 Phase 2 Active Code Migration A migration is one of the very rare opportunities to clean up the entire dataset Alignment with the project about the training and boarding Ideally as web-based training focusing on the particular needs of a project In most cases we ve seen so far a 100% migration of the entire history is not providing enough business value Tons of unnecessary (not actively maintained) data clutters the new archives The likelihood to change a release older than 10 releases back is less than 5%. Best practice is to the define the right number of releases to be migrated (Active Code) Usually 5 15 baselines Could vary between projects Grace period for read-only mode migrated VOBs 17 Copyright 2013 CollabNet, Inc. All Rights Reserved.

18 Version Tree for Active Code /main 0 Release Release HOT FIX Release 1.0 Release Release Latest 18 Copyright 2013 CollabNet, Inc. All Rights Reserved.

19 Version Tree for Active Code /main 0 Release Release HOT FIX Release 1.0 Release Release Latest 19 Copyright 2013 CollabNet, Inc. All Rights Reserved.

20 Version Tree for Active Code Release 1.1 Release 1.2 Release 1.3 Release HOT FIX Release /Latest 2 /Latest /Latest Copyright 2013 CollabNet, Inc. All Rights Reserved.

21 Phase 3 Archiving and Roll-out Archiving and Roll-out The migration will be done by buckets of VOBs Logical dependencies Set up SVN synch to trickle charge repositories for a few weeks prior to migration (Optional) VOBs will be locked before migration On dates updates applied to SVN repository (Optional) Selected baselines will be imported into new repositories Benchmarking should be done in your environment, as the network and disk speed on the client will have the biggest impacts A real life example at another financial institution showed an import of 1,600 files with 90 MB in less than 9 minutes (with a remote server though public internet lines) 21 Copyright 2013 CollabNet, Inc. All Rights Reserved.

22 Phase 3 The migrated VOBs will be archived Part of the archive is a ClearCase VMware image that can be activated at any given point in time VOBs can be reactivated at any given point Users start working with the new repositories For a defined grace period (1-2 months) the original ClearCase VOBs remain online (taken offline after the grace period) 22 Copyright 2013 CollabNet, Inc. All Rights Reserved.

23 Considerations for ClearCase Users Allow enough time for all users to get trained on Architectural differences (for example change sets vs. single elements) Responsibility for the cloned repository Established naming and branching conventions Git features and clients (based on your way of working) Create and publish your own glossary Highlighting the commonalities and differences between git and ClearCase in the specific setup Encourage frequent push of changes to master repository Check-in in ClearCase makes all changes permanent, in git it is a combination of commit and push Encourage regular hygiene on user machines Enforce protection on master (gateways) 23 Copyright 2013 CollabNet, Inc. All Rights Reserved.

24 Summary Be pragmatic, not dogmatic with your migration approach but keep stakeholders accountable Focus on Active Code and business value Give users enough time to get trained and familiarize themselves with conceptual differences Planning upfront is key to safe unnecessary work every hour spend on planning saves a day of work Create and share your own glossary to foster the transition process and don t give up on the archiving concept 24 Copyright 2013 CollabNet, Inc. All Rights Reserved.

25 Learn More WHITEPAPER: The Case for Open Source over ClearCase MakingtheCaseforOpenSourceoverCCandTCO_WP.html Free 5 page executive whitepaper WEBINAR: ClearCase Migration August 1 st : Git vs. ClearCase - a Developer's View WORKSHOP: Plan your Migration Strategy 25 Copyright 2013 CollabNet, Inc. All Rights Reserved.

26 CollabNet, Inc Marina Blvd., Suite 600 Brisbane, CA blogs.collab.net twitter.com/collabnet CollabNet, Inc., All rights reserved. CollabNet is a trademark or registered trademark of CollabNet Inc., in the US and other countries. All other trademarks, brand names, or product names belong to their respective holders. 26 Copyright 2013 CollabNet, Inc. All Rights Reserved.