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
business functions
Enterprise Application Portfolio
SaaS
65
AppOps team
27 engineers
IT tools
50
Business
100
Customer
600 developers
Total
215
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
Dev
Request for
SDLC Instance
Test
Infrastructure
Verification
Hardware
Setup
Web Server
Configuration
Load
Test
UAT
Build VMs –
new or clone
Firewall
Changes
DNS
Entries
External
Interface &
Integration
Install,
Setup,
Configure
PPM
Tasks
Workload
Database
Refresh
Workload
Monitoring
Setup
Stage
Latest Code
Deployment
Security – VM
access control
20 Major Steps
3 to 5 Weeks in Traditional Virtualized Environment
4
Production
Load
Balancer
Entries
Functional
Testing
Environmental
Testing
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
work around
3+ weeks gaps up
to 5x per project
AppOps may
say “No”
to some
requests
Late projects cause
domino effect
with constrained
resources
Variations in
calendar and
service quality
5
Human Middleware Problem – AppOps Team View
Handoffs
Slow and
Error Prone
Capacity
Constrained
Global Team
Management
Silos. Globally
distributed teams.
Multiple application
experts.
Many manual steps.
Ticketing systems.
Human error.
Only 4-6 projects
in parallel
Project manage
around PTO and
holidays.
Variable skills
6
Two Project Goals
Transition
to Private Cloud – 4,000 VMs
Automate
the Process – 24 hours
Key Dependency
Need SDDC to automate the process
7
Phased Project Approach
Phase 1 - Completed
Dev
Test
Phase 2 - H1 2014
UAT
 Deploy automation and management
capabilities





8
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
Load
Test
Stage
Production
 Expand service profiles – using
expanded virtual network and
storage in IaaS
 Financial transformation – chargeback
 Advanced analytics, performance
management
 Transition 1,200 VMs Stage, LoadTest
Traditional Operations Functions – Provided by AppOps
Process
Governance
People
Cloud Automation and Management
vCloud Suite
Extension
via
API and SDK
Private Cloud IaaS
Software-Defined Data Center
9
3rd Party
Components
Why Standardize and Automate Service Provisioning?
Service
Request
40 work week effort – Per release…
Virtual Server
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
180
1.
Re-provision instead of repair
and cross-training teams
2.
Improve blueprints to drive down
defects, automate functional and
environmental testing
3.
Additional automation platform
capabilities
Provisioning time (hours)
160
1.
140
120
Plan to get to 24 hour goal
100
•
2.
80
•
60
3.
40
2013 Goal
Provision – 16 hours
20
QA – 8 hours
0
05/07
Test13
Dev14
05/22
Test14
05/27
06/19
Dev15
06/25
Test15
07/22
Dev16
08/05
Test16
SDLC Instance - Oracle ERP with Portal (date)
11
More automation and management
changes
Improve QA testing process
Results
Cycle Time
Virtual Machines Transitioned
AppOps Team
Hours per SDLC instance
To Private Cloud
# of Engineers
Goal – 4000
672 hours (4 weeks)
27
2,800
22
Today
Today
2,200
Today
172
36
Phase 1
Phase 2
Reduced provision time
Phase 1
Phase 2
Phase 1
Phase 2
Improved productivity
of 600 developers
Reduced
IT operations costs
(4 weeks to 36 hours)
20%
$1.5M /year
Able to say
Reduced the cost of
a VM/month
95%
“yes”
to developer requests
12
Goal - 5
Goal – 24 hours
80%
($133 to $20)
Reduced
infrastructure costs
$4.5M/year
For More Information
Venkat Gopalakrishnan, Director IT
venkatg@vmware.com
13