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

breakthroughs in scalability
SMART_READER_LITE
LIVE PREVIEW

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


slide-1
SLIDE 1

From ClearCase to Perforce Helix:

Breakthroughs in Scalability at Intel

Haim Mousan

Senior DevOps Engineer

slide-2
SLIDE 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.

slide-3
SLIDE 3

Introduction

Desktop Mobile Set-Top Box IOTG Servers Google Glass

Sensors Security

slide-4
SLIDE 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

slide-5
SLIDE 5

Solution – Today

slide-6
SLIDE 6

Solution – Today

CI Build

Security Scans

Legal Scans

Perforce

  • rce  CI

CI

  • Continuous Integration
  • Gated check-in
  • Full release proc. automation
slide-7
SLIDE 7

Solution – Today

ALM CI Build

Security Scans

Legal Scans Arch

Perforce

  • rce  CI

CI

  • Continuous Integration
  • Gated check-in
  • Full release proc. automation

Perforce

  • rce  ALM
  • Code link with TFS workitems
  • Full data traceability
slide-8
SLIDE 8

Solution – Today- Perforce

ALM BI CI Build

Security Scans

Legal Scans Arch

Perforce

  • rce  CI

CI

  • Continuous Integration
  • Gated check-in
  • Full release proc. automation

Perforce

  • rce  ALM
  • Code link with TFS workitems
  • Full data traceability

Perforce

  • rce  BI

BI

  • Decision support system
  • Code changes tracking
slide-9
SLIDE 9

Solution – Today!

2013 2013

Security

Sensors Security

Kabylake Broxton NextGen.1 GoldSand NextGen.2 Sofia Skylake Cannonlake Broadwell Haswell

BU2

BU4

BU6 BU3 BU1 BU4

2016 2016

Desktop Mobile Server 3.47 3.17 1.50 6.50 2014 A 2015

Sc Scop

  • pe vs. HC

HC

3.0 1 2.8 1 2.00 4.00 2014 2015

Sc Scop

  • pe vs. HC

HC

slide-10
SLIDE 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
slide-11
SLIDE 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)

slide-12
SLIDE 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)

slide-13
SLIDE 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
slide-14
SLIDE 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
slide-15
SLIDE 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
slide-16
SLIDE 16

Solution – CCP4 Migration

  • Migration scope – repositories, historical labels
  • Label 1.0.0.1
  • Label 1.0.0.10
  • Label 1.0.0.15
  • Latest Code
  • Changelist X
  • Changelist Y
  • Changelist Z
  • #Head Revision
slide-17
SLIDE 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
slide-18
SLIDE 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
slide-19
SLIDE 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
slide-20
SLIDE 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
slide-21
SLIDE 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
slide-22
SLIDE 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
slide-23
SLIDE 23

Solution – CCP4 Migration

  • Highlights
  • Performance cross geos
  • Training
  • Migration script development
  • Methodology enforcement
  • Lowlights
  • Methodologies consolidation
  • Symbolic links
  • Server charset mismatch
slide-24
SLIDE 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)

slide-25
SLIDE 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)

slide-26
SLIDE 26

Solution – Perforce  CI

Build/Scan Test

CI Orchestrators Passed Failed

Deployment

slide-27
SLIDE 27

Solution – Perforce  TFS

Code Submission Build/CI Req Story

Development Portal

Bug

slide-28
SLIDE 28

Solution – Perforce  TFS

DEMO

slide-29
SLIDE 29

29

slide-30
SLIDE 30

30

slide-31
SLIDE 31

31

slide-32
SLIDE 32

32

slide-33
SLIDE 33

33

slide-34
SLIDE 34
slide-35
SLIDE 35
slide-36
SLIDE 36

36

slide-37
SLIDE 37

37

slide-38
SLIDE 38

Solution – Perforce  TFS

Code Submission

Req Story

Development Portal

Bug

Test Coverage

Validation Portal Full Data Traceability

slide-39
SLIDE 39

Solution – Perforce  BI

slide-40
SLIDE 40

40

slide-41
SLIDE 41

41

slide-42
SLIDE 42

42

slide-43
SLIDE 43

43

slide-44
SLIDE 44

44

slide-45
SLIDE 45

45

slide-46
SLIDE 46

46

slide-47
SLIDE 47

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
slide-48
SLIDE 48

Thank You!

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