Configuration Configuration ManagementManagement

CheckpointCheckpoint

Presentation GoalsPresentation Goals Describe:Describe:

Our interpretation of the Technical Configuration Our interpretation of the Technical Configuration Management charterManagement charter

What we’ve been doing since the re-orgWhat we’ve been doing since the re-org Current state as we begin Configuration ManagementCurrent state as we begin Configuration Management

Are our assumptions accurate?Are our assumptions accurate?

Illustrate:Illustrate: Our understanding of CMII to dateOur understanding of CMII to date Our approach with implementing CM into BBYOur approach with implementing CM into BBY

Are we on target?Are we on target?

AgendaAgenda

Post Re-Org (Initial) DeliverablesPost Re-Org (Initial) Deliverables Current StateCurrent State Configuration Management II (CMII)Configuration Management II (CMII) Application HierarchyApplication Hierarchy Change ProcessChange Process Scope & GoalsScope & Goals Go Forward StrategyGo Forward Strategy Q&AQ&A

Post Re-Org State of MindPost Re-Org State of MindWhat are our Deliverables?What are our Deliverables?

CMDB

Manage Server configuration with “Police / Manage Server configuration with “Police / Auditor” MentalityAuditor” Mentality Inventory Control, “Definitive Record of Authority”Inventory Control, “Definitive Record of Authority” Audit DeviationsAudit Deviations

Correlation of Configuration Change to approved Correlation of Configuration Change to approved Change Mgmt ticket (or lack thereof)Change Mgmt ticket (or lack thereof)

Provide Deviation-to-Standard Configuration Provide Deviation-to-Standard Configuration Information to CustomersInformation to Customers

Alignment under ITIL with deployment of CMDB and Alignment under ITIL with deployment of CMDB and small number of initial Configuration Items (i.e. – small number of initial Configuration Items (i.e. – Server Name, Location, etc.)Server Name, Location, etc.)

Become Foundation for key business areas (Issue Become Foundation for key business areas (Issue Mitigation, Release Mgmt, Disaster Recovery, Mitigation, Release Mgmt, Disaster Recovery, Systems Monitoring)Systems Monitoring)

Role of Software Config Mgmt. unclear (Integration? Role of Software Config Mgmt. unclear (Integration? Top to Bottom? Parallel?)Top to Bottom? Parallel?)

ITIL Definition of CMITIL Definition of CM

““Identify, record and report on all ITIdentify, record and report on all ITcomponents that are under the control and components that are under the control and

scope of Configuration Management.”scope of Configuration Management.”

Current Wintel Current Wintel Engineering StateEngineering State Engineering ‘Flavor’ of the MonthEngineering ‘Flavor’ of the Month

Documentation non-existent and/or Documentation non-existent and/or inconsistentinconsistent across Engineering team across Engineering team Information captured not audited or reviewed by Information captured not audited or reviewed by interestedinterested parties parties Engineering against documented Technical Specification is Engineering against documented Technical Specification is not occurringnot occurring

Byproducts of Current StateByproducts of Current State Intellectual Capital walks out the doorIntellectual Capital walks out the door Corrective Action is the normCorrective Action is the norm Customer Confusion over varying ‘standards’Customer Confusion over varying ‘standards’ Difficult to backfill Engineers due to dissimilar processesDifficult to backfill Engineers due to dissimilar processes Management of Server / App Configuration hampered due to missing and/or Management of Server / App Configuration hampered due to missing and/or

inaccurate informationinaccurate information ““Waste Approach” to Server Procurement and UtilizationWaste Approach” to Server Procurement and Utilization Ineffective Outage Impact Assessment CapabilityIneffective Outage Impact Assessment Capability Inability to track Device History (what changed?)Inability to track Device History (what changed?) Inconsistent License TrackingInconsistent License Tracking Difficult to track end of Lease InformationDifficult to track end of Lease Information

Configuration Management Configuration Management TermsTerms

Fun with Acronym’s…Fun with Acronym’s… CM: Configuration ManagementCM: Configuration Management CMM-SW: Capability Maturity Model, SoftwareCMM-SW: Capability Maturity Model, Software

Sunsetted in favor of:Sunsetted in favor of: CMMI: Capability Maturity Model IntegrationCMMI: Capability Maturity Model Integration

SEI: Software Engineering InstituteSEI: Software Engineering Institute• Steward of all Capability Maturity Model-related intellectual Steward of all Capability Maturity Model-related intellectual

Property at Carnegie Mellon UniversityProperty at Carnegie Mellon University Open Source approach to CMOpen Source approach to CM

CMII: Configuration Management, Version 2 aka CMII: Configuration Management, Version 2 aka ‘CM2’‘CM2’

ICM: Institute of Configuration ManagementICM: Institute of Configuration Management• Doing CMM “one version better” and branding it as CMIIDoing CMM “one version better” and branding it as CMII• Applying CMM principles across the Organization rather than Applying CMM principles across the Organization rather than

focusing entirely on Softwarefocusing entirely on Software

CMM – Maturity LevelsCMM – Maturity Levels

Application HierarchyApplication Hierarchy

Physical (or ‘Application’) Item Hierarchy

“Make” or“Repairable” Item

“Buy” or“Replaceable” Item

KEY

Integrated CustomerExperience (ICE)

ID: 171

DL380

ICE Application

ID: 111

DLL #1

ID: 121

DLL #2

ID: 122

DLL #3

ID: 123

Compaq DL380G2

ID: 222

OS Build

ID: 233

Rack Server

ID: 232

Assign IP

ID: 231

Compaq DL380G2

ID: 222

OS Build

ID: 233

Rack Server

ID: 232

Assign IP

ID: 231

Infrastructure Drill-Infrastructure Drill-DownDown

Compaq DL380G2

ID: 222

OS Build

ID: 233

Rack Server

ID: 232

Assign IP

ID: 231

ML-222-AD-222-A

BOM-222-A

Technical SpecificationDocuments

I-233-AI-232-AD-232-AI-231-A

Document Type‘I’ = Instruction Set‘D’ = Drawing‘ML’ = Master List‘BOM’ = Bill of Material

# - #### - #

ID No. Revision No.

Instruction (I) Set ExampleInstruction (I) Set ExampleCreator Owner: System Engineer Target Audience: Level 2 Engineer Validated by Target Audience? YES Validated? Configuration Management ID: I-233-A

Howto (Instruction Set) Build OS

Installation Process

The overall server build process (Figure 1) consists of six stages. Each stage has a specific purpose and specific outputs. This document addresses specifically those activities performed in the Post-Operating System stage of the process as well as instructions on bringing the server to this stage. Once this stage is complete the server will comply with Best Buy’s stated base server requirements. Any additional settings are applied based on a project or application/role specific need.

Pre-OperatingSystem

OperatingSystem

OperatingSystem GUI

Mode

Post-Operating

System

ConfigurationCollection

Application /ProjectSpecific

Figure 1 Overview of the build process

Configure Server

Although instructions are provided during configuration using the CDSD boot disk, the following items provide basic instructions

1. Insert the CDSD boot disk.

2. Boot the server.

NOTE: If you enter the wrong information or the build process does not complete successfully, you can restart the process by pressing Y when prompted (immediately following Initializing Setup…)

Creater Owner: Level 3 EngineerTarget Audience: Level 2 EngineerValidated by Target Audience? YES

Configuration Management ID: I-233-A

Master List (ML) Master List (ML) ExampleExample

Number of Items

Compaq Part Number Description Price

Extended Price

0 253864-001 DL380R02 P1400-512KB, 256 MB $2,317.24 $0.001 201099-B21 Pentium III P1400-512KB Processor Option Kit $879.20 $879.200 225011-001 Hot Plug Redundant Power Supply Module $134.40 $0.000 225012-B21 Hot Plug Redundant Fan Option Kit $102.00 $0.00

0 201692-B21256-MB PC133-MHz Registered ECC SDRAM Memory Option Kit (2 x 128 MB) $149.40 $0.00

Server Type: DL380 G2

Configuration Management ID: ML-222-A

CMII MantraCMII Mantra

Only two types of work that occur in a CM2 Only two types of work that occur in a CM2 organizationorganization

Time spent Documenting Technical SpecificationsTime spent Documenting Technical Specifications Time spent performing work described in Technical Time spent performing work described in Technical

SpecificationsSpecifications

No changes are made to code or Infrastructure No changes are made to code or Infrastructure unless the Technical Specifications that describe unless the Technical Specifications that describe them are documented, validated and approvedthem are documented, validated and approved

Change ProcessChange Process

Request for Change(Approval based onTechnical Spec)i.e - I-233-A

Configuration MgmtDocument Repository

CreatorOwner

Technical Review Board(Technically Possible?)

CRBBusiness Decision(Cost vs Benefit?)

CIBImplementation Plan(Assign Resource)

Issue WorkAuthorization (W.A.)

Email Contains:W.A.

Config Documents(I-233-A, ML-233-A,

D-233-A, etc.)TargetAudience

Perform WorkRev Document after

Completion:

I-233-B

Fast Track

End StateEnd State

Compaq DL380G2

ID: 222

OS Build

ID: 233ID: 377

Rack Server

ID: 232

Assign IP

ID: 231

I-233-AI-233-B

I-232-AD-232-AI-231-A

New (Authorized) Tech New (Authorized) Tech Spec. (Rev) describing Spec. (Rev) describing ConfigurationConfiguration

Ability to leverage Ability to leverage historical Data (how many historical Data (how many Rev A’s are still in the Rev A’s are still in the environment, what was environment, what was the original configuration, the original configuration, etc.)etc.)

Expanding Scope Expanding Scope

CMDB

Compaq DL380G2

ID: 222

OS Build

ID: 233

Rack Server

ID: 232

Assign IP

ID: 231

I-233-AI-232-AD-232-AI-231-A

Technology Configuration Management

Process Maturity Accountability Audit

Request for Change(Approval based onTechnical Spec)i.e - I-233-A

Configuration MgmtDocument Repository

CreatorOwner

Technical Review Board(Technically Possible?)

CRBBusiness Decision(Cost vs Benefit?)

CIBImplementation Plan(Assign Resource)

Issue WorkAuthorization (W.A.)

Email Contains:W.A.

Config Documents(I-233-A, ML-233-A,

D-233-A, etc.)TargetAudience

Perform WorkRev Document after

Completion:

I-233-B

Configuration Management Configuration Management GoalsGoals

Accurate inventory of deployed hardwareAccurate inventory of deployed hardware Accurate information on CIs and their documentationAccurate information on CIs and their documentation Work is performed according to technical specificationWork is performed according to technical specification Integrate a document management systemIntegrate a document management system Track Configuration deviationsTrack Configuration deviations Achieve Dev/QA/PROD consistencyAchieve Dev/QA/PROD consistency Provide reporting and auditing capabilities Provide reporting and auditing capabilities Transfer software licenses from device to device & track Transfer software licenses from device to device & track Enable more accurate financial & capacity planningEnable more accurate financial & capacity planning Dependencies between apps, devices and servicesDependencies between apps, devices and services Disaster Recovery – Leverage CMDB infoDisaster Recovery – Leverage CMDB info Help Desk, SOC, Incident and Problem Mgmt tie inHelp Desk, SOC, Incident and Problem Mgmt tie in

Technical Configuration Technical Configuration Management InterfacesManagement Interfaces

SoftwareConfigurationManagement

Provisioning

DisasterRecovery

AssetManagement

Agility

EnterpriseSystems

Monitoring

Meta Data

ChangeMangement

ConfigurationManagement

ScopeScope

Phase 1: Wintel & Unix devicesPhase 1: Wintel & Unix devices

Proposed Phases for the roadmap may include:Proposed Phases for the roadmap may include: Network devicesNetwork devices Network Security devicesNetwork Security devices Desktop devicesDesktop devices Hand held, PDA devicesHand held, PDA devices Store ServersStore Servers MiddlewareMiddleware

Technical Configuration Technical Configuration Management RoadmapManagement Roadmap

2-5 years:2-5 years:Strategic ManagementStrategic Management Planning and long term control over quality, stability Planning and long term control over quality, stability

and flexibilityand flexibility

6-24 months:6-24 months:Tactical Management (Service Delivery)Tactical Management (Service Delivery) To guarantee quality, stability and flexibilityTo guarantee quality, stability and flexibility Service Level, Availability Management, Capacity Service Level, Availability Management, Capacity

Management, Financial ManagementManagement, Financial Management

0-6 months:0-6 months: Operational Management (Service Support)Operational Management (Service Support) To achieve quality, stability, flexibilityTo achieve quality, stability, flexibility Service Desk, Configuration Management, IncidentService Desk, Configuration Management, Incident

& Problem Management, Change Management and & Problem Management, Change Management and Release ManagementRelease Management

Procedures

Processes

Policies

Next StepsNext Steps Continued EducationContinued Education

Training for BSI, ESM, Network, Network Security and Data Center Training for BSI, ESM, Network, Network Security and Data Center representativesrepresentatives

Ramp up the Technical Configuration Management TeamRamp up the Technical Configuration Management Team Close the gap between CMM, CMII and ITIL vision with Joe and Close the gap between CMM, CMII and ITIL vision with Joe and

LisaLisa Integrate roadmap with Software Configuration ManagementIntegrate roadmap with Software Configuration Management Validate and gain buy-in with server teamsValidate and gain buy-in with server teams Market CM with all Platform & Production Services Leaders Market CM with all Platform & Production Services Leaders ITIL progress check with Platform & Production Services LeadersITIL progress check with Platform & Production Services Leaders Define “governing body” to oversee all capabilitiesDefine “governing body” to oversee all capabilities Gain customer buy-inGain customer buy-in

Approach has to be easily understood and not seen as another Approach has to be easily understood and not seen as another hindrance hindrance

ITIL recommends we should define things as what the Customer sees ITIL recommends we should define things as what the Customer sees as a service (i.e. – ‘EMAIL’) rather than the underlying Technology (i.e. as a service (i.e. – ‘EMAIL’) rather than the underlying Technology (i.e. – SMTP, POP3, etc.)– SMTP, POP3, etc.)

Q&AQ&A

Are we on Target with our assumptions?Are we on Target with our assumptions? Are we in line with upper management’s Are we in line with upper management’s

vision when our capability was created?vision when our capability was created? Are there any red flags?Are there any red flags?