The Journey to the Software-Defined Data Center

September 2013

© 2013 VMware Inc. All rights reserved

Executive Summary

AppOps Team
Deploy integrated, complex SDLC instances to support 600 developers.

Challenge
Process is manual, siloed, slow, unreliable. Reduces developer efficiency. Increases risk.

Two Fundamentally Different Options

1. Fix the “human middleware” on traditional infrastructure
2. Replace and automate on private cloud SDDC

Results From Choice to Replace and Automate on SDDC

 Process time – dropped from 4 weeks to 36 hours
 Developer productivity – increased 20% or more
 Project schedule risk - eliminated
 Annual infrastructure and operating costs - reduced by $6M annually

Key Lesson Learned

Invest in Agility, and Service Quality and Cost will Improve

2
Corporate IT Application Group

Manage portfolio of enterprise

applications used by global Enterprise Application Portfolio
business functions
SaaS 65
AppOps team IT tools 50
27 engineers Business 100
Customer Total 215
600 developers

Role
Provision 16 different dev/test
instances that include 80+ app
components.

Infrastructure footprint
 ~4,000 non-production VMs
 ~500 production VMs

3
AppOps Provisions Environments Across SDLC
 Support 30 to 50 major development projects per year
 Team of 27 engineers manually builds each SDLC instance
 Each project needs SDLC instance multiple times per project
Enterprise App Development Project - 9 months

Load
Dev Test UAT Stage Production
Test

Install, Workload Load

Request for Infrastructure Hardware Build VMs – DNS Setup, Database Latest Code Balancer
SDLC Instance Verification Setup new or clone Entries Configure Refresh Deployment Entries

External Workload
Web Server Firewall Interface & PPM Monitoring Security – VM Functional Environmental
Configuration Changes Integration Tasks Setup access control Testing Testing

20 Major Steps
3 to 5 Weeks in Traditional Virtualized Environment

4
Human Middleware Problem – Customer View

“I can’t develop” “My project is late”

“I can’t test” “I’m waiting for the

software I need to
run my business…”

Disruptive Unpredictable Schedule Risk Variable Quality

Developer must AppOps may Late projects cause Variations in

work around say “No” domino effect calendar and
3+ weeks gaps up to some with constrained service quality
to 5x per project requests resources

5
Human Middleware Problem – AppOps Team View

Slow and Capacity Global Team

Handoffs
Error Prone Constrained Management
Silos. Globally
Many manual steps. Only 4-6 projects Project manage
distributed teams.
Ticketing systems. in parallel around PTO and
Multiple application
Human error. holidays.
experts.
Variable skills

6
Two Project Goals

Transition Automate
to Private Cloud – 4,000 VMs the Process – 24 hours

Key Dependency
Need SDDC to automate the process

7
Phased Project Approach

Phase 1 - Completed Phase 2 - H1 2014

Load
Dev Test UAT Stage Production
Test

 Deploy automation and management  Expand service profiles – using

capabilities
 Create 5+1 vDCs
 Blueprints for 80+ applications
 Service catalog with 16 instances
 Transition 2,800 VMs - Dev, Test, UAT
 Key Milestone – 4 months
• 1st automated instance @ 172 hours
expanded virtual network and
storage in IaaS
 Financial transformation – chargeback
 Advanced analytics, performance
management
 Transition 1,200 VMs Stage, LoadTest

8
Traditional Operations Functions – Provided by AppOps

Process People Governance

Cloud Automation and Management

Extension 3rd Party

vCloud Suite via Components
API and SDK

Private Cloud IaaS

Software-Defined Data Center

9
 Why Standardize and Automate Service Provisioning?

Service
Request

Virtual Server 40 work week effort – Per release…

Provision QA Staging Release

Run Book

4 weeks

Virtual Data Center

20 work weeks effort – Once!

Service Blueprint
Definition Policy
POC1 POC2 To Catalog 36 hours

It takes less effort/time to convert the runbook into blueprints

than it takes to “run” the runbook...

10
 Total Cycle Time - Improvements

Improvements

200 1. Re-provision instead of repair

and cross-training teams
180
2. Improve blueprints to drive down
160 defects, automate functional and
1. environmental testing
Provisioning time (hours)

140 3. Additional automation platform

capabilities
120

Plan to get to 24 hour goal

100
2. • More automation and management
80 changes
• Improve QA testing process
60
3.
40
2013 Goal
20 Provision – 16 hours

QA – 8 hours
0
05/07
Test13 05/22
Dev14 05/27
Test14 06/19
Dev15 06/25
Test15 07/22
Dev16 08/05
Test16

SDLC Instance - Oracle ERP with Portal (date)

11
Results

Cycle Time Virtual Machines Transitioned AppOps Team

Hours per SDLC instance To Private Cloud # of Engineers

672 hours (4 weeks) Goal – 4000 27

2,800
Today 22
Today
Today 2,200
172
36 Goal - 5
Goal – 24 hours

Phase 1 Phase 2 Phase 1 Phase 2 Phase 1 Phase 2

Reduced provision time Improved productivity Reduced

of 600 developers IT operations costs
95%
(4 weeks to 36 hours) 20% $1.5M /year
Reduced the cost of
Able to say Reduced
a VM/month
infrastructure costs
“yes” 80%
to developer requests $4.5M/year
($133 to $20)
12
For More Information

Venkat Gopalakrishnan, Director IT

venkatg@vmware.com

13