iw16 presentation_05 25 16
TRANSCRIPT
Separating one of the world’s largest Informatica platformsPhil Morris & Edmundo SepulvedaMay 25, 2016
Introductions
2
Phil Morris
Edmundo Sepulveda
Operations and Service Transition, Hewlett Packard Enterprisehttps://www.linkedin.com/profile/view?id=24629848
Informatica Shared Services Architect, HP Inc.
https://www.linkedin.com/pub/edmundo-sepulveda-castro/b9/180/97
3
Agenda
1 The challenge; overall approach
2 How we maintained “business as usual”
Managing separation challenges 4
3 Before & after architectures
6 Q & A
5 Best practices & lessons learned
4
The challenge
• Set in the context of one of the largest IT company separations in history
• How we separated Hewlett Packard’s Informatica Shared Services (ISS) platform to support the data integration needs of both Hewlett Packard Enterprise and HP Inc.
Never before seen scale, scope and timeline
7.5KTotal testers
159KSIT
test cases
135KUAT
test cases
100KSharePoint
sites
436Mock
cutovers
19MBatch jobs
2.6KApps
dispositioned
21KResolved defects
32.9KServersre-IP’d
8 PBNew
storage
375.5KEmail
accounts
6K
Servers built
12KE2E
test cases
5.2KIT FTEutilized
2.6KReleases
1.2KGo-lives
74KInterfaces
4KProject
milestones
560Projectplans
2.5KLinked
dependencies
9.5months
Record setting paceRequirements 34 days
Design 41 days
Build 69 days
Test 104 days
Go Live 67 days
• Largest and most complex business separation in history
• Successful execution has enabled HPE to create a customer-facing divestiture and separation go-to-market practice
5
ISS overview and features
6
• Shared platform where IT teams can share Informatica software products
• Highly available and scalable infrastructure/architecture• Facilitated onboarding • Highly monitored, automated alerts and centralized
support
PowerCenter highlights • SAP connector• GRID enabled• Web services• Salesforce.com connector• Vertica connector
3-Tier environments
HPUX servers
Active-passive servers
Hewlett PackardCloud environment
7
Original HPQ ISS architecture
DEV
DEV Repository
ITG
ITG Repository
ITG
PRO
PRO Repository
PRO
PRO PRO
PRO
PRO Repository
PRO
PRO PRO
PRO
PRO Repository
PRO
PRO PRO
PRO PRO
PRO PRO
ITG
PRO
Atlanta
Austin
Houston
Go-forward HPE & HPI architectures HPI : PowerCenter 9.6.1 – hot fix 3
8
DEV
DEV Repository
ITG
ITG Repository
ITG
PRO
PRO Repository
PRO
PRO PRO
PRO
PRO Repository
PRO
PRO PRO
HPE Austin
HPE Houston
Confidential
HPE : PowerCenter 9.5.1 – hot fix 4
DEV
Repo
ITG
Repo
ITG
PRO
PRO Repository
PRO
PRO PROPRO PRO
PRO PRO
DEV
HPI Austin
Overall approach
9
Managed under Separation Management Office
Maintained business operations & continuity at all times
Maximized re-use of existing ISS infrastructure, architecture
Minimized actions for or disruption to tenant applications
Tailored plan for every application according to disposition
Disposition types and approach
Disposition type Description
1 Do nothing No transfer or configuration update required
2 Sunset Remove application from the landscape
3 Give & go Application moved as-is from current location to target data center
4 Configure in place Logical separation by configuration without physical separation
5 Extract & go Create new instance of the same application and transfer required data only
6 Clone, cleanse & go Clone complete application and cleanse data that should not be transferred
7 Extract & transform Implement new application and extract, transform & load data from old application
Increasing effort
8
11
How we maintained “business as usual”
• Weekly “office hour” Information / Q&A sessions
• Implementation of platform “Click to chat” services
• Set up of virtual “War Rooms” during key periods
• Development team playbook for detailed separation instructions
• Supported normal business practices (onboarding, app updates, platform patches), with streamlined processing
• Individual application support, consultancy, and answering questions
• Set up a shared network space to use during cutover period
• Streamlined and simplified support model
Managing separation challenges
Simplification of underlying infrastructure - Atlanta datacenter exit
Implementation of new firewalls
Platform and application ReIP activities
Challenges sending files
12
Best practices • “Escalate in 24, resolve in 48”
• Categorize every tenant application upfront
• Process tailored to each application type
• 24*7 Click to Chat service
• Upfront detailed survey to capture all separation related information for every asset
• Platform team undertakes as many activities centrally as possible (consistency, efficiency, minimize mistakes)
• Set up new dedicated portal for all separation activities
• Creation of “playbook” guiding application teams through detailed step-by-step instructions
• Re-use existing hardware as much as possible
• Cutover in a staged, controlled way – DEV/ITG/PRO
13
14
Best practices
• Fight the urge to change
• Take full advantage of Vibe, VIBE is half the battle
• Change OS is a battle that you might lose
• Simplify and streamline decisions for your customers
• Replicate servers 100%, even what you do not agree with
• Verify the use of environmental variables within your projects
• Virtualize a path when a new install does not create it
• Check the shared folder utilization by project multiple times
• Copy everything and then delete, do not pick what to copy
• Meet daily with your team
• Communicate often throughout your projects, but know your audience
• Update your contact information after the separation
• Plan for geolocation accordingly
• Execute the cutover well before the separation and work in parallel
