1. HYBRID IT - AN ECOSYSTEM FOR GETTING THE BEST
OUT OF BOTH WORLDS
Oliver Raff, GTS Execu3ve IT Architect
Florian Graf, GTS Cloud Migra3on Architect
Claus Schrøder-Hansen, GBS Applica3on Architect
Clea Zolotow, GTS Dis3nguished Engineer
1

2. ABSTRACT
Hybrid IT provides a managed ecosystem of providers,
resources, and tools. Successful Hybrid IT deployment
requires managing and op<mizing systems of record and
systems of engagement while ensuring new business
requirements can be met. This paper provides an
overview of hybrid IT, brokerage system examples, and
business linkage. Series z is covered as well as midrange
systems. Specific components for the transi<on to and
delivery of a hybrid cloud are explored. Finally, best
prac<ces for hybrid cloud usability u<lizing aggrega<on,
integra<on, and customiza<on capabili<es are outlined.
2

3. Introduc<on
• The strategy for enterprise IT will be to enable different cloud environments across the compute
landscape and gradually enable the enterprise applica3ons to take advantage of this disparate
environment via open API interfaces and management.
• Hybrid IT is an end-to-end plaQorm for consuming IT services securely and conveniently. By
u3lizing standard interfaces, services can be combined and treated as black box by the applica3on
owner, allowing infrastructure, database, or applica3on services to be consumed as-needed. Here,
Hybrid IT requires brokerage as a central plaQorm, with a governance and decision framework for
consuming services.
• This environment naturally leads to ITaaS, which is the transforma3on post-technology into a
business service – u3lizing a service and consump3on model for the business users of the
environment.
3

4. What is it?
Hybrid Cloud: “A cloud compu3ng service that is composed of some
combina3on of private, public, and community cloud services, from different
service providers, for capacity or capability.“
Hybrid IT: “A trusted broker and provider for all IT Services – including
services provided by the IT organiza3on and external providers – using both
cloud compu3ng styles and tradi3onal styles of compu3ng.”
4

5. Systems of Record/
Engagement/Interac<on
• Note here that the emphasis is on the connec3vity between the
different areas of Cloud.
• For example, an organiza3on may have public cloud in several
flavors (Iaas and Paas) as well as private cloud for their Xaas as well
as their legacy systems of record. This has given rise to a new
technology, systems of interac3on – this is the glue that keep all
these systems talking to each other, governed by the broker and
orchestra3on components (Bruce, 2016).
5

6. Flexibility in the Hybrid Cloud
for Business Requirements
• The important concept to remember about ITaaS is that is isn’t a
technology journey, like the move to virtualiza3on. It’s about a total IT
transforma3on to build a service and consump3on model palatable to
your users, whether cloud or not (EMC Corpora3on, 2012).
• This vision is enabled by brokerage services that stretch across the
various hybrid and cloud environments to provide a single pane of
glass environment.
6

7. 7

8. Flexibility in the Hybrid Cloud
for Business Requirements
• The figure above shows a modular, open and integrated approach for
designing, building and running your digital business solu3ons with
flexibility and control.
• These transforma3on scan happen from a legacy governance system
transformed into a cloud and re-transformed into ITaaS, providing
market compe33on and an internal solu3on for dark cloud
environments (Bils, 2013).
8

9. Hybrid Cloud
Brokerage
Services
• Aggregate private and public IT services into a catalog to centralize the comparison and purchase of
services from mul3ple providers.
• Integrate mul3ple IT services from a technical (performance, monitoring, op3miza3on) and
administra3on (cost, metering, repor3ng) stand point.
• Customize IT services through professional services or custom development.
• Compare the IT services provided in the service catalog by various dimensions like deployment
model, Service Level Agreement, point of delivery (loca3on of data center) and price
Hybrid Cloud Brokerage Services
Traditional IT
Private
Cloud
SaaS
PaaS
Broker
Serv ice
Discov ery
Cost / Inv oice
Aggregation
Prov ider Mgmt
Serv ice Of f ering
Mgmt
Orchestration &
Policies
Pricing &
Fulf illment Mgmt
IaaS
Resource Mgmt
9

10. Series z Integra<on with
Hybrid Cloud
• Like any other hypervisor and opera3ng
system, OpenStack can be used as an open
integra3on point for zLinux in the Cloud.
OpenStack is a fully open sourced soiware
that used to connect various cloud
management systems, such as IBM’s Cloud
Orchestrator (ICO), to zLinux virtualized
systems managed by hypervisors.
• Some of the interface op3ons include
dashboard management, API integra3on, or
in the case of ICO, RESTful APIs.
10

11. Transi<on into Hybrid
Cloud
• There are many different use cases to start transi3oning into the cloud. Most
customers won’t have the possibility to start from scratch with new workload,
therefore they are looking into op3ons to analyze their exis3ng workload and
migrate it seamlessly into the Cloud.
• The Hybrid IT Broker considers the type of workload and proposes the best fijng
target cloud (tradi3onal, private and public cloud) as well as migra3on scenario.
The following picture outlines the most common cloud use cases and their
migra3on scenarios.
11

12. 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 poten3ally in
splijng 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 migra3on. 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
Virtualiza3on Format (OVF), which
supports V2V from different hypervisors
plus also P2V transforma3ons. The OVF
contains the metadata informa3on of the
VM plus the actual virtual disks. By
analyzing the meta informa3on (VM
virtual hardware sizing plus plaQorm) and
the actual content in the VDISK the
Hybrid IT Broker would have the ability to
make a jus3fied decision what the most
suitable target plaQorm (Graf, 2015).
12

13. Architectural paQerns for
hybrid service management
• The following diagram is taken from a real customer
deployment and shows the integrated panern for
service management including configura3on
management, and event management. In this case an
on-premise private cloud managed by a cloud provider
is integrated with the customer’s service and systems
management environment of the tradi3onal IT.
• Addi3onally, an on-premise management tool agent is
deployed on the cloud systems for license management
following the on-premise panern. Cloud Service provider On-premise
Dual pattern
• Use ISM tools and interfaces on-premise
and provided by cloud service provider
• Integrate them manually or at processlevel
documenting cross management best-
practices and procedures
Service Mgmt
environment
Managed-workload
Service Mgmt
Environment (*)
Managed-workload
Customized ISM processes
On-premise pattern
• Extend on-premise management tools and
agents to manage also workload on cloud
• Do not leverage built-in service mgmt
capabilities from cloud provider
Service Mgmt
environment
Managed-workload
Service Mgmt
Environment (*)
Managed-workload
Integrated pattern
• Leverage both on-premise and built-in
cloud ISM capabilities and tools
• Use APIs to get mgmt data from cloud and
feed to on-prem mgmt tools and processes
Service Mgmt
environment
Managed-workload
Service Mgmt
Environment (*)
Managed-workload
Customized ISM processes
APIs
(*) on-premise, on SaaS or outsourced
13

14. 14
Cloud Service provider On-premise
Dual pattern
• Use ISM tools and interfaces on-premise
and provided by cloud service provider
• Integrate them manually or at processlevel
documenting cross management best-
practices and procedures
Service Mgmt
environment
Managed-workload
Service Mgmt
Environment (*)
Managed-workload
Customized ISM processes
On-premise pattern
• Extend on-premise management tools and
agents to manage also workload on cloud
• Do not leverage built-in service mgmt
capabilities from cloud provider
Service Mgmt
environment
Managed-workload
Service Mgmt
Environment (*)
Managed-workload
Integrated pattern
• Leverage both on-premise and built-in
cloud ISM capabilities and tools
• Use APIs to get mgmt data from cloud and
feed to on-prem mgmt tools and processes
Service Mgmt
environment
Managed-workload
Service Mgmt
Environment (*)
Managed-workload
Customized ISM processes
APIs
(*) on-premise, on SaaS or outsourced

15. Conclusion
• Here we have shown how to enable different cloud
environments across the compute landscape to allow enterprise
applica3ons to take advantage of Hybrid IT’s ability to u3lize API
interfaces. We can now u3lize standard interfaces such as REST
and JSON and allow IaaS, Saas, and PaaS to be combined and
consumed as needed.
• Migra3on into and between these environments can be
automated and transi3onal and transforma3on is actually
needed to clean legacy installs. Technologies can be used for a
metadata input to the Broker.
• Service delivery provides unparalleled integra3on opportuni3es
as the goal is to provide a single pane of glass for the SLAs and
QoS. Leveraging (and understanding) the system management
stacks of the vendors another large job for the Broker.
Everything revolves around the Broker with a governance and
decision framework for consuming services.
• This environment leads eventually to ITaaS, which is the
transforma3on of IT into a business service.
15

16. Dave in a pixel
16

17. References
• References
• Bils, S. (2013). What Makes ITaaS Transforma3onal? Retrieved July 3, 2016, from
hnp://leverhawk.com/is-itaas-really-a-new-concept-20130628321
• Bruce. (2016). Busines Process Watch Blog. Retrieved July 14, 2016, from hnp://
brsilver.com/ibm-impact-bpm-makes-way-for-smarter-process/
• Buckellew, P., Cus3s, K., Esposito, R., & Lesser, E. (2013). The “upwardly mobile”
enterprise: Sejng the strategic agenda, 1–24. Retrieved from hnp://
public.dhe.ibm.com/common/ssi/ecm/en/gbe03574usen/GBE03574USEN.PDF
• Clabby, J. (n.d.). Mainframes/Linux: Systems of Record, Systems of Engagement.
hnp://doi.org/ZSP03894-USEN-00
• Cognizant Corpora3on. (2016). Cloud360 | Enterprise Cloud Management |
Cognizant Technology Solu3ons. Retrieved July 10, 2016, from hnps://
www.cognizant.com/Cloud360
• EMC Corpora3on. (2012). An IT-as-a-Service Handbook: Ten Key Steps on the
Journey to ITaaS.
• Graf, F. (2015). Workload Transforma3on Analysis, Personal Communica3on.
• Gross, Manhew B., & Hogarth, Jeanne M., Schmeiser, M. (2012). Consumers and
Mobile Financial Services. Federal Reserve Report, (March). Retrieved from
hnp://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 hnps://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
hnps://www-03.ibm.com/press/us/en/pressrelease/44067.wss
• IBM. (2016a). IBM - KVM for IBM z Systems. Retrieved September 1, 2016, from
hnp://www-03.ibm.com/systems/z/solu3ons/virtualiza3on/kvm/index.html
• IBM. (2016b). Systems of Engagement and the Enterprise. Retrieved August 15,
2016, from hnp://www-01.ibm.com/soiware/ebusiness/jstart/
systemsofengagement/
• IBM. (2016c). The Journey to an ITaaS Opera3ng Model Think it. Expert cloud
consul3ng 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
Compu3ng. Retrieved from hnp://www.forbes.com/sites/kevinjackson/
2012/08/12/cloud-management-broker-the-next-wave-in-cloud-compu3ng/
#194c443f3190
• Kloeckner, K. (2016). The Enterprise ITaaS Framework. Bangalore. Retrieved from
hnps://w3-03.sso.ibm.com/services/prac33onerportal/documents/
D610112H11040H77
• Langer, S. (2013). Making the Case for Linux on System z. In WAVV Conference
(p. 49). Covington, Kentucky: IBM. Retrieved from ip://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
hnps://www.gartner.com/doc/3212517/compe33ve-landscape-cloud-service-
brokerage
• NIST. (2016a). 6.1 Cloud Management Broker | NIST. Retrieved from hnps://
www.nist.gov/informa3on-technology-laboratory/61-cloud-management-broker
• NIST. (2016b). Mobile Device Security. Retrieved from hnps://nccoe.nist.gov/
sites/default/files/library/fact-sheets/mds-fact-sheet.pdf
• Owens, M. (2016). The Journey to an ITaaS Opera3ng Model. Retrieved July 3,
2016, from hnps://www.linkedin.com/pulse/journey-itaas-opera3ng-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 Introduc3on. Retrieved August 17,
2016, from hnp://www.bmc.com/blogs/introducing-it-as-service-itaas/
• Rochester, M. (2016). 5 Things to Know about Cri3cal Success Factors for SAP-
centric Transforma3ons. Retrieved April 12, 2016, from hnps://www.ibm.com/
developerworks/community/blogs/5things/entry/
5_things_to_know_about_cri3cal_success_factors_for_sap_centric_transforma
3ons?lang=en
• Sherrill, S. (2015). Building an API Bridge to Your IBM z Systems Applica<ons and
Data. IBM. Retrieved from hnp://www.redbooks.ibm.com/redpapers/pdfs/
redp5296.pdf
• Standards Customer Council, C. (2016). Prac3cal Guide to Hybrid Cloud
Compu3ng. Retrieved from hnp://www.cloud-council.org/deliverables/CSCC-
Prac3cal-Guide-to-Hybrid-Cloud-Compu3ng.pdf
• Stuart, J. (2015). The Fed Finds Rising Mobile-Payments Adop3on, But Big
Hurdles Hinder Usage. Retrieved September 2, 2015, from hnp://
www.digitaltransac3ons.net/news/story/The-Fed-Finds-Rising-Mobile-
Payments-Adop3on_-But-Big-Hurdles-Hinder-Usage
• Tomala-Reyes, A. (2014). What is IBM Bluemix? Retrieved September 1, 2016,
from hnps://www.ibm.com/developerworks/cloud/library/cl-bluemixfoundry/
• White, B., Gasparovic, M., Pinto, F., & Young, R. (2016). Gejng Started with
KVM for IBM zSystems (2nd ed.). Poughkeepsie, NY: IBM Corpora3on. Retrieved
from hnp://www.redbooks.ibm.com/redbooks/pdfs/sg248332.pdf
• Zolotow, C., Graf, F., Pfitzmann, B., Huber, R., Schlaner, M., Schrøder-Hansen, C.,
& Hunt, T. (2016). Transi3on and Transforma3on into the Cloud. In W. Chen, Y.
Zhang, & R. Gonschalk (Eds.), End-to-End Cloud Compu<ng Architecture Design
17