breakthroughs in scalability
play

Breakthroughs in Scalability at Intel Haim Mousan Senior DevOps - PowerPoint PPT Presentation

From ClearCase to Perforce Helix: Breakthroughs in Scalability at Intel Haim Mousan Senior DevOps Engineer Introduction Haim Mousan SCM & ALM/BI Tech Lead Intel Firmware Department (~600 people, 3 Geos) Responsible for delivery


  1. From ClearCase to Perforce Helix: Breakthroughs in Scalability at Intel Haim Mousan Senior DevOps Engineer

  2. Introduction  Haim Mousan  SCM & ALM/BI Tech Lead  Intel Firmware Department (~600 people, 3 Geos) Responsible for delivery most critical Intel Firmware IPs Those 2 IPs integrated in all Intel Platforms The views expressed in this presentation are my own. I do not speak for Intel and do not represent Intel at any matter. I’m here to share my own private experience with SCM, Perforce usage and integration within our team in Jerusalem.

  3. Introduction Desktop Mobile Set-Top Box Security Sensors IOTG Servers Google Glass

  4. Problem Statement – 3 years ago… Unstable coding environment with IBM ClearCase  Unbearable Performance and Usability Issues  Many dozens of methodologies  Development productivity loss  Zero integration with other ALM tools  “Where is my data?” user complaints  3 people supporting ClearCase  Massive increase in Intel’s Projects expected (X6)  SCM system is mission critical - cannot afford downtime

  5. Solution – Today

  6. Solution – Today Perforce orce  CI CI CI • Continuous Integration Gated check-in • Build • Full release proc. automation Security Scans Legal Scans

  7. Solution – Today Perforce orce  CI CI CI ALM • Continuous Integration Gated check-in • Build • Full release proc. automation Arch Perforce orce  ALM Code link with TFS workitems • • Full data traceability Security Scans Legal Scans

  8. Solution – Today- Perforce Perforce orce  CI CI CI ALM • Continuous Integration Gated check-in • Build • Full release proc. automation Arch Perforce orce  ALM Code link with TFS workitems • • Full data traceability Security Scans BI Legal Scans Perforce orce  BI BI • Decision support system Code changes tracking •

  9. Solution – Today! Sensors Security Security Skylake Kabylake Sofia GoldSand Haswell Broadwell Cannonlake Broxton NextGen.1 NextGen.2 Desktop 2013 2013 2016 2016 BU3 BU1 BU2 Server Mobile BU4 BU4 BU6 Scop Sc ope vs. HC HC Sc Scop ope vs. HC HC 3.0 2.8 4.00 2.00 1 1 3.47 6.50 1.50 3.17 2014 2015 2014 A 2015

  10. Solution – Today!  Entire organization SCM is scaled up  Unified methodologies ~25  3 core methodologies  Supported by 0.2 people (was 3)  99.9% Stability  Major Performance Increase

  11. Solution - Details Phase I:  Migration IBM ClearCase to Perforce Phase II:  Perforce  Continuous Integration (Jenkins/QB)  Perforce  ALM (Microsoft TFS)  Perforce  OLAP Based BI (SharePoint BI)

  12. Solution - Details Phase I:  Migration IBM ClearCase to Perforce Phase II:  Perforce  Continuous Integration (Jenkins/QB)  Perforce  ALM (Microsoft TFS)  Perforce  OLAP Based BI (SharePoint BI)

  13. Solution – CC  P4 Migration  12 Teams migrated (500 people)  8 weeks – from definitions stage to deployment • Perforce depots setup • Migration scope – repositories, historical labels • Methodology consolidation • Migration script & preparations • Pilot • Training • Deployment

  14. Solution – CC  P4 Migration  12 Teams migrated (500 people)  8 weeks – from definitions stage to deployment • Perforce depots setup • Migration scope – repositories, historical labels • Methodology consolidation • Migration script & preparations • Pilot • Training • Deployment

  15. Solution – CC  P4 Migration  12 Teams migrated (500 people)  8 weeks – from definitions stage to deployment • Perforce depots setup • Migration scope – repositories, historical labels • Methodology consolidation • Migration script & preparations • Pilot • Training • Deployment

  16. Solution – CC  P4 Migration  Migration scope – repositories, historical labels  Label 1.0.0.1  Changelist X  Label 1.0.0.10  Changelist Y  Label 1.0.0.15  Changelist Z  Latest Code  #Head Revision

  17. Solution – CC  P4 Migration  12 Teams migrated (500 people)  8 weeks – from definitions stage to deployment • Perforce depots setup • Migration scope – repositories, historical labels • Methodology consolidation • Migration script & preparations • Pilot • Training • Deployment

  18. Solution – CC  P4 Migration  12 Teams migrated (500 people)  8 weeks – from definitions stage to deployment • Perforce depots setup • Migration scope – repositories, historical labels • Methodology consolidation • Migration script & preparations • Pilot • Training • Deployment

  19. Solution – CC  P4 Migration  12 Teams migrated (500 people)  8 weeks – from definitions stage to deployment • Perforce depots setup • Migration scope – repositories, historical labels • Methodology consolidation • Migration script & preparations • Pilot • Training • Deployment

  20. Solution – CC  P4 Migration  12 Teams migrated (500 people)  8 weeks – from definitions stage to deployment • Perforce depots setup • Migration scope – repositories, historical labels • Methodology consolidation • Migration script & preparations • Pilot • Training • Deployment

  21. Solution – CC  P4 Migration  12 Teams migrated (500 people)  8 weeks – from definitions stage to deployment • Perforce depots setup • Migration scope – repositories, historical labels • Methodology consolidation • Migration script & preparations • Pilot • Training • Deployment

  22. Solution – CC  P4 Migration  12 Teams migrated (500 people)  8 weeks – from definitions stage to deployment • Perforce depots setup • Migration scope – repositories, historical labels • Methodology consolidation • Migration script & preparations • Pilot • Training • Deployment

  23. Solution – CC  P4 Migration  Highlights • Performance cross geos • Training • Migration script development • Methodology enforcement  Lowlights • Methodologies consolidation • Symbolic links • Server charset mismatch

  24. Solution - Details Phase I:  Migration IBM ClearCase to Perforce Phase II:  Perforce  Continuous Integration (Jenkins/QB)  Perforce  ALM (Microsoft TFS)  Perforce  OLAP Based BI (SharePoint BI)

  25. Solution - Details Phase I:  Migration IBM ClearCase to Perforce Phase II:  Perforce  Continuous Integration (Jenkins/QB)  Perforce  ALM (Microsoft TFS)  Perforce  OLAP Based BI (SharePoint BI)

  26. Solution – Perforce  CI CI Orchestrators Deployment Build/Scan Test Failed Passed

  27. Solution – Perforce  TFS Build/CI Bug Development Portal Req Code Submission Story

  28. Solution – Perforce  TFS DEMO

  29. 29

  30. 30

  31. 31

  32. 32

  33. 33

  34. 36

  35. 37

  36. Solution – Perforce  TFS Full Data Traceability Bug Development Portal Validation Portal Req Code Test Submission Coverage Story

  37. Solution – Perforce  BI

  38. 40

  39. 41

  40. 42

  41. 43

  42. 44

  43. 45

  44. 46

  45. Key Messages  Scalable and usable solution for firmware/software is a major challenge  BI and full data traceability are breakthrough capabilities for any SW team  Robust Source Control Management tool integrated with ALM is no longer a theoretical concept  Can be easily adopted by any SW team within several weeks

  46. Thank You! Haim Mousan haimmousan@yahoo.com https://www.linkedin.com/in/haim- mousan-260b3812

Recommend


More recommend