1. Transi'on and Transforma'on into a Cloud
Environment
Clea Zolotow, IBM GTS Dis4nguished
Engineer
1

2. Co-Authors
(the usual suspects)
• Florian Graf
• Birgit Pfitzmann
• Rebecca Huber
• Marcel SchlaLer (re4red)
• Claus Schrøder-Hansen
• Anthony Hunt
2

3. ABSTRACT
• It is a challenging migra/ng and transform exis/ng
workloads into the cloud, especially those requiring the
managed services (i.e., pain/ng the system with tooling).
• Various types of transi/on and transforma/on (T&T) into
the cloud from physical moves to cogni/ve migra/on are
covered as well as wave planning for applica/ons.
• T&T is an integral part of cloud services, and crea/ng a
repeatable, reusable, factory model for a customer helps to
ensure a successful cloud migra/on.
3

4. Introduc'on
• The cloud journey starts with
building a private or signing up for
a public cloud offering.
• Cloud offers many opportuni4es
and advantages for enterprise
customers, but also reveals
challenges migra4ng exis4ng
workload into a cloud.
• Exis4ng workload is the majority of
cloud applica4ons when a large
enterprise adopts cloud and new,
greenfield, developments are
usually an excep'on.
4

5. Data Centre Migra'on:
Terminology
• Data Centre Migra'on (DCM) and Data Centre Reloca'on (DCR) are fundamentally the same thing
and represent the physical or logical reloca4on of IT services from one hos4ng loca4on to another.
This reloca4on could consist of no physical hardware moves at all, or it could consist of everything
being loaded into a truck and driven to the new loca4on, or anything in between. Some4mes
“reloca4on” is associated with pure moves without many changes to the soZware and management,
while “migra4on” is used for stronger transforma4ons, such as to a managed cloud.
• Data Centre Consolida'on (DCC) is a DCM or DCR from mul4ple hos4ng loca4ons into fewer hos4ng
loca4ons. (I need a word for Data Centre adds – where we add mul4ple sites to a single datacenter
construct!)
• Data Centre Transforma'on (DCT) is the process of bringing maximum technical, opera4onal and
cost efficiency to the Data Centre through a formal program of review and technology change.
• Data Migra'on (DM) is the migra4on of data from one applica4on, database or service to another,
and a far simpler task, with many data replica4on technologies available to support such data
movement. Data Migra4on is likely to be a component of a DCM, DCR or DCC program (Dagley, 2011).
5

6. STEPS FOR TRANSITION
AND TRANSFORMATION
Discovery
Planning
Transforma'on Planning
Migra'on of a move group
Early-life support and steady-state
6

7. Cisco Tetra'on – a new
wave planning tool
Full visibility: All
infrastructure, all
applica4ons, all data
In mapping and
recording a distributed
IT environment, Cisco
Tetra4on Analy4cs
provides visibility and
telemetry data across
every applica4on and
infrastructure
component.
7

8. ENGAGING THE ENTERPRISE:
Wave Planning
• Wav planning across
mul4ple sites needs to be
accomplished to ensure
images move in their
applica4on groups.
• A wave is a group of servers
or applica'ons migrated in
the same 'me period.
• Here, each site is denoted by
a color and the connec4vity
between the servers is
indicated by lines. Note that
this would be a very difficult
group of servers to break
into waves.
8

9. TOOLING AND AUTOMATION
Image-based tooling (such as Double-
Take Move and PlateSpin) and SAN
based tools (u4lizing vendors such as
Cirrus and Vicom) can be u4lized.
This tooling choice needs to be
determined as part of the T&T
architecture.
Other cloud tools, such as Racemi and
Rackware, can paint the image as well
(either pre- or post-migra4on) for
rela4vely minor opera4ng system and
tooling changes.
9

10. Business Applica'on
Owners
• Before we get all enamored with the geekiness of it all, cloud migra4on is not
a server or image migra4on; it is an applica4on migra4on.
• The applica4on owner must be involved and available for interviews, where
applica4on informa4on from automated discovery is verified and various
service aspects are determined. This is many 4mes not sustainable.
• During the migra4on planning, the applica4on owner can also provide change
windows for the migra4on and has input on the migra4on design and plan.
It’s far easier to have this dictated to the applica4on owner, otherwise the
transforma4on will never happen.
• The business applica4on owner is also responsible for any changes that are
planned on applica4on components and to baseline tes4ng before migra4on
of the applica4on and for User Acceptance Tes4ng (UAT) of the applica4on in
the target environment.
10

11. 11
Networking and T&T
• Most migra4on ac4vi4es go through a network channel into the
new cloud data center (excluding the rare liZ and shiZ and
reinstall of applica4ons with no data movement).
• This pipe has to be reliable and provide enough bandwidth for
the migra4on itself plus the subsequent produc4on opera4on.
• Note that the transi4on network should be different from the
produc4on network, whenever possible.
• Further, note that many large transi4ons require primary and
backup pipes from different vendors in order to ensure
redundancy.

12. 12
WAN could
not handle
transition traffic
WAN could
not handle
transition traffic

13. Compute Block and T&T
• The compute block is based on a hypervisor, like VMware ESX or KVM.
• The conversion from physical to virtual or the change of the
virtualiza4on hypervisor can influence the workload in different ways.
• The performance of the new hardware needs to be at least equal to
the source system.
• Benchmarks like rPerf (Cler, 2013) or RPE2 (Temple, 2012) can help in
that area . Physical servers may also be included in the cloud.
• Be careful of rightsizing images when they move!
13

14. Managed
Infrastructure as a
Service (MIaaS)
• (MIaaS) come with their own system management
toolset to provide backup, monitoring, patching,
security compliance and many other services.
• These tools have to be deployed onto the migrated
systems, which is challenging.
• Each of the managed services (like monitors) to be
deployed has its own pre-condi4ons which have to
be fulfilled to successfully install the soZware.
• The migra4on process has to ensure that these
precondi4ons are met or even beLer that the
managed services deployments are robust enough to
fulfill their precondi4ons themselves. For that to
take place the scope of the managed services
development has to be extended to not only cover
freshly provisioned but also migrated workload.
• It is important to note that the migra4on of the
server into the cloud contains the “pain4ng” of the
applica4on to be cloud-compliant.
14

15. Security, compliance and
audit requirements
• During a migra4on to the
managed Cloud, the system is
aLached to the centralized
authen4ca4on system and all
local unmanaged users are
revoked unless specific
excep4ons are approved.
• Therefore, it is important to
assess the user set-up of each
applica4on in advance to lower
the risk of breaking the
business applica4on.
• Furthermore the business
applica4on oZen requires a
configura4on change to be able
to query the new centralized
AD/LDAP for user logins and
permissions.
15

16. Transi'on into Hybrid
Cloud
• There are many different use cases to start transi4oning into the cloud. Most
customers won’t have the possibility to start from scratch with new workload,
therefore they are looking into op4ons to analyze their exis4ng workload and
migrate it seamlessly into the Cloud.
• The Hybrid IT Broker considers the type of workload and proposes the best fisng
target cloud (tradi4onal, private and public cloud) as well as migra4on scenario.
The following picture outlines the most common cloud use cases and their
migra4on scenarios.
16

17. Simple Workload Discovery
and Migra'on Execu'on
– Independent Workload View assumes
workload with common images can be
separated i.e. each workload is
considered on it’s own. This results
poten4ally in splisng images used by
more than one workload
– Combined Workload View assumes a
workload is only migrated to the cloud if
all its images can be migrated.
Workloads with common images are
only migrated together, i.e. if one
workload cannot be migrated, neither
can any of the workloads that share the
common image with this workload.
In the self-service fashion, outsourced
customers would like to use an integrated
portal as main point of entry for their
workload discovery and migra4on. In a
simple world the customers would be
given the ability to upload a flat-file based
image from his workload. Industry
standard would be the Open
Virtualiza4on Format (OVF), which
supports V2V from different hypervisors
plus also P2V transforma4ons. The OVF
contains the metadata informa4on of the
VM plus the actual virtual disks. By
analyzing the meta informa4on (VM
virtual hardware sizing plus platorm) and
the actual content in the VDISK the
Hybrid IT Broker would have the ability to
make a jus4fied decision what the most
suitable target platorm (Graf, 2015).
17

18. Quality Gates
• No governance is complete
without including quality gates.
The wave lifecycle contains quality
checkpoints at the end of each
phase (as in the figure below),
e.g., to ensure that relevant
applica4on and middleware
discovery has been completed
before final plans are made, and
that plans are final with all
relevant aspects before migra4on
starts.
• Phases that have a cri4cal
milestone as part of their process
have a checkpoint within the
phase, e.g. detailed design
contains a financial checkpoint,
and migra4on contains a
migra4on Go/No Go checkpoint.
18

19. 19
ØUpdated
App
Exclusion
List
Ø Handover
checklist
Ø Application
Acceptance
Report
Ø Pre-Migration
Checklist
Ø Post-
Migration
Checklist
Ø Qualification
(IQ/OQs)
Ø Application
Group HW/SW
Qualification
Certificate
Ø Test Plans
Ø Solution Design
(ISD)
Ø Updated Wave
Plan & Migration
Schedule
Ø Infra Sol
Design
(ISD)
Ø App Cost
info
Ø Wave Scope
Document
Ø Wave App
Exclusion List
Ø Network Test
Results
Ø Data Center
Capacity
Requirements
Ø Project
Plan
Ø Roles &
Resp
Ø AAQs
ØUpdated
App
Exclusion
List
Ø Handover
checklist
Ø Application
Acceptance
Report
Ø Pre-Migration
Checklist
Ø Post-
Migration
Checklist
Ø Qualification
(IQ/OQs)
Ø Application
Group HW/SW
Qualification
Certificate
Ø Test Plans
Ø Solution Design
(ISD)
Ø Updated Wave
Plan & Migration
Schedule
Ø Infra Sol
Design
(ISD)
Ø App Cost
info
Ø Wave Scope
Document
Ø Wave App
Exclusion List
Ø Network Test
Results
Ø Data Center
Capacity
Requirements
Ø Project
Plan
Ø Roles &
Resp
Ø AAQs
QC-1
Assessment
QC-3
Detailed
Design
QC-4
Implementation
Planning
QC-6
Post Migration
QC-7
Handover
QC-2
Financial
QC-5
Migration
Go/No-Go
Global
Quality
Plan
Application
Group
HW/SW
Qualification
Certificate
Wave Qual
Reports
Global
ICON
Quality
Report
Wave ISD
Soft
Ckpt
Hard
Ckpt
Soft
Ckpt
Hard
Ckpt
Wave Scope
Document
Wave ISD
Signoff
CHECKPOINTSMILESTONESDELIVERABLES
CLOSURE
Wave/Global
HANDOVER
MIGRATION
EXECUTION
Ø WQR: All
App Groups
completed
Ø GIQR: All
Waves
completed
Handover
Checklist
Application
Group
Pre/Post
Migration
checklists
IMPLEMENTATION
PLANNING
DETAILED DESIGN
APPLICATION
ASSESSMENT
KICKOFF
PHASE

20. Tes'ng effort and acceptance
of migra'on window
• Service disrup4on during migra4on is
unavoidable. Before the execu4on of the
migra4on an agreement has to be
reached with the business owners of the
applica4on for when and for how long it
is acceptable to be unavailable.
• A set of migra4on ac4vi4es, like data
transfer, can happen in parallel to the
produc4on opera4on of the applica4on
but at a certain point in 4me the
migra4on window for the cut-over has to
be started.
• Prac4cal experiences show that it is
challenging to find an agreement with
the business for one or more migra4on
windows.
20

21. Paten4ng Heritage
21

22. References
• References
• Bils, S. (2013). What Makes ITaaS Transforma4onal? Retrieved July 3, 2016, from
hLp://leverhawk.com/is-itaas-really-a-new-concept-20130628321
• Bruce. (2016). Busines Process Watch Blog. Retrieved July 14, 2016, from hLp://
brsilver.com/ibm-impact-bpm-makes-way-for-smarter-process/
• Buckellew, P., Cus4s, K., Esposito, R., & Lesser, E. (2013). The “upwardly mobile”
enterprise: Sesng the strategic agenda, 1–24. Retrieved from hLp://
public.dhe.ibm.com/common/ssi/ecm/en/gbe03574usen/GBE03574USEN.PDF
• Clabby, J. (n.d.). Mainframes/Linux: Systems of Record, Systems of Engagement.
hLp://doi.org/ZSP03894-USEN-00
• Cognizant Corpora4on. (2016). Cloud360 | Enterprise Cloud Management |
Cognizant Technology Solu4ons. Retrieved July 10, 2016, from hLps://
www.cognizant.com/Cloud360
• EMC Corpora4on. (2012). An IT-as-a-Service Handbook: Ten Key Steps on the
Journey to ITaaS.
• Graf, F. (2015). Workload Transforma4on Analysis, Personal Communica4on.
• Gross, MaLhew B., & Hogarth, Jeanne M., Schmeiser, M. (2012). Consumers and
Mobile Financial Services. Federal Reserve Report, (March). Retrieved from
hLp://www.federalreserve.gov/econresdata/mobile-devices/files/mobile-
device-report-201203.pdf
• Gucer, V. (2015). 5 Things To Know About IBM Bluemix (5 Things To Know IBM
Redbooks Blog). Retrieved September 1, 2016, from hLps://www.ibm.com/
developerworks/community/blogs/5things/entry/
5_things_to_know_about_ibm_bluemix?lang=en
• IBM. (2014, June 2). IBM News room - 2014-06-02 IBM Opens Mainframe Linux
and Cloud Center in Beijing - United States. Retrieved September 2, 2015, from
hLps://www-03.ibm.com/press/us/en/pressrelease/44067.wss
• IBM. (2016a). IBM - KVM for IBM z Systems. Retrieved September 1, 2016, from
hLp://www-03.ibm.com/systems/z/solu4ons/virtualiza4on/kvm/index.html
• IBM. (2016b). Systems of Engagement and the Enterprise. Retrieved August 15,
2016, from hLp://www-01.ibm.com/soZware/ebusiness/jstart/
systemsofengagement/
• IBM. (2016c). The Journey to an ITaaS Opera4ng Model Think it. Expert cloud
consul4ng and strategy for business growth. In InterConnect (p. 15). Las Vegas,
Nevada: IBM.
• Jackson, K. L. (2012). Cloud Management Broker: The Next Wave In Cloud
Compu4ng. Retrieved from hLp://www.forbes.com/sites/kevinjackson/
2012/08/12/cloud-management-broker-the-next-wave-in-cloud-compu4ng/
#194c443f3190
• Kloeckner, K. (2016). The Enterprise ITaaS Framework. Bangalore. Retrieved from
hLps://w3-03.sso.ibm.com/services/prac44onerportal/documents/
D610112H11040H77
• Langer, S. (2013). Making the Case for Linux on System z. In WAVV Conference
(p. 49). Covington, Kentucky: IBM. Retrieved from Zp://public.dhe.ibm.com/
eserver/zseries/zos/vse/pdf3/wavv13/
Making_the_Case_for_Linux_on_System_z.pdf
• Moore, G. (2011). Systems of Engagement and The Future of Enterprise IT. Aiim,
14.
• Nag, S. (2016). Compe//ve Landscape: Cloud Service Brokerage. Retrieved from
hLps://www.gartner.com/doc/3212517/compe44ve-landscape-cloud-service-
brokerage
• NIST. (2016a). 6.1 Cloud Management Broker | NIST. Retrieved from hLps://
www.nist.gov/informa4on-technology-laboratory/61-cloud-management-broker
• NIST. (2016b). Mobile Device Security. Retrieved from hLps://nccoe.nist.gov/
sites/default/files/library/fact-sheets/mds-fact-sheet.pdf
• Owens, M. (2016). The Journey to an ITaaS Opera4ng Model. Retrieved July 3,
2016, from hLps://www.linkedin.com/pulse/journey-itaas-opera4ng-model-
mike-owens
• Pappe, S. (2016). IBM Cloud Compu/ng Reference Architecture (1 No. 3).
Armonk.
• Rixon, C. (2011). IT as a Service (ITaaS): An Introduc4on. Retrieved August 17,
2016, from hLp://www.bmc.com/blogs/introducing-it-as-service-itaas/
• Rochester, M. (2016). 5 Things to Know about Cri4cal Success Factors for SAP-
centric Transforma4ons. Retrieved April 12, 2016, from hLps://www.ibm.com/
developerworks/community/blogs/5things/entry/
5_things_to_know_about_cri4cal_success_factors_for_sap_centric_transforma
4ons?lang=en
• Sherrill, S. (2015). Building an API Bridge to Your IBM z Systems Applica/ons and
Data. IBM. Retrieved from hLp://www.redbooks.ibm.com/redpapers/pdfs/
redp5296.pdf
• Standards Customer Council, C. (2016). Prac4cal Guide to Hybrid Cloud
Compu4ng. Retrieved from hLp://www.cloud-council.org/deliverables/CSCC-
Prac4cal-Guide-to-Hybrid-Cloud-Compu4ng.pdf
• Stuart, J. (2015). The Fed Finds Rising Mobile-Payments Adop4on, But Big
Hurdles Hinder Usage. Retrieved September 2, 2015, from hLp://
www.digitaltransac4ons.net/news/story/The-Fed-Finds-Rising-Mobile-
Payments-Adop4on_-But-Big-Hurdles-Hinder-Usage
• Tomala-Reyes, A. (2014). What is IBM Bluemix? Retrieved September 1, 2016,
from hLps://www.ibm.com/developerworks/cloud/library/cl-bluemixfoundry/
• White, B., Gasparovic, M., Pinto, F., & Young, R. (2016). Gesng Started with
KVM for IBM zSystems (2nd ed.). Poughkeepsie, NY: IBM Corpora4on. Retrieved
from hLp://www.redbooks.ibm.com/redbooks/pdfs/sg248332.pdf
• Zolotow, C., Graf, F., Pfitzmann, B., Huber, R., SchlaLer, M., Schrøder-Hansen, C.,
& Hunt, T. (2016). Transi4on and Transforma4on into the Cloud. In W. Chen, Y.
Zhang, & R. GoLschalk (Eds.), End-to-End Cloud Compu/ng Architecture Design
22