Section 1 – Define the NeedSection 2 – Define the SolutionSection 3 – Plan the workSection 4 – Layout the business case
Cost Savings (server consolidation, operational efficiency)Going Green (reduce power consumption, reduce physical foot print, extend life of Data Center facilities)Operational Agility (decreased proviGreen Grid – data center efficiency standardssioning time, increased availability, lower RTO/RPO)
Which came first the chicken of the egg?
C02 or Power Reduction objectives
VMWorld 2009 - Gebelin Getting To Yes!
Getting to Yes!<br />Developing a Strategic Business Case for Virtualization <br />Chris Gebelin<br />MGM MIRAGE<br />Executive Director, Enterprise Management<br />firstname.lastname@example.org<br />
Building the Business Case<br /> Define the Need<br /> Define the Solution<br /> Plan the Work<br /> Financial Analysis<br />
Benchmark Current<br />THIS IS NOT EASY!<br />Toughest part of the processes for most organizations<br />Use Goals & Objectives to define KPIs<br /><ul><li>What is total current cost to deploy a physical server?
What is the annual cost to operate a physical server?
How long does it take to deploy a physical server?</li></li></ul><li>Additional Factors<br />P2V Migrations<br /><ul><li>Analyze current server inventory to determine candidates
Supports lower operating costs, and reduces future capital costs associated with hardware upgrades/refresh</li></ul>Organizational Analysis<br /><ul><li>Organizational capability/resistance to CHANGE
Agility</li></li></ul><li>Recap<br />Talked with Sr. Management, technical staff, and customers to document the goals &objectives for the program<br />Benchmarked current Key Performance Indicators<br />Evaluated the impact on our current infrastructure environment<br />Defined P2V candidates<br />Took a hard look at the impact on our organization & it’s ability to adopt this change<br />
The Plan<br /> What Services to offer<br /> Layout Technical Model<br /> Consider Scalability & Manageability<br /> Engineer the Solution<br />
Service Design<br /><ul><li>Service Definition drives design, cost (capital expense & operating expenses), deployment timelines, DR capabilities
Leverage Tier Model from Storage Management practice</li></li></ul><li>Service Management<br />Capacity Management<br /><ul><li>Key to long term success of Virtual Infrastructure is “Unit of Consumption” approach</li></ul>Unit of Compute<br />Unit or Memory<br />Unit of Storage<br />Unit of Network <br />
Building Blocks<br />Key Design Principles<br /><ul><li>Align to Service Requirements… don’t over engineer
Use a Modular approach… virtual infrastructure needs to scale easily and rapidly
Design fully built-out solution, but deploy what you need </li></li></ul><li>Solution Recap<br />Using our goals & requirements we defined the service offerings<br />Developed a technical solution that:<br />Meets our service offering needs<br />Is modular is design, so that we can expand capacity in each of the four “Units of Consumption”<br />Is designed for full build-out so we know maximum capacity<br />
Converting Strategy into Action<br /> Technical scope of work<br /> Migrations<br /> Building & deploy service management<br /> Organization changes<br />
VI Program<br />P2V Objective: 400 servers<br />P2V Objective: 400 servers<br />Period 1 Scope<br />Period 2 Scope<br />Period 3 Scope<br />Virtual Infrastructure<br /><ul><li>Design & Architecture for dual data center VM Infrastructure
Implement scalable/modular infrastructure to support 1200 guests
VI foundation (compute, memory, storage, network)
VI management (Virtual Center, Capacity Planning)</li></li></ul><li>Migrations<br />Build a Process Map<br />Partner with Application Owners & Developers<br /><ul><li>Develop a repeatable process for migrations; identify roles & responsibilities
Demonstrate benefits to them… recovery, clones for testing & dev
Don’t forget to Ask the big question… does “not supported” mean it’s never been tested in a virtual environment or are there known compatibility issues?</li></li></ul><li>Organizational Strategy<br /><ul><li>Keys to success for managing VI is adopting Service Management approach:</li></ul>Policies, Procedures & Service definition<br />Update organizational responsibilities<br />Management of VI components (hosts, network, storage)<br />Guest Provisioning<br />Capacity Management<br />Funding Strategy for “Unit of Consumption” replenishment<br />Overall Service Ownership<br />
VI Policy<br />Wave 1: Mandatory VM candidates<br />Wave 2: Potential VM candidates<br />Wave 3: Future VM candidates<br />Excluded VM candidates<br />
Program Recap<br />Worked with Program Manager to define the scope of work and a schedule<br />Communicated the Program Plan with other IT departments <br />Developed a process for migrations to get everyone on the same page<br />